Paul

I think Blesta version 4.6 may solve this for you. Beta soon.

You can configure your packages now for pro-rata, if they purchased a 1 year term then it would be prorated to June 1st or July 1st depending on what you set for the cutofff day. Then you can adjust the renew date and generate a 2nd invoice for June 1st - Jan 1st. After that it'll renew on Jan 1st each year. So, an extra manual step in there unfortunately. We might be interested in adding a prorata month option for yearly services if you want to make a feature request. Prorata option works best with monthly services, so if you have a monthly service you want to renew on the 1st each month, then placing an order will prorate it.. and you pay either partial month or partial month + whole month to get it to renew on the 1st. It doesn't work so well with yearly terms because it will still prorate it to the 1st of the next month not the 1st of a particular month.

One thing I'd like to see is an export directly to Campaign Monitor list, or Mailchimp, etc. Separate feature for a separate time though. CORE-3111 sounds fine with me, so long as the default option is to use system mail settings.

Welcome! The cPanel doesn't utilize any configurable options currently. You can create them, but the module will not detect and use them for provisioning. That's not a bad idea though. Since the cPanel server or server group is selected on the Package level, you'd need to have another Package for Bermuda with the Package configured to use a cPanel server group that contains your Bermuda cPanel servers, or a specific server for Bermuda. I'd suggest doing the following: Create your regular cPanel Packages, assigned to their own Package Group. Create another Package Group for Bermuda, call it "Bermuda Hosting" or whatever you want. Use the "Copy" feature under Packages to copy the Package, modify the name, price, package group, and cPanel server or server group for Bermuda and save. Repeat for all your Packages. Make sure both Package Groups are assigned to your order form (Packages > Order Forms: Edit). You can sort their display by drag and drop within the order form where the Package Groups are shown. You can sort the display of the Packages within their groups under Packages > Package Groups by clicking the row for the Package group and drag and drop packages within it. I hope that helps! You can make a feature request for using configurable options to override or set the cPanel server or server group at https://requests.blesta.com It's a good idea and something we'd be likely to add in the future.

Does the client have any contacts? What version of Blesta? What version of the widget?

At the time an invoice is generated, I believe we save the previous balance on the account. It might make sense to store the previous balance, but as you indicate it would be the balance at the time the invoice was generated, not including the generated invoice since application of payments/credits would occur later.

PayPal reports the error when the client tries to make any payment, or when the client tries to set up a subscription? Are you experiencing this now in the live environment? Thanks for the link.

Settings > Billing/Payment > Invoice Customization: Display on Invoice [x] Payments/Credits This will show any payments or credits applied to the invoice. If we are not showing total account credits, maybe that could be shown here?

If we add an order search, it would be a search option and not part of the smart search. Similar to the ticket search. Would order number be the only metric you would need to search by? We have another task to display order history to clients, see https://dev.blesta.com/browse/CORE-2295 which may be useful in this case.

A 500 error is a server-side issue, not a Blesta order. I would suggest checking your server logs. Could be a lot of things.. maybe server doesn't have enough memory? Maybe Ioncube is not installed properly? Maybe you have mod_security module in your Apache and it's blocking requests? Could be a lot of things. Nothing specific about Invoice Customization that should result in a 500 error Are the orders approved or not approved? If they are approved, the cron activates orders every 5 minutes. Is your cron job set up to run every 5 minutes? Never heard of the password being wrong, unless it was changed in Centova or Vesta after it was provisioned. Check the module log under Tools > Logs > Module.

You can't apply more to an invoice than the invoice is for. The remaining amounts are issued as a credit, not applied to the invoice.

You can remove it from the templates under /components/modules/cpanel/ I don't have explicit instructions, but it should be in a file ending in .pdt

This has to do with 3D Secure right? We are planning to add 3DS support to Stripe. Not totally sure all that is involved in making that happen yet, but it is on our radar and we'll be taking a closer look very soon.

If you remove the cpanel extended module directory from /components/modules/ does the page load? If that doesn't work, you may also need to remove the record from the modules table. Be sure to backup everything (files + database) first.

For reference, GoCardless docs are available at https://docs.blesta.com/display/user/GoCardless GoCardless is a non-merchant gateway, so there is no payment account associated within Blesta. You do need to set up a webhook in GoCardless, and the URL to the webhook is displayed in the GoCardless configuration under Settings > Company > Payment Gateways > GoCardless. I'm not totally sure if modifying the webhook endpoint URL in GoCardless will automatically make recurring payments work that were set up in another system, or if they would need to be re-created. It's worth a try.

Did you check your logs? ../logs_blesta/ (defined under Settings > System > General) You can also disable your cron job, enable errorReporting in your /config/blesta.php (Change from "0" to "-1") and then try running the cron manually after 5 minutes, either via CLI (preferred) or under Settings > System > Automation. Note any errors output, and whether any tickets were imported. Also note that your department defines also whether non-clients can open tickets. If a from address that's being imported does not match an existing client and you only allow existing clients to open tickets, then it will not be imported.

Were you able to save those settings? Is port 993 egress open at your Firewall on your Blesta server? Is your cron job set up and running? Is the automation task (Settings > Company > Automation > Plugin > Download Tickets) enabled and running?

There's a dropdown to set the language if you have multiple languages installed. Right now this can't be set as a URL parameter, but it's something we're considering. However, it probably wouldn't be difficult to check for a GET parameter and then set the language similarly to the way the dropdown works.

What modules specifically are you wanting?

Little late on the reply, but I like it it. Not a big fan of all the blue, but it does fit together well.

There is a "Report Post" link in the top right of every post, just mouse over the section and it should appear.

Follow the moving Blesta guide at https://docs.blesta.com/display/user/Moving+Blesta if you are moving Blesta. You do not change your system key, it must remain the same as generated on initial install or your installation will be irreversibly broken.

Nobody is deleting your tickets. I see a ticket from you, but it's not attached to any client account. Probably you emailed from a different address than we have on file for you and no match was found, or you weren't logged in to the client area when you opened the ticket, so it wasn't attached to your account. The ticket says that I have your Blesta admin login details? Where did you send those, are they in another ticket or??

Did you follow the moving Blesta guide? https://docs.blesta.com/display/user/Moving+Blesta CPU usage depends on what is happening. I don't recommend rate limiting resources for Blesta, if you are doing so it's possible your server killed or interrupted the cron while it was in the middle of something important. Most of the heavy lifting happens via cron.

That's not what I mean. I mean your cron job on your server should run to provision it. You are doing it through a web browser, which is making an HTTP request to the same server that is restarting Apache and dropping the connection. That's the issue here. The problem is that Blesta and Virtualmin are on the same server, and Virtualmin drops the connection when you do it in a browser. Let the cron job run on the server automatically, and it should work. You won't have this problem if the Virtualmin server is external to Blesta.