Confluence 3.5 : Removing Malfunctioning Plugins
This page last changed on Mar 09, 2011 by bmallow.
Confluence goes to some lengths to prevent itself being unusable due to a problematic plugin. However, sometimes a plugin will manage to do this anyway. This page describes what to do if a plugin cannot be disabled or deleted from the Administration console (from Administration >> Plugins). Plugin Loading Strategies
Check these locations when troubleshooting plugin loading issues.
Deleting a plugin from the DatabaseTo remove a plugin from Confluence when Confluence is not running,
Disabling a plugin from the databaseTo disable 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>true</boolean> </entry> </map> Edit the value boolean to have false: <map> <entry> <string>com.atlassian.confluence.ext.usage</string> <boolean>false</boolean> </entry> </map> Deleting a Bundled PluginBundled plugins can be administered from the Plugins console from Administration >> Plugins. You can upload or disable them there. If you need to remove a bundled plugin, check to see if you have duplicates in the <confluence-home>/bundled-plugins or <confluence-home>/plugin-cache directory. Usually, the problem is that an old plugin is getting loaded along with the properly bundled one, but if you need to remove a bundled plugin, check Plugin loading strategies in Confluence. |
![]() |
Document generated by Confluence on Mar 16, 2011 18:31 |