Thanks Dan,
[QUOTE=IWorx-Dan;18578]Unfortunately the plugin documentation doesn’t exist yet because plugins were originally added as a system for integrating 3rd party software (like softaculous) and for custom paid plugins and not for “public” use. This stance has since changed but as a result we still don’t have any documentation :(.
[/quote]
No problem - just wanted to be sure I hadn’t missed something…
If you have a specific question about something you can always shoot us a support ticket that a developer can take a look at to try and help you out.
If there’s anything that stumps me I’ll take you up on that kind offer - there’s nothing I haven’t been able to work out so far.
(That’s more a tribute to the logical way the plugin system works than anything else…)
The example plugins that are there are a great resource and as you mentioned, the naming of controllers is consistent with how they are named in the API.
They are a great resource, and the consistent naming between API and plugin saved me a lot of “guessing” in the plugin I created.
Thanks again
Jim