Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-11407

Mark core plugins as system plugins to prevent them from being disabled by administrators

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Medium Medium
    • 2.9
    • None
    • None

      Currently, not all core plugins are marked as system and so they can be disabled. Plugins can be designated as "System" by adding a flag to the plugin manifest file. To do this, system=true should be added to the top-level atlassian-plugin element of the manifest xml file.

            [CONFSERVER-11407] Mark core plugins as system plugins to prevent them from being disabled by administrators

            Andrew Lynch (Inactive) added a comment - Reviewed by Chris in https://svn.atlassian.com/privateeye/cru/CR-744 .

            Implemented in antistatic branch.

            Tim Moore [Atlassian] added a comment - Implemented in antistatic branch.

            we think the only core plugin that isn't labeled system is the "Core Path Converters". so once i change that in confluence, i'll close this issue

            Cheryl Jerozal [Atlassian] added a comment - we think the only core plugin that isn't labeled system is the "Core Path Converters". so once i change that in confluence, i'll close this issue

            Definite +1 on moving non-system plugins out of core and into bundled

            Charles Miller (Inactive) added a comment - Definite +1 on moving non-system plugins out of core and into bundled

            hmm, so maybe system is currently used as it should be. i think a quick audit would be good since we'd like to change the default loading of any non-system core plugins to be bundled (move them out of the confluence source), and it'd be nice to be certain of which plugins should be system and stay as core before that.

            Cheryl Jerozal [Atlassian] added a comment - hmm, so maybe system is currently used as it should be. i think a quick audit would be good since we'd like to change the default loading of any non-system core plugins to be bundled (move them out of the confluence source), and it'd be nice to be certain of which plugins should be system and stay as core before that.

            We should only mark plugins as system if they are necessary for the system to function correctly. This is the heuristic we've used so far in deciding whether to make a plugin a system plugin or not. Otherwise, customers like having the ability to turn features off if they don't want to use them, or want to replace them with some equivalent plugin they think works better.

            This issue should either be repurposed to be an audit of existing plugins to see which should be system or not, or should be closed as Invalid.

            Charles Miller (Inactive) added a comment - We should only mark plugins as system if they are necessary for the system to function correctly . This is the heuristic we've used so far in deciding whether to make a plugin a system plugin or not. Otherwise, customers like having the ability to turn features off if they don't want to use them, or want to replace them with some equivalent plugin they think works better. This issue should either be repurposed to be an audit of existing plugins to see which should be system or not, or should be closed as Invalid.

              christopher.owen@atlassian.com Christopher Owen [Atlassian]
              cjerozal Cheryl Jerozal [Atlassian]
              Affected customers:
              0 This affects my team
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: