Download
2015-02-26, 00:30:54
Tell me about it, I can revamp extend when 3.4 is released probably.
3.4 will allow users to modify order, but plugins themselves ( again catch 22 ) is a bit harder to engineer , I can maybe add a priority arguments to register_plugin(), and sort by that, or add an argument for an array of dependencies, plugin id and version, but plugin id is hard to nail down, we do not do a good job keeping them unique in extend, also the issue of not knowing anything but filename before we load a plugin other than relying on the api, we would need plugins to have some kind of manifest or file header to parse before including it.
And then use some intelligent looping through all plugins dependencies and using a logical ordering based on that, however it can still fail if there are cyclical dependencies. So a core solution is difficult, a specific use case and user one is much easier to manage, hence the GSPLUGINORDER, maybe i can cherry pick that into 3.3.6
another idea is to disable special pages, and having extras load it itself as a dependency, problem is this changes the relative include path, including from an include presents other interesting issues in php, but might be worth looking into, plugins basically have to be included in global scope also, since we still use globals for alot.
3.4 will allow users to modify order, but plugins themselves ( again catch 22 ) is a bit harder to engineer , I can maybe add a priority arguments to register_plugin(), and sort by that, or add an argument for an array of dependencies, plugin id and version, but plugin id is hard to nail down, we do not do a good job keeping them unique in extend, also the issue of not knowing anything but filename before we load a plugin other than relying on the api, we would need plugins to have some kind of manifest or file header to parse before including it.
And then use some intelligent looping through all plugins dependencies and using a logical ordering based on that, however it can still fail if there are cyclical dependencies. So a core solution is difficult, a specific use case and user one is much easier to manage, hence the GSPLUGINORDER, maybe i can cherry pick that into 3.3.6
another idea is to disable special pages, and having extras load it itself as a dependency, problem is this changes the relative include path, including from an include presents other interesting issues in php, but might be worth looking into, plugins basically have to be included in global scope also, since we still use globals for alot.
