New way addons are added to the system to make for easier management and uninstallation
-
Mark Krieger shared this idea 1 month ago
- Core System
- 1 Comment
0
Votes
Login to Vote
A recent need to uninstall an addon led me to this suggestion. There was of course no uninstall information, so I downloaded the newest addon installer and went folder by folder through the "core" system to delete each folder and file that had been installed.
That was necessary because while I had disabled that registrar module, other parts of the addon stayed active and messed with the WHMCS install.
It would be much better if WHMCS would have an addon system where there would be a root addon folder and each addon has a subfolder in it that contains the hooks/addons/modules/templates/includes... folders for that addon.
Delete the addon's folder, and every file is gone and no hunting around for remnant pieces anywhere in the "core". That would keep the core clean.
WHMCS could scan the paths on addon activation, and then add them to the include paths in a database entry.
For most existing addon installations, it should just change from dumping everything into the WHMCS root to putting an addon into /addons/addon_name folder.
That was necessary because while I had disabled that registrar module, other parts of the addon stayed active and messed with the WHMCS install.
It would be much better if WHMCS would have an addon system where there would be a root addon folder and each addon has a subfolder in it that contains the hooks/addons/modules/templates/includes... folders for that addon.
Delete the addon's folder, and every file is gone and no hunting around for remnant pieces anywhere in the "core". That would keep the core clean.
WHMCS could scan the paths on addon activation, and then add them to the include paths in a database entry.
For most existing addon installations, it should just change from dumping everything into the WHMCS root to putting an addon into /addons/addon_name folder.
2 Comments
Login to post a comment.
Thanks for submitting this idea.
Action Hooks and Template files for Addon Modules should be placed in the /modules/addons/$modulename/ directory as documented:
- https://developers.whmcs.com/addon-modules/hooks/
- https://developers.whmcs.com/addon-modules/client-area-output/
This sounds like the arrangement being requested here. Is that fair to say say?
Your documentation on Hooks for example at https://developers.whmcs.com/hooks/getting-started/ states "Hooks in WHMCS exist in the /includes/hooks/ directory. Alternately, they may be within a module (for more information, see Module Hooks)."
Which sounds like the preferred option is the hooks directory and the module placement is a secondary option for example. So many hooks for modules, templates, registrar modules end up in the hooks folder.
It's great that it is supported for modules to be fully contained (for hooks) already. How about templates and registrar modules? Am I missing any other addons in different places?
It would be great if your documentation for development would prefer fully self-contained addons and maybe deprecate non-core files in core folders?
Possibly support multiple hook files in a hooks folder in modules to make porting to the new structure easier?
It's just so messy and hard to troubleshoot to have custom files in the core structure.
CentralNIC for example at https://github.com/centralnicgroup-opensource/rtldev-middleware-whmcs/releases/tag/v26.0.0 has files in:
/includes/hooks
/modules/addons
/modules/registrars
/modules/servers
/resources
/templates