-
Bug
-
Resolution: Fixed
-
Medium
-
None
-
4.2
-
None
NOTE: This bug report is for Confluence Server. Using Confluence Cloud? See the corresponding bug report.
Our official documentation for the Confluence like feature instructs users that they may disable the feature if they don't want to use it. This can be done by disabling the Like plugin from the UPM. (see http://confluence.atlassian.com/display/DOC/Likes+and+Popular+Content#LikesandPopularContent-Disablingthelikefeature)
However, for OnDemand users, because the plugin is bundled as a system plugin, users are not able to disable the plugin (in OnDemand, only users with System Administrator permissions are permitted to enable or disable 'system' plugins, and the System Administrator perm is only granted to atlassian support) (see http://confluence.atlassian.com/display/AOD/Restricted+Functions+in+Atlassian+OnDemand#RestrictedFunctionsinAtlassianOnDemand-Confluence).
There is already an existing feature in the UPM that allows the host product to 'override' a plugins listing from 'System' to 'User-Installed', so that users are able to enable and disable it. We should perform this override for the Like plugin, also.
- relates to
-
CONFCLOUD-25469 The Confluence Like plugin cannot be disabled in OnDemand instances
-
- Closed
-
- mentioned in
-
Wiki Page Loading...
[CONFSERVER-25469] The Confluence Like plugin cannot be disabled in OnDemand instances
Workflow | Original: JAC Bug Workflow v3 [ 2898191 ] | New: CONFSERVER Bug Workflow v4 [ 3002019 ] |
Workflow | Original: JAC Bug Workflow v2 [ 2790312 ] | New: JAC Bug Workflow v3 [ 2898191 ] |
Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: JAC Bug Workflow [ 2723267 ] | New: JAC Bug Workflow v2 [ 2790312 ] |
Workflow | Original: Confluence Workflow - Public Facing - Restricted v5 - TEMP [ 2397802 ] | New: JAC Bug Workflow [ 2723267 ] |
Workflow | Original: Confluence Workflow - Public Facing - Restricted v5 [ 2295449 ] | New: Confluence Workflow - Public Facing - Restricted v5 - TEMP [ 2397802 ] |
Workflow | Original: Confluence Workflow - Public Facing - Restricted v5.1 - TEMP [ 2231417 ] | New: Confluence Workflow - Public Facing - Restricted v5 [ 2295449 ] |
Workflow | Original: Confluence Workflow - Public Facing - Restricted v5 - TEMP [ 2190506 ] | New: Confluence Workflow - Public Facing - Restricted v5.1 - TEMP [ 2231417 ] |
Workflow | Original: Confluence Workflow - Public Facing - Restricted v5 [ 1924441 ] | New: Confluence Workflow - Public Facing - Restricted v5 - TEMP [ 2190506 ] |
Workflow | Original: Confluence Workflow - Public Facing - Restricted v3 [ 1717499 ] | New: Confluence Workflow - Public Facing - Restricted v5 [ 1924441 ] |
Description |
Original:
Our official documentation for the Confluence like feature instructs users that they may disable the feature if they don't want to use it. This can be done by disabling the Like plugin from the UPM. (see [http://confluence.atlassian.com/display/DOC/Likes+and+Popular+Content#LikesandPopularContent-Disablingthelikefeature])
However, for OnDemand users, because the plugin is bundled as a system plugin, users are not able to disable the plugin (in OnDemand, only users with System Administrator permissions are permitted to enable or disable 'system' plugins, and the System Administrator perm is only granted to atlassian support) (see [http://confluence.atlassian.com/display/AOD/Restricted+Functions+in+Atlassian+OnDemand#RestrictedFunctionsinAtlassianOnDemand-Confluence]). There is already an existing feature in the UPM that allows the host product to 'override' a plugins listing from 'System' to 'User-Installed', so that users are able to enable and disable it. We should perform this override for the Like plugin, also. |
New:
{panel:bgColor=#e7f4fa} *NOTE:* This bug report is for *Confluence Server*. Using *Confluence Cloud*? [See the corresponding bug report|http://jira.atlassian.com/browse/CONFCLOUD-25469]. {panel} Our official documentation for the Confluence like feature instructs users that they may disable the feature if they don't want to use it. This can be done by disabling the Like plugin from the UPM. (see [http://confluence.atlassian.com/display/DOC/Likes+and+Popular+Content#LikesandPopularContent-Disablingthelikefeature]) However, for OnDemand users, because the plugin is bundled as a system plugin, users are not able to disable the plugin (in OnDemand, only users with System Administrator permissions are permitted to enable or disable 'system' plugins, and the System Administrator perm is only granted to atlassian support) (see [http://confluence.atlassian.com/display/AOD/Restricted+Functions+in+Atlassian+OnDemand#RestrictedFunctionsinAtlassianOnDemand-Confluence]). There is already an existing feature in the UPM that allows the host product to 'override' a plugins listing from 'System' to 'User-Installed', so that users are able to enable and disable it. We should perform this override for the Like plugin, also. |