Confluence 4.0 : 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 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 <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.Bundled plugins are included in a zip of jars called atlassian-bundled-plugins.zip which is on the main Confluence classpath, in a resources directory - <confluence-install>/confluence/WEB-INF/classes/com/atlassian/confluence/setup . At Confluence startup, they are extracted and copied into the $CONFLUENCE_HOME/bundled-plugins directory, from whence they are loaded. To remove a bundled plugin (you shouldn't normally have to do this), remove the plugin from the atlassian-bundled-plugins.zip file and the bundled-plugins directory, otherwise Confluence will just put it back in place on the next startup. In versions later than 2.6, you'll have to recreate the .jar file (if the jar file is from the lib folder) or recreate the zip folder(if its in the classes folder). Bundled plugins can be upgraded or disabled.
If you need to remove a bundled plugin, check to see if you have duplicates in the 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 Sep 19, 2011 02:41 |