Documentation for Confluence 5.4.
Documentation for Confluence OnDemand and earlier versions of Confluence is available too.

Skip to end of metadata
Go to start of metadata

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

On this page:

Upgrade Notes

Checking for compatible plugins before upgrading

Before upgrading to Confluence 4.2, please consider the plugins that are essential for your installation, and use the plugin upgrade check to see whether there is a compatible version of those plugins available for Confluence 4.2.

In particular, the implementation of quick comments required some significant changes to the editor’s initialisation code. This will have consequences for some Confluence plugins. Details are in this blog post: JavaScript Changes Required for Confluence 4.2 Compatibility.

Disabling notification of signups

This release includes an automatic notification, sent by email to all administrators, each time someone signs up to the Confluence site. This notification is part of the feature that allows you to invite people to sign up via a URL, and to set your signup mode to public or private. See the documentation.

The notification is enabled by default on the first upgrade to Confluence 4.1.9 or later.  If you are upgrading to Confluence 4.2 from Confluence 4.1.7 or earlier, you may want to disable the notification after upgrading, especially if you allow public signup and are expecting a large number of signups.

To disable the notification:

The email notification includes a link to change notification settings. Alternatively, follow these steps:

  1. Click Add Users on the dashboard.
    Or take the longer route: Choose the cog icon  at top right of the screen, then choose Confluence Admin. Click UsersAdd User.
  2. Remove the tick from Notify administrators when users sign up.

Configuring the Recommended Updates notification

Confluence now sends a regular email report to subscribers, containing the top content that is relevant to the person receiving the message. By default Confluence will send a weekly update to all users, except under these conditions:

  • If you have public signup enabled, the Recommended Updates email notification is turned off by default.
  • If you are connected to LDAP and a user has never logged in to Confluence, that user will not receive the Recommended Updates notification.
    (warning) Due to a bug in Confluence 4.2, 4.2.1 and 4.2.2, the Recommended Updates email notification may be sent to all LDAP Confluence users, whether they have logged in or not. The problem is tracked on this issue: CONF-25213 - Customers report that the recommended updates email goes to ALL LDAP users whether logged in or not Resolved The problem will be fixed in Confluence 4.2.3. Until then, you may wish to disable the notification as described in the next paragraph, if your Confluence site is connected to a large LDAP user base.

You can turn off the Recommended Updates notification, or change its settings for the site. See Configuring the Recommended Updates Email Notification. Confluence users can choose their personal settings, which will override the defaults. See Subscribing to Email Notifications of Updates to Confluence Content.

Disabling the new 'Popular' tab on the dashboard

In some environments, you may prefer not to display the new 'Popular' tab on the dashboard. For example, if your wiki allows only a small group of people to log in and contribute content or comments. Then the tab may not be relevant to you.

To prevent the tab from appearing, you can disable the relevant plugin module. You need System Administrator permissions to do this. Go to the Dashboard Macros plugin (see Configuring add-ons ), click Manage plugin modules and disable the Popular Tab module.

Advance notice: End of support for DB2 in Confluence 4.3

We are planning to end support for DB2 in Confluence 4.3. See End of Support Announcements for Confluence.

Advance notice: Removal of JIRA Portlet macro in Confluence 4.3

The JIRA Portlet macro, for JIRA 3.x and earlier, allows you to display a JIRA dashboard portlet on a Confluence page. Gadgets replaced portlets in JIRA 4.0 and Confluence 3.1.

In Confluence 4.1 and 4.2, 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.

In Confluence 4.3, we will remove the JIRA Portlet macro from Confluence. Pages that contain the macro will no longer display information drawn from JIRA. Instead, they will show an error reporting that the macro does not exist. To prevent this behaviour, please upgrade to a version of JIRA that supports gadgets, and follow the instructions in How to Migrate from JIRA Issues and JIRA Portlets to Gadgets.

Advance notice: End of support for PostgreSQL 8.2 in Confluence 4.3

Update added on 1 May 2012: We are planning to end support for version 8.2 of PostgreSQL in Confluence 4.3. See End of Support Announcements for Confluence.

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

Icon

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 Directory 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, then you must upgrade to Confluence 3.5.x before upgrading to Confluence 4.x. There are several reasons for this:
    • There were major changes to user management and LDAP in Confluence 3.5.
    • From version 3.5, you will be able to use our new automated installer / upgrader to move to 4.0. The Confluence 4.0 installer does not support upgrading from Confluence versions earlier than 3.5.
    • We recommend that you fix any issues arising from the upgrade to version 3.5.x, separately from those that may arise from upgrading to version 4.x. 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, then upgrade 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. Please check the known issues for the relevant release on this page of the Knowledge Base and follow the instructions to solve the problem.
  • 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.
  • No labels

9 Comments

  1. It is not clear if we can upgrade from 3.5 directly to 4.2, or we should do it in two steps: 3.5 -> 4.0 -> 4.2 

    1. Hallo Maksym

      You should be able to upgrade directly from Confluence 3.5 to 4.2. The only requirement is to upgrade to 3.5 first, if you're on a version earlier than 3.5. Please would you try it in a test environment first, and contact our support staff at http://support.atlassian.com if you have any problems.

      Cheers, Sarah

       

    2. We upgrade from 3.0 to 3.5.13, then from 3.5.13 directly to 4.2.

      For your information

  2. Anonymous

    The same question!

    Tried 3.5.7->4.2 in test env, it looks like there were not any data conversion from wikimarkup to xhtml

    1. Hallo there

      I've had a chat to the engineers, and the upgrade process should handle the wiki markup conversion when upgrading from Confluence 3.5.7 straight to 4.2. Please would you raise a support request at http://support.atlassian.com, so that our support engineers can help with the upgrade.

      Cheers, Sarah

       

  3. We've tried Upgrade 3.5.9 to 4.2 and there did not come up tasks to convert wiki markup. Also f.e. the code for Scaffolding plugin got lost.

    Doing the path 3.5.9 -> 4.1.9 -> 4.2 on the 4.1.9 stage the markup upgrade ran and then the upgrade to 4.2 succeed (also for Scaffolding)

     

     

    1. Hallo Harald

      I've raised an issue for the development team to investigate: CONF-25352 - Customers report that the wiki markup conversion tasks do not run when upgrading 3.5 to 4.2 Open

      Please would you add details of your environment there, and any logs and other information that can help in the investigation. You can also watch the issue for updates.

      Cheers, Sarah

       

      1. Anonymous

        Using the Confluence CLI from Bob Swift, you can copy spaces from 3.5 to 4.2  (that is what I am using) and it properly converts the wiki markup to the storage format that 4.2+ apparently uses.

        However - if 3.x has any macros that 4.2 does not, the space will not fully migrate.

         

        Is there any way to use the Confluence CLI to copy spaces and ignore macros that aren't available in the new version?

  4. Anonymous

    i am unable to disable the popular tab using the instructions provided above

    there is no "plugins" option within admin>configuration

    there is a mange plugins, but within that i cannot find any mention of dashboard macros or popular tab?

    although i am on version 4.3, so it may have changed again, but can see no mention within 4.3 release notes?