I've thought a little bit about the problem, that currently all plugins are always enabled; the web console has no way to disable a plugin. Apart from possible "security" problems (you don't want to give full control to users in some cases), some plugins are only relevant for development and shouldn't be used in production.
What about using a simple configuration resource which is included like other stuff (css files etc.) through an optional import. The configuration file could be a simple property file, which defines the default value for unknown plugins and then might have a line per plugin like DEFAULT=disabled PLUGIN_ID_1=enabled PLUGIN_ID_2=disabled ... Currently the label (I think) is used as the plugin id - which might be something we need to change as well. I think this should be a resource in the bundle (or an additional bundle). Using something like the ConfigAdmin is too easily changeable. WDYT? Carsten -- Carsten Ziegeler [email protected]
