Re: Addons directory
Reply #1 –
mmm...I think it would make sense...
Re: Addons directory
Reply #4 –
Well, the direct file upload stuff is going down a very deep and dark rabbit hole.
But just having a central place for things does solve a lot of headaches, though it creates others. That's why I ended up having loadPluginSource, loadPluginTemplate and loadPluginLanguage trio of functions, whose first parameter is the plugin id. (The idea is that a plugin should neither know nor care what folder their files are in, inside Plugins/)
Re: Addons directory
Reply #7 –
Ah. I see - I misunderstood earlier.
That raises other interesting problems. By the way, when you say "enabled", is that practically equivalent with "installed"?
Re: Addons directory
Reply #8 –
In SMF terms, yes. The files are present, but the plugin is not active until it is enabled - it is at that point the hooks are added to the list and whatnot.
Note that during startup, the list is examined and if the plugin does not apparently exist, its hooks are not registered. Means that disabling a plugin in the last ditch case is as simple as renaming its folder if things have truly gone south.
The architecture really isn't pretty but it's proven effective in our experience.