Leaderboard

Yes this seems to have worked there was an entry to confirm a cpanel password, I deleted and seems to be working now. Thank you very much Paul for the help.

It sounds like you may have pending service changes that are unable to be processed for whatever reason. Take a look in your service_changes table. You may need to remove any items that are in here as they are unable to be processed. If you do so, be sure to back it all up first.

after i have see the video, i prefer this redirect to remain in the core .

It'll work on Windows. Here's an example of setting up a scheduled task in Windows to run the cron for Drupal. https://www.drupal.org/docs/7/setting-up-cron-for-drupal/configuring-cron-jobs-with-windows You'd just change the path to be that which you mentioned (https://sub.domain.com/cron/?cron_key=PUT_HER)

I would highly recommend not modifying existing tables. Plugins are designed to be able to create or modify their own tables, but modifying core tables could prove very problematic. In terms of tying into existing functionality, you might look at Event Handlers also known as hooks. Tying into the Invoices.add event, would allow you to edit an invoice right after it's created and add additional line items or make other modifications to it before it's emailed out. If you need to display additional information on an invoice that's not there now, or can't be added by modifying an existing invoice, you should create your own tables for this data. It then may be necessary to create a custom invoice template that one could use instead of the default, that could fetch the information from those new tables for display.

Here's a basic rundown of importing cPanel accounts manually https://docs.blesta.com/display/user/cPanel#cPanel-ImportingcPanelAccounts

Indeed! I did that but obviously managed to forget the file inside models/. So now i was able to install! Thx!

Paul's suggestion was to run it manually so you can view the cron output to possibly identify an error with the task completing properly. If there is an error, it will give some insight into where to look next to resolve the task hanging.

Yes worked perfectly, set at 45 seconds, this I believe should be fine. Thanks again Paul, this helped me a lot, much appreciation. Maybe in future releases there could be a setting for this in Blesta to turn off or to adjust the time. Thanks again

Is it actually running that long? Do you see the process running on your server? Or does it hang, and get reset after 6 hours? I would suggest disabling your cron job, and enabling error reporting and debugging and running it manually when it's scheduled to run next. To enable error reporting, edit /config/blesta.php and change **Configure::errorReporting(0);** to **Configure::errorReporting(-1);** You may also wish to enable System Debug. To do so, change **Configure::set("System.debug", false);** to **Configure::set("System.debug", true);** It's a good idea to change these settings back when you are done.

We only moved over to Blesta in April as soon as v4.0 was released and we put this on PHP7. We've had no issues so far, all seems to be working very well and worth the switch from an old version fo WHMCS we used to use.