Confluence Docs 3.0 : Removing Malfunctioning Plugins This page last changed on Sep 02, 2009 by ivan@atlassian.com. 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. ### Plugin Loading Strategies Read through Plugin loading strategies in Confluence. Determine where your plugin is loaded. The usual options are: The PLUGINDATA table on the database The <confluence-home>/bundled-plugins folder The <confluence-home>/plugin-cache folder The <confluence-home>/plugins-osgi-cache folder The <confluence-home>/plugins-temp folder The <confluence-install>/confluence/WEB-INF/lib folder (deprecated approach) Check these locations when troubleshooting plugin loading issues.
| Check the How to display classpath utility for tips on what's loading, and the Knowledge Base Article on plugin malfunctioning.
2. ##### Deleting a plugin from the Database To remove a plugin from Confluence when Confluence is not running: Connect to the Confluence database. Run the following SQL statement in your database:
       select plugindataid, pluginkey,filename,lastmoddate from plugindata;
3. After you have found the plugindataid for the offending plugin, please run the following:
       delete from plugindata where plugindataid='XXXXXX';
where XXXXXX is the plugindataid value. Restart Confluence. ##### Deleting a Bundled Plugin Bundled 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 `<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 Nov 05, 2009 23:27