srn

Out of curiosity, does anyone have recommendations on deploying blesta in a high availability (HA) configuration? As long as database updates aren't required we believe we've figured out how to do atomic updates between two versions on a single machine while nginx is running, but due to the licensing we aren't sure if it's possible to go beyond beyond a single machine. For example, I don't know if two licenses on two different machines and a single database would work.

@Paul please see https://github.com/prgmrcom/otp-phpqrcode

Paypal is no longer refunding the 2.9% commission - please vote for this feature at https://requests.blesta.com/topic/manage-paypal-subscriptions

Sorry, missed this - yes one of our customers found it for us. We applied the workaround and are no longer experiencing issues.

If "Allow users to modify current and create new subscriptions" is selected in "Manage PayPal Payments Standard", meaning that the value of "modify" passed in the paypal form is 1, then paypal reports an error. The workaround is to deselect "Allow users to modify current and create new subscriptions" so that the value of "modify" is 0. Please see https://www.paypal.com/us/smarthelp/article/important-notice-regarding-upcoming-subscription-changes-ts2239

A customer pointed out to us that blesta's labeling scheme is not friendly to older versions of google authenticator in that the issuer is not included in the label, see https://github.com/google/google-authenticator/wiki/Key-Uri-Format#label

+1

Thank you. In reference to CORE-1686, is there any circumstance under which both issuing a credit for unused time and voiding invoices that are not yet due would be desirable? If not, the choice should probably be a drop-down and not individual check boxes. Also, is there any rough estimate of when 4.0 will be released? Are we talking weeks or months?

Actually, to be completely honest I didn't really expect a credit to be issued, but my understanding from talking to support was I should file a bug report. Sorry for the noise if there wasn't really supposed to be a bug report. Assuming it's a new feature and not a bug, I'd like to hear if there's a way we could implement this for ourselves that could contribute to a more general release.

I commented on this feature request thread: http://www.blesta.com/forums/index.php?/topic/588-cancel-reason-account-credit/ asking about the status of the feature request " Configurable credit for remaining time - if a client cancels with 25 days left, I'd like to issue an account credit for the remaining amount." The response back from Paul (on your staff) was "Settings > Company > Billing/Payment > Invoice and Charge Options: Allow Prorated Credits to be Issued for Service Downgrades". That's why I expected a credit to be issued for the canceled service.

This API call generates a credit (ripped from our python interface) call("POST", "Services", "edit", {"service_id": 65, "bypass_module": True, "vars": { "prorate": "true", "status": "canceled", "date_renews": "2016-05-06" }}) This does not: call("POST", "Services", "edit", {"service_id": 66, "bypass_module": True, "vars": { "prorate": "true", "status": "canceled", }}) This does not: call("POST", "Services", "cancel", {"service_id": 67, "vars": { "use_module": False, }})

Here is my bug report then http://www.blesta.com/forums/index.php?/topic/6433-canceling-service-does-not-result-in-a-credit/

Following the same initial process but changing the renewal date to be one day after the creation date (instead of canceling) results in a credit of $5.00. At some point I got a credit of $5.17 instead of $5.00 but have been unable to reproduce the result.

With blesta version 3.6.1, from the admin interface: * Under Settings->Company->"Billing/Payment" ** Ensure "Allow Prorated Credits to be Issued for Service Downgrades" is enabled for the given client group ** Disable "Automatically Apply Loose Credits" (only to simplify expected and actual results) * Under "Clients", create a test client that has "Total Credit" 0.00 and "Total Due" 0.00 * View test client * Click "NEW SERVICE" under "Services" * Select package that recurs and costs money and click CONTINUE * Select "Create Invoice" . Select "Active" for status though this may not matter. Any term greater than one-time and amount greater than 0.0 should work. I created a service with a 1 month term @ 5.00. * Click "ADD SERVICE" * Observe client has Total Credit 0.00 and Total Due $5.00 (or whatever the price is for the initial term) * Select "Manage" for the active service * Under actions, select "Cancel" * Click SAVE under Actions Expected result: Total Credit of 5.00 and Total Due of 5.00 Actual result: Total Credit of 0.00 and Total Due of 5.00 Distribution: Ubuntu Trusty 14.04 php version: 5.5.9+dfsg-1ubuntu4.16 mysql version: 5.5.49-0ubuntu0.14.04.1

While https://dev.blesta.com/browse/CORE-590 exists for the cancellation reason, canceling a service currently doesn't prorate. I'm assuming it's still a new feature since nothing about proration or credits appears in the Services::cancel method. It looks to me like just calling prorate won't always work because prorate won't do anything if an override_price is set.