Allow plugins to be enabled, but not active yet #1804
Labels
Enhancement
For new feature suggestions that enhance Matomo's capabilities or add a new report, new API etc.
wontfix
If you can reproduce this issue, please reopen the issue or create a new one describing it.
Milestone
Comments
|
Unless I'm mistaken, I think that the current plugin design can accomodate this. For example, until your plugin is configured (settings), you would just return false in the hooks that won't work unless the plugin was configured. I don't think we want to allow redirecting users to the settings page after enabling the plugin as this would be confusing. Maybe a generic solution would be, like wordpress, to add a 'messaging' system where plugins could write yellow messages at the top of the screen (notification messages). |
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
From kamerman's comment:5 of #1552:
Last minute idea - I'm developing a plugin that won't work unless its settings are properly configured. Maybe there is a good way to send a user to the plugin's admin page when they attempt to activate it and only commit the activation if the plugin settings are configured successfully. A framework for this type of activity may be helpful for other plugins that require some settings to function properly. Many examples can be found in WordPress.
For more complex/involved configurations, plugins should continue to use Piwik_AddAdminMenu().
For lightweight configurations, we could add a "setup" icon that opens a popup dialog, or use an accordian widget to expand the settings inline. (Examples: Trac and Hudson)
The text was updated successfully, but these errors were encountered: