Confluence 3.3 Upgrade Notes
Below are some important notes on upgrading to Confluence 3.3. For details of the new features and improvements in this release, please read the Confluence 3.3 release notes.
On this page:
Upgrade Notes
End of Support for WebSphere, WebLogic, Resin, Internet Explorer 6 and Java Platform 5 (JDK/JRE 1.5)
As previously announced, we are no longer providing support for:
- IBM WebSphere (all versions) from this release onwards.
- Oracle WebLogic (all versions) from this release onwards.
- Caucho Resin (all versions) from this release onwards.
- Internet Explorer 6 from this release onwards.
- Java Platform 5 (JDK/JRE 1.5) from this release onwards.
Please see End of Support Announcements for Confluence for further details.
DWR Deprecation Notice
We have replaced DWR with XWork actions (returning JSON, implementing the Beanable interface). The DWR servlet still works, however the client-side JavaScript files are not embedded into pages anymore. Support for the client side Javascript proxies has been moved into the Confluence Legacy Web Resources plugin. This plugin is disabled by default.
If you need any of the following web resources you will need to enable the Confluence Legacy Web Resources plugin:
- DWR framework
- DWR Javascript proxies for label (add, remove, suggest) or editor operations (heartbeat, draft saving, editor preferences)
You will also need to make the following resource a required resource in your view template: legacy.confluence.web.resources:dwr-confluence
This will embed the DWR client-side JavaScript files in your plugin's view output.
Upgrade Procedure
Upgrade a test environment first
As always, please test your upgrades in your test environment before rolling into production.
If you are already running a version of Confluence, please follow these instructions to upgrade to the latest version:
- Before you upgrade, we strongly recommend that you back up your Confluence home directory and database. See the documentation on backing up your Confluence site. If you are using an external database, perform a database backup.
- If your version of Confluence is earlier than 3.2.x, then please read the Upgrade Notes Overview and the Upgrade Notes for each version of Confluence listed on that page. (There are hyperlinks to each one.) Also:
- If you are upgrading from 2.1 or earlier, please read the 2.2 release notes.
- If you are upgrading from 2.2 or earlier, you will need to upgrade to Confluence 2.7.x first, confirm the upgrade was successful, then upgrade again from version 2.7.x to the latest. For more details, please refer to CONF-11767.
- Download the latest version of Confluence.
- Follow the instructions in the upgrade guide.
Checking for Other Known Issues and Troubleshooting the Confluence Upgrade
After you have completed the steps required to upgrade your Confluence installation, check all the items on the Confluence post-upgrade checklist to ensure that everything works as expected. If something is not working correctly, please check for known Confluence issues and try troubleshooting your upgrade as described below:
- Check for known issues. Sometimes we find out about a problem with the latest version of Confluence after we have released the software. In such cases we publish information about the known issues in the Confluence Knowledge Base.
- Check for answers from the community. Other users may have encountered the same issue. You can check for answers from the community at Atlassian Community.
- Did you encounter a problem during the Confluence upgrade? Please refer to the guide to troubleshooting upgrades in the Confluence Knowledge Base.
- If you encounter a problem during the upgrade and cannot solve it, please create a support ticket and one of our support engineers will help you.
Useful Plugins
Before installing an add-on (also called a plugin) into your Confluence site, please check the add-on's information page to see whether it is supported by Atlassian, by another vendor, or not at all. See our guidelines on add-on support.
- Unable to render {include} The included page could not be found.