Jump to content

activa

Members
  • Posts

    737
  • Joined

  • Last visited

  • Days Won

    14

Posts posted by activa

  1. Use a module for service management, and a plugin for just about anything else. While a plugin could potentially be created to handle service management, it wouldn't be able to provide the same level of service management as a module in Blesta, unless you completely recreated the entire system's service management through your plugin. For example, Blesta wouldn't tell the plugin that it's adding a service until it has already been added, so any validation/requirements the plugin may impose would be ineffective.

     

    If you're just wanting to add a general module that provides server management, a new module sounds like the way to go.

    your answer is just for the OP question . what about the other questions , use two module to manage 1 service ?

  2. Ok.

    Thought that may not be always the case, because of the ifSet()

     

    ==

     

     

     

     

    You did include your class name in the callback URL, so that the request gets routed to your class?

     

    As in:

     

    $callbackurl = Configure::get("Blesta.gw_callback_url").Configure::get("Blesta.company_id")."/".strtolower(get_class($this))."/";
    

     

     

    In case you are not able to find your problem, you may also able to use Paypal Express through our Omnipay module.

     

     i will check it just for inspiration , because we need a separate gateway for checkout . and we will adding the incontext feature checkout later .

  3. i think Blesta should merge this two module and my module (cpanel reloaded) in just one module . that is the best option .

     

    if blesta accept i can begin for upgrading the core module to add more option from the extended module .

     

    that way is easyfor blesta to update and enhaced just one module .

×
×
  • Create New...