Confluence goes to some lengths to prevent itself being unusable due to a problematic add-on. However, sometimes an add-on will manage to do this anyway. This page describes what to do if an add-on cannot be disabled or deleted from the administration console (from Administration > Manage Add-ons). 

(warning) The information on this page does not apply to Confluence OnDemand.

Add-on Loading Strategies

  1. Read through Plugin loading strategies in Confluence.
  2. アドオン ファイルの場所を確認します。通常は次の場所にあります。
    1. The PLUGINDATA table on the database
    2. <Confluence ホーム>/bundled-plugins フォルダ
    3. <Confluence ホーム>/plugin-cache フォルダ
    4. <Confluence ホーム>/plugins-osgi-cache フォルダ
    5. <Confluence ホーム>/plugins-temp フォルダ
    6. The <confluence-install>/confluence/WEB-INF/lib folder (deprecated approach)

アドオンの読み込みの問題のトラブルシューティングを行うときにはこれらの場所を確認します。

Check the How do I display the Confluence System Classpath? FAQ and the Knowledge Base Article on plugin loading problems for more information on troubleshooting add-on loading issues.

Deleting an add-on from the Database

To remove an add-on from Confluence when Confluence is not running,

  1. Confluence のデータベースに接続します。

  2. データベース内で次の SQL ステートメントを実行します。

    select plugindataid, pluginkey, filename, lastmoddate from PLUGINDATA;

  3. 問題のあるアドオンの plugindataid 値を見つけたら、次のように実行します。

    delete from PLUGINDATA where plugindataid='XXXXXX';

    ここで、XXXXXX が plugindataid 値です。

  4. Confluence を再起動します。
Disabling an add-on from the database

To disable the add-on in the database,

Confluence のデータベースで次のクエリを実行します。

select BANDANAVALUE from BANDANA where BANDANAKEY = 'plugin.manager.state.Map'

次のような値が返されます。

<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>
バンドルされたアドオンの削除

バンドルされたアドオンは、アドオンの管理ページ内のアプリケーションの管理コンソールで管理できます。ここで、アップロードや無効化を行えます。

Bundled add-ons are included in a ZIP archive of JAR files 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 add-on (you shouldn't normally have to do this), remove the add-on 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 add-ons can be upgraded or disabled.

If you need to remove a bundled add-on, 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 add-on is getting loaded along with the properly bundled one, but if you need to remove a bundled add-on, check Add-on loading strategies in Confluence.

  • ラベルなし

Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 2.5 Australia License.