Add support for disabling plugins #4141
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Allows enabling and disabling plugins from within the UI.
Adds
Enable
/Disable
buttons to each plugin entry in the plugins setting page. Disabled plugins have their heading dulled. Enabling or disabling a plugin makes aReload UI
button appear next to theEnable
/Disable
button to prompt the user to reload the UI as needed (only the last enabled/disabled plugin shows this button).Disabled plugins will not have the css or javascript included when getting these from the server. Tasks for a disabled plugin will fail to run if triggered, and the tasks for disabled plugins are hidden in the UI. Hooks for disabled plugins are not run.