Public bug reported: Once a new plugin is installed via the Administration UI it can be enabled and disabled or have config set. It'd be nice to be able to set a restriction on some plugins that they can't be enabled unless certain configuration is set up correctly.
This would be primarily to avoid incorrect system configuration resulting in enabled but broken plugins. Especially when thinking about contrib plugins that might require third party software to be installed on the server and configured in Mahara. ** Affects: mahara Importance: Wishlist Status: New -- You received this bug notification because you are a member of Mahara Contributors, which is subscribed to Mahara. https://bugs.launchpad.net/bugs/730727 Title: plugin enable/disable to rely on correct plugin configuration Status in Mahara ePortfolio: New Bug description: Once a new plugin is installed via the Administration UI it can be enabled and disabled or have config set. It'd be nice to be able to set a restriction on some plugins that they can't be enabled unless certain configuration is set up correctly. This would be primarily to avoid incorrect system configuration resulting in enabled but broken plugins. Especially when thinking about contrib plugins that might require third party software to be installed on the server and configured in Mahara. _______________________________________________ Mailing list: https://launchpad.net/~mahara-contributors Post to : mahara-contributors@lists.launchpad.net Unsubscribe : https://launchpad.net/~mahara-contributors More help : https://help.launchpad.net/ListHelp