Confluence 4.1 Upgrade Notes

Below are some important notes on upgrading to Confluence 4.1. For details of the new features and improvements in this release, please read the Confluence 4.1 Release Notes.

On this page:

Upgrade Notes

Confluence Clustered reactivated

Please be aware that Confluence Clustered is now available again, following a brief hiatus after the release of Confluence 4.0.

Personal labels deprecated

The tab that displays personal labels in the user profile has been hidden in Confluence 4.1. We are planning to remove personal labels altogether from Confluence in a future release. The functionality for creating personal labels is still in Confluence, but we recommend that you stop using them. People can still see their existing personal labels by visiting the following URL:

CONFLUENCE-URL/users/viewmylabels.action 

Where CONFLUENCE-URL is the URL of your Confluence site.

For example: https://confluence.atlassian.com/users/viewmylabels.action

Legacy Crowd SSO Authenticator removed

For customers with Crowd SSO authentication who ever used Confluence 3.4.9 or earlier: Customers who were using the com.atlassian.crowd.integration.seraph.v22.CrowdAuthenticator in their seraph-config.xml must replace this with com.atlassian.confluence.user.ConfluenceCrowdSSOAuthenticator. This has been the default Crowd SSO authenticator since Confluence 3.5, so users who installed from scratch with Confluence 3.5 or higher are not affected.

Reduced functionality for JIRA Portlets macro

Upgrade notes updated in March 2012: In Confluence 4.1, it is no longer possible to add a JIRA Portlet macro via the Confluence macro browser. It is still possible to add the macro using wiki markup or by copying an existing JIRA Portlet macro. The macro still displays information correctly.

Plain text emails no longer available

Emails are now only available in HTML format, which allows for the display of images and formatted content, such as changes made and the full content of the updated page or blog post.

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:

  1. Before you upgrade, we strongly recommend that you back up your Confluence Home and other important directories and database. See the documentation on backing up your Confluence site. If you are using an external database, perform a database backup.
  2. If your version of Confluence is earlier than 3.5.x, then you should  upgrade to Confluence 3.5.x before upgrading to Confluence 4.1. There are several reasons for this:
    • There were major changes to user management and LDAP in Confluence 3.5.
    • From version 3.5, you'll be able to use our new automated Installer / Upgrader to move to 4.1. The Confluence 4.1 Installer does not support upgrading from earlier versions of Confluence than 3.5.x.
    • We recommend that any issues arising from the upgrade to version 3.5.x be fixed separately to those that may arise from upgrading to version 4.1. Please contact Atlassian Support for assistance.
    • 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.)
    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 from version 2.7.x to version 3.5.x, before upgrading to the latest version. For more details, please refer to CONF-11767.
    If your site contains links to a file system (for example [\\\C:\Foo\Bar\foobarpreso.ppt] these may break when upgrading to Confluence 4.2.x.  We recommend that you upgrade directly to Confluence 5.0.3. Refer to  CONF-23575 - Links to filesystem are lost after upgrade to Confluence 4.x or upon saving the page in the new editor Resolved  for more details. 
  3. Download the latest version of Confluence.
  4. 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 Answers.
  • 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.
RELATED TOPICS

Confluence 4.1 Release Notes

Was this helpful?

Thanks for your feedback!

Why was this unhelpful?

Have a question about this article?

See questions about this article

Powered by Confluence and Scroll Viewport