Jump to content

Jonathan

Members
  • Posts

    409
  • Joined

  • Last visited

  • Days Won

    27

Posts posted by Jonathan

  1. Presently there's no way to access the suspension reason within the suspendService() method in modules.  Looking at the source in app/models/services.php this is because the updated suspension_reason isn't set until after suspendService() runs, thus the suspension_reason field in the $service object is incorrect (ie it's the old/previous reason, if any).

    It would be great to be able to pass this value along to modules which may have their own methods of notifying customers, taking actions, etc.

  2. 8 minutes ago, Charlie said:

    Is this being maintained?

    Yes and no.  There's not active work being done on it right now but also there are no known major bugs, but it could use some TLC.  I've been inundated with work as of late on some big datacenter moves so I've not given it any love in a while.  As far as I know @NETLINK is still around as well.

    I've been in talks with Blesta for a while on sponsoring them (read, paying them) on adding some features to it and taking the whole thing under their wing so to speak but they've not been very responsive.

  3. Some modules take several minutes to activate a service and they don't create a lock of any sort when starting activating to prevent another process, be it cron or human, from duplicating the action.

    I've seen multiple instances of an order getting entered, a staffer clicking "activate" on the service to go ahead and provision it and either the cron was already running, or starts running while the staff-induced activation is still running and two services are setup, two activation emails are sent, but only one record exists in blesta so you end up with a totally orphaned service.

    A simple fix for this is to use locks in the database during provisioning.

  4. 3 minutes ago, mukesh said:

    i am using 1.8.4

    and there no response from page just waiting shown in left side in bottom......

    and something wrong is replay by cpanel admin team so i shared you there reply

    I need to know what page you were getting that error on about link_buttons.  All errors I knew of related to that were fixed in 1.8.4.

    The "Audit Domains" and "Sync renew dates" pages are very heavy on the API and if you have low values for PHP timeouts it's quite possible the pages will simply fail to function.  Sadly to improve these pages I need help from Namesilo and thus far they've refused to improve their API in a way to let me make the page more efficient.

  5. On 10/12/2018 at 9:23 PM, Panfilo said:

    Is anyone running this on Blesta 4.3.2 and php7? I currently get 

     Something went wrong.

    Undefined variable: link_buttons

     

    When i enable it try to 'manage' it. Any help would be appreciated. Thanks

    What page do you get this on?  Are you on version 1.8.4?

  6. On 11/10/2018 at 4:31 AM, mukesh said:

    after this domain not working i try create new api and use it.

    then new api not updating. 

     

    I tried enabling error reporting on blesta config file at that time I received the following error:

    
    Something went wrong.
    
    The maximum execution time of 30 seconds exceeded

     

    It almost sounds like you might have a firewall blocking communication with the Namesilo API.

  7. 1 minute ago, Blesta Addons said:

    This will lead to a massive change in Blesta, unless they will make a back-award capability . already exist a post about it, and  a use has posted a prof of concept how to integrate it in blesta .

     

    No it wouldn't, since it uses similar syntax that's what really matters.  Blesta on the back-end would have some work to do but when changing libraries that will always be the case.  If it can be done with little to no impact to end users and how their templates are built then it can be done without customers noticing since templates wouldn't have to be updated.

  8. 9 minutes ago, Tyson said:

    The h2o library is attempting to write it to a random directory. The user it's running as likely doesn't have write permission, and so it falls back to the system's temp directory.

    It's possible a cache directory could be specified when loading the h2o library, which may work around it. This isn't the first php 7 issue with this library though. It's dated and I'd like to replace it.

    Permissions should not be an issue unless it's trying to write to something based on / perhaps instead of it's current working directory.

    If you do replace it, try to stick with something based on Jinja2 like h2o is.  Jinja2 native in Python is by far the best template engine/library I've ever used hands down.

  9. 16 minutes ago, Tyson said:

    php 7.1 added an error notice when calling tempnam in which it falls back to using the system's temporary directory. That will be displayed if error reporting is enabled.

    Do you know where it would be trying to write to that's failing causing the fallback and the notice?  This occurs on stock Blesta with all permissions proper and required modules present so it seems like something needs to be adjusted in the code.

×
×
  • Create New...