The Universal Plugin Manager (UPM) provides you with a powerful and user-friendly interface to manage your plugins. The Universal Plugin Manager is a system plugin that allows you to perform common plugin tasks, such as:
- Enabling/disabling plugins and their plugin modules.
- Installing new plugins.
- Configuring advanced plugin options.
- Finding out-of-date plugins and updating them.
- Checking the compatibility of your installed plugins against newer versions of the application.
Through the UPM you can interact with the Atlassian Plugin Exchange (formerly the Plugin Exchange). You can use UPM to browse available plugins for your application. You can try or buy any of these plugins with a single click without ever leaving your application.
The Universal Plugin Manager (UPM) 2.0 is available for number of Atlassian applications. Currently, the UPM 2.0 version is not bundled with any Atlassian application. Existing applications contain older versions of the UPM. If you want the functionality described in this documentation, you should upgrade your UPM to 2.0. The plugin's page on the Atlassian Marketplace (formerly Plugin Exchange) lists the latest compatible applications. |
Read more about the Universal Plugin Manager in the topics linked below:







5 Comments
Hide/Show CommentsJan 04, 2011
Anonymous
A useful comment here could be which sites this plugins tries to reach so i can allow the internal iptables protecting our test env to reach the internet sites it needs. Does such a list exist?
Mar 21, 2011
Khang Yeen Lee
Please also include upgrade guide for this plugin. I migrated from 3.4.2 to 3.5 but the UPM is still running at 1.2.4. Can't seem to find anyway to upgrade it to 1.3.1. Help please. Thanks.
Mar 23, 2011
Anonymous
I have the exact same problem. I'm working with support now. When I upload the 1.3.1 jar file, it says I need to restart Confluence. So I do, and it STILL says I need to restart Confluence...
Mar 24, 2011
Anonymous
Can you please include the link to your support ticket? Thanks.
Jun 08, 2011
Brett Ryan
Unfortunately it appears there is a bug in the UPM that after the upgrade occurs confluence to think the UPM hasn't been upgraded on a restart. Clicking the x will clear the message and tell you that the upgrade was aborted, however, if you check and confirm with a restart, it in fact was upgraded to 1.4.
Thus it appears this is just a bug in the way the UPM detects if it was upgraded or not.
Add Comment