Paul

It wasn't scheduled for v4 beta 5, it's just the affected version, likely the task was created during beta 5. It's currently assigned to the "Short Term" bucket, for further review and assignment. I'll consider your comments a +1 for the feature.

https://dev.blesta.com/browse/CORE-2364

Edit the invoice to confirm which currency it was billed in. It's possible the $ symbol is associated with your currency. You can update that under Settings > Company > Currencies > Active Currency. If it is in USD, then you should update the currency with the client and make sure the package pricing is set to the right currency.

There are 3 files included in the hotfix for PHP 7: ~/app/app_controller.php ~/app/app_model.php ~/app/models/license.php You must overwrite all 3 with those in the hotfix directory.

cPanel does not allow domains with the word test in them, it's not Blesta. Try using a different domain without that key word.

Yes, you just update with the SMTP credentials they provide under Settings > Company > Emails

9 emails a minute? If you have a large customer base, it could be impractical. I strongly suggest using something like Mailgun (which is free up to like 10k emails/month) as an SMTP server. We are considering adding a rate limit option to the Mass Mailer, but I'm not sure if there is a feature request for it yet. https://requests.blesta.com

We need a webmoney sandbox account, but it's not clear how to get one. They make you promise you're not in the USA. Can anyone offer some test credentials for development?

Don't set up the cron or run the cron manually until you're ready. Blesta will back bill for services that should have been billed when the cron wasn't running, so we suggest making a transition relatively quickly. If you don't you may wish to manually change service renew dates to ensure that they are correct. If you did an import in Jan for example, and a service has a renew date of Jan 15, then when the cron runs it will produce multiple invoices to "catch up" to today.

Sounds like we're going backwards!

The plugin schedules services that are suspended to be cancelled. The 1st setting determines how long a service has been suspended, before it is scheduled to be cancelled. The 2nd setting determines what the scheduled cancellation date will be. The core performs the cancellation, but the plugin schedules it. Without the Auto Cancel plugin, services cannot be scheduled for cancellation automatically.

We got the email around 2am, and reissued and responded at 8:30am.

Just to clarify, the auto cancel plugin simply scheduled services for cancellation. Services scheduled for cancellation are cancelled automatically by the core.

We made the decision to use config option pricing when we added config options and not do a currency conversion because of the complexity. That's not to say that can't change in the future, but it was intentional.

@Blesta Addons lists an OVH Server module as "Coming Soon". Have you tried reaching out to Leaseweb or Antagus about a Blesta module? If you have accounts there and have a good contact at those companies, feel free to loop us in on a conversation.

Modifying the invoice creation form would be part of the core. However, you could create a plugin that adds an action to the Actions section on a client profile page, when clicked, would load the plugin with your own invoice creation form. You'd have full control over it. The core form would still exist, but you could use the one you created instead. This is a good place to start - https://docs.blesta.com/display/dev/Creating+a+Plugin

We will be putting it on our Github (github.com/blesta) next week, we've made some changes to the module. It'll stay on Github, and if we can get some feedback on the module and consider it stable, we'll likely start pulling it in in our builds where it'll appear in the subsequent minor release.

There's no mechanism in place that would allow the receipt to be sent automatically without user action, so sending at a later time would require significant changes. Cron doesn't process these notifications, so if it's not sent at the time it's recorded it's not sent at all. Might be worth looking at changing, but I doubt it would be a very high priority. https://requests.blesta.com

Not sure if I got you a new trial key, so I just PM'd one to you.

Are you getting this under Tools > Logs > Gateway tab? You can click a row to see the raw input/output. It sounds like they may have returned null, or no response. Is port 443 egress open at your firewall? Does CURL support TLS 1.2?

Thanks for the contribution. I've added a note to that task to refer to this thread.

Is it a security related thing to use the client API? Just curious about that. Screenshots look great!

Wow, disk full. I'm beginning to hate CSF/LFD, it spams itself with email and fills up the disk. Give it a few minutes, and it should work again. The new source docs look a bit off, I'll have to check into that.

It was not up to date with v4.0 no, I have updated it just now. http://source-docs.blesta.com and the old docs for 3.6 are archived here http://source-docs.blesta.com/3.6/

Hopefully the author can correct any issues you're experiencing. Would be a shame if you have to stick with CE!