Certain add-ons are disabled but cannot be re-enabled through the UI
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
You may encounter add-ons or their sub-components which are disabled and cannot be re-enabled, as there will be no "enable" button for them in the UI.
Cause
These add-ons are disabled in the database.
Solution
Re-enable the desired add-ons by changing their status directly in the database since they cannot be re-enabled through the UI.
To enable the add-on in the database:
Run the following query on your Confluence database:
select BANDANAVALUE from BANDANA where BANDANAKEY = 'plugin.manager.state.Map';This will return a value like:
<map>
<entry>
<string>com.atlassian.confluence.ext.usage</string>
<boolean>false</boolean>
</entry>
</map>
Copy the contents of the BANDANAVALUE column to a text editor.
To re-enable the plugin, change the boolean value for the add-on in question to true, then issue the following UPDATE statement to commit these changes:
update BANDANA set BANDANAVALUE='(the entire text from <map> to </map>)' where BANDANAKEY='plugin.manager.state.Map';
Note: you will be updating BANDANAVALUE with the entire contents of the text in your text editor, from <map> to </map> including portions of text that you did not update.
Always make a full backup of the database and be prepared to roll-back before making direct edits to the database.
Restart Confluence for this change to be picked up.