Leaderboard
Popular Content
Showing content with the highest reputation on 02/03/2014 in all areas
-
Thanks for the steps to duplicate. I've fixed this in CORE-1032 for v3.1.1. If you want to fix this yourself, you can update the following files: Update /app/views/admin/default/admin_clients_addservice_confirm.pdt (line 76) and change: if ($this->Html->ifSet($addon->package_options && $this->Html->ifSet($addon->configoptions))) { to: if ($this->Html->ifSet($addon->package_options) && $this->Html->ifSet($addon->configoptions)) { You may receive a separate error as well, that you can fix by updating /app/controllers/admin_clients.php (line 4137) and changing: $addon->package_options = $this->PackageOptions->getByPackageId($addon->id); to: $addon->package_options = $this->PackageOptions->getByPackageId($addon->package_id);1 point
-
Since the issue is recurring, it sounds as if you have a larger issue, possibly an error occurring when the cron executes up to that point. Since you don't see the link to clear the task, you should delete this task from the log_cron table and run the cron manually through the admin interface. You should be able to run the following query and then delete all of the results. It usually goes without saying, but you should backup the database before making manual changes. SELECT * FROM `log_cron` WHERE `run_id` !=0 AND `end_date` IS NULL ORDER BY `start_date` DESC; Then go to [settings] -> [system] -> [Automation] and run the cron manually. If there is an error, you should see it there, and then we can come up with a solution.1 point
-
A link to clear a task will appear next to it on the Automation page if Blesta determined that the task has stalled. It sounds like: the task was still actually running the cron had not yet finished running other tasks in the same group or you had another issue that prevented the cron from finishing Manually updating the database to clear this problem is not necessary, as you can do so through the interface, as long as you don't encounter one of the above 3 conditions.1 point
-
I think this is the reason it currently works this way.1 point
-
If you can retrieve the packages via the API in Blesta v2.5, then I'm not sure why it's not working in v3. However, I don't think this action is logged. We would need to know what the response is from the server when attempting to fetch the packages to see what the cause may be. If you can update a file to add in logging, then please update /components/modules/cpanel/cpanel.php (line 1521) and change: return $this->ArrayHelper->numericToKey($this->Json->decode($api->listpkgs())->package, 'name', 'name'); to: $this->log($module_row->meta->host_name . "|listpkgs", null, "input", true); $result = $this->parseResponse($api->listpkgs()); if (!$result || !property_exists($result, "package")) return array(); return $this->ArrayHelper->numericToKey($result->package, "name", "name"); Then, go to add/edit a cPanel package, and then check the Module Logs. Let us know what output is shown.1 point
-
Thanks, I've added this as CORE-1031 to look into it.1 point
-
It's scheduled for v3.2, but may get pushed back.1 point