Jump to content

Search the Community

Showing results for tags 'domain module'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • General
    • News
    • The Lounge
  • Community
    • Pre-Sales Questions
    • Support
    • The Marketplace
    • Contribute
    • Show Off
    • Feature Requests
    • Bugs
    • Contests
  • Developer Corner
    • General
    • Extensions
  • BlestaStore's Forum
  • BlestaStore's BlestaCMS
  • BlestaStore's Resellers
  • BlestaStore's BlestaForums
  • BlestaStore's Promotions
  • CubeData's Official Announcements From CubeData
  • CubeData's Peer Support
  • CubeData's Resellers
  • ModulesGarden Club's Topics
  • Blesta Addons's Topics

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL








Found 1 result

  1. we have talked about this subject so many times ago and we think is the time to talk about it now . i have made a plan to make something special for my need and provide it to the cmmunity , but i have stack with some limitation and some lock of professional advanced skill and lock of time . so what i have do , first i have decided to make the domain manager as a module , and add the registrar as a components inside the module . the registrar wil have a : - json file to identify the name ,description, version ect ... - folder for API class - module.php (that file has the fields that will be used in the addrow in module + the rules validation ) - manager.php (that file will have the available functions for this registrar ) - package.php (that file will include the fields that will be shown in the package creation ) - maybe we can add more files for other uses . in the module manager , we add registrar as a row (addrow) , in the add row , it list all the registrar exist in components folder as a list , when we select a registrar it load the returned fields in module.php . in the package creation , when we select domain manager , it list the available registrar , when selecting the chosed registrar it can load the required fields by package.php (optional ) . in the client/admin side , we will have a standard function like , name-server, contacts, dns, forwarding , emails ... ect ... the tabs has a relation with the actions available in the registrar or simply if not available show a message of unavailability . so the idea is simple clients/admins tabs --- communicate with the module , the module forward the call to the registrar module . the registrar module return the response , the module show the response (success or errors) . with this way we have a centralized domain management, and we can maintain 1 module rather than multiple modules .we can add the registrars as we want and we can improves them without touching the module it self . the logic is nearly the same used in the gateways , we laod the gateway class inside the gateway model .
  • Create New...