Jump to content

Tyson

Blesta Developers
  • Posts

    3,638
  • Joined

  • Last visited

  • Days Won

    241

Everything posted by Tyson

  1. Every service option should have a "Name". Did you not enter one?
  2. Tyson

    Suspend Error

    Do you have multiple languages installed for Blesta? The Service Suspension email was never sent out previously to v3.0.3, and previously had placeholder text/tags. After installing/upgrading to v3.0.3, this email template was updated, but only for English, US. You'll need to update this template in other languages accordingly.
  3. The Plesk module creates a new "customer" account in Plesk for each service ("subscription") you create--so this wouldn't be a bug as it is intended to work this way. As for your error, it sounds to me like you're receiving it because your service plan in Plesk has already reached it's max domain limit, and Plesk simply cannot add anymore. Check your service plan limitations in Plesk.
  4. Tyson

    Release 3.0.3

    Some people are still having a few issues with the module related to some other fields.
  5. Tyson

    Routes

    The patch contains all patch versions since 3.0.0, hence the name "blesta-3.0.0-3.0.3".
  6. Tyson

    Release 3.0.3

    I should mention that the Service Suspension email template was previously never used, and contained placeholder text and tags. When patching, the English, US version of this template will be updated. Be sure to adjust the template content as suitable for your company.
  7. I was going off of yours and CubicWebs previous comments mentioning user_id, which is the value of $logged_in. However, Transactions::getTotalCredit() requires the client_id, and so you must first determine the client by fetching them via Clients::getByUserId().
  8. Yes, $this->uses() is available to controllers, which is where models should be loaded--not from views. While you can get away with it by calling the Loader directly, doing so partially negates the logical separation of business logic and presentation in the MVC design pattern. Generally speaking, when your solution goes against the design pattern you're working within, it's a good idea to rethink your approach. I'm not sure why you opted to not use the API, but core files are included in our patches and updates, which will overwrite your custom changes if you are not keeping record of them and merging file content accordingly.
  9. This part happens to be the user ID: <?php if ($this->Html->ifSet($logged_in)) { ?> i.e. $this->Transactions->getTotalCredit($logged_in, "GBP") There is no explicit client information set to the structure, so if you're a staff member logged in as the client, then you would be using the wrong user ID in this case, but it should work fine for clients themselves. Alternatively, you could check to see if the staff is logged in as the client, and simply not display the credit section altogether. i.e. <?php if ($this->Html->ifSet($logged_in, false) && !$this->Html->ifSet($staff_as_client, false)) { ?> As for <div id="credit">Credit: <?php print_r( money_format('£%i', $this->Transactions->getTotalCredit(1, "GBP"))); ?></div> Is there any particular reason you're not using the CurrencyFormat helper? FYI, our future implentation of credits in the client interface will be much different than this.
  10. That'd do it. Glad you were able to figure it out though.
  11. Since this is an improvement, and not a bug, I'll close this thread. CORE-126 is assigned tentatively for v3.3.0 to allow the content of a last row to be removed.
  12. The first row is used to generate additional rows, so it's necessary to not remove it from the page. We have a task somewhere to just remove the content of the row in this case, but it's rather low priority, and would affect several locations where this add/remove row is used. In the meantime, it's equivalent to add a new row and then remove the other row with content in it.
  13. Looks like you have an unused $module_id (probably remnants from testing?). And the group on packages.id is extraneous, as Packages::getPackages() already groups on this field. But otherwise looks good.
  14. You don't need to delete the log. It will try again 6 hours from the last time it failed, and then it will be back on its normal schedule. We plan to have a page that lists failed tasks, why (if available), with an option to retry them. This is part of a 2-step process, of which the first step was to at least tell you that something is not running correctly by way of the System Status plugin.
  15. Tyson

    Tickets Problem

    What version of PHP and MySQL are you running?
  16. I think the problem is that the service's module_row_id is invalid, as it should be an integer representing the module row of the module the service was created for. It seems like one of the following may have occurred when you created the service: You didn't set a module_row_id The package didn't have a valid module_row set (I see it's 0 above) The module you're using did not return the module row when fetching it based on the package module group in Module::selectModuleRow() Looks like #3 would be why.
  17. If you only have one row, it will not be removed.
  18. Has anyone been able to duplicate this in sandbox mode with a sandbox account?
  19. Some cron task has failed to complete recently. To see which tasks are failing, you can check the logs for them: SELECT * FROM `log_cron` WHERE `run_id` !=0 AND `end_date` IS NULL ORDER BY `start_date` DESC; Check the `run_id` with the `cron_task_runs`.`id`, and then the `cron_task_runs`.`task_id` with `cron_tasks`.`id` to determine the name of the cron task that is actually failing.
  20. Check your filesystem, and make sure that /uploads/1/download_files/ exists and is writable. The Dowload Manager saves files into that directory, but the permissions may not be correct.
  21. This issue was already brought up in the beta, but unfortunately the friendly names for the templates are not available via the SolusVM API, so this is not a bug with Blesta, but rather a limitation of the SolusVM API. Until they support this, there's nothing we can do.
  22. Make sure the uploads directory is writable, as defined under [settings] -> [system] -> [General] -> [basic]. It should contain the absolute path to that directory.
  23. Tyson

    Api Issue

    The documention is correct, as my link was to the source documentation, not the API SDK documentation which requires the use of key/value pairs in order to explicitly map them to the appropriate method call parameters.
×
×
  • Create New...