Leaderboard

Just moved the install to a different server. It works fine now. Must of been some weird coincidence that what ever happened, happened while doing the update. That activity must have been the straw that broke the back. This server was for Blesta only, though I did have two light websites temporarily on this server. Certainly was not working hard, so who knows what happened. Some PHP files must have got corrupted Years ago it was common for amazon aws instances to just go bad, nothing could be done, delete and start up new one. Netflix spent a lot of time trying to figure that one out, and never did, per their blog. Only solution was delete instance start new one. Even though a lot of people and companies like Netfix have experienced data corruption, amazon aws has never admitted that data corruption ever happened. I have not had a server failure that necessitated deleting and starting a new one in a couple of years. I suppose I was due. Sucks when something happens and there are no logs to even point in what direction. Specially when it happens while doing an update, as it appears it is a problem with the update. Fortunately building a new server is a trivial matter. I would much rather rebuild a server than rebuild Blesta.

Thanks, I think that would be a useful addition. We'll look into it for CORE-3066.

Oh yeah I'm aware, I was just pointing him in the right direction

If you're trying to use the API to fetch a non-merchant gateway's payment HTML, see Payments::getBuildProcess as @coreyman mentioned above. The arguments required are the method's parameters. If you are making a merchant CC payment, look at the other end-points available on the same page.

That's cause it needs 3 values to work not sure which ones though.

I found this - So I tried accessing an endpoint via the attached image method in postman and it looks like we are on the right track. Looks like the arguments are as follows - "contact_info" => $contact_info, "amount" => $amount, "currency" => $currency, "invoice_amounts" => $invoice_amounts, "options" => $options, "gateway_id" => $gateway_id This method and docblock can be found in \components\gateway_payments\gateway_payments.php /** * Returns an array of HTML markup used to render capture and pay requests for non-merchant gateways * * @param array $contact_info An array of contact info including: * - id The contact ID * - client_id The ID of the client this contact belongs to * - user_id The user ID this contact belongs to (if any) * - contact_type The type of contact * - contact_type_id The ID of the contact type * - first_name The first name on the contact * - last_name The last name on the contact * - title The title of the contact * - company The company name of the contact * - address1 The address 1 line of the contact * - address2 The address 2 line of the contact * - city The city of the contact * - state An array of state info including: * - code The 2 or 3-character state code * - name The local name of the country * - country An array of country info including: * - alpha2 The 2-character country code * - alpha3 The 3-cahracter country code * - name The english name of the country * - alt_name The local name of the country * - zip The zip/postal code of the contact * @param float $amount The amount to charge this contact * @param string $currency The current to charge * @param array $invoice_amounts An array of invoices, each containing: * - id The ID of the invoice being processed * - amount The amount being processed for this invoice (which is included in $amount) * @param array $options An array of options including: * - description The Description of the charge * - return_url The URL to redirect users to after a successful payment * - recur An array of recurring info including: * - start_date The date/time in UTC that the recurring payment begins * - amount The amount to recur * - term The term to recur * - period The recurring period (day, week, month, year, onetime) used * in conjunction with term in order to determine the next recurring payment * @param int $gateway_id The ID of the nonmerchant gateway to fetch, * if null will return all nonmerchant gateways for the currency * @return array An array of HTML, indexed by the gateway name */

Blesta version 4.5.0-b2 (BETA 2) is now available. You can download it from right here (Client Area Login Required). Read the blog post announcement at https://www.blesta.com/2019/01/31/blesta-4.5-beta-released/ This is a BETA release. Beta releases are not considered stable enough for production use, and are UNSUPPORTED. DO NOT INSTALL IN A PRODUCTION ENVIRONMENT. Please report any bugs you find in the v4.5 beta bug forum. Installing Blesta See Installing Blesta in the User Manual for instructions. Upgrading Blesta See Upgrading Blesta in the User Manual for instructions. Release Notes See Blesta Core - Version 4.5.0-b2. For older releases see all Change Logs.