Confluence 4.0 Upgrade Notes

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

On this page:

Upgrade Notes

Content updates after upgrade

You will notice once you upgrade to Confluence 4.0, every page will have been edited during the migration process. This manifests itself in the appearance of changes to every page's content by various different users. When migrating pages, Confluence will show the same username that last contributed to your content as the author of the change. This is the upgrade task of migrating your wiki page storage format to XHTML from Wiki Markup. Do not be alarmed by this. This will only happen once for all current versions of content. This will not trigger email notifications, but will update your RSS feeds. Where possible, a change comment of "Upgraded to Confluence 4" will be added to pages and blog posts.

User macros migration

After upgrading, user macros will not be able to be inserted until they have defined macro parameters. See User Macro Template Syntax. Defining macro parameters will mean that they can once again insert these user macros.

Email notifications

With the update of the email templates, the textual content of the notifications has also changed. These wording changes may invalidate any email filters set up to label or organize your email notifications.

Plugins may not be compatible with Confluence 4.0

To check your plugins are compatible with Confluence 4.0, see the Universal Plugin Manager (UPM) under Confluence Admin > Plugins > Confluence Upgrade Check. Here, you can select the new version of Confluence and see whether your existing plugins are compatible. If your custom plugins are not working following the upgrade to Confluence 4.0, see the Plugin Development Upgrade FAQ for 4.0 for guidance on how to solve this issue.

Functionality removed: converting a Global Space to a Personal Space

Confluence 4.0 does not offer the ability to convert a global space to a personal space. Our research has shown that this feature is not used much. We have decided to remove it as part of our ongoing mission to simplify Confluence where possible. We deprecated this functionality in the Confluence 3.5 Upgrade Notes.

Functionality removed: editing a Confluence page in an Office application

After extensive usability testing, we are confident the new Confluence 4.0 editor will be easier to learn and more reliable to use than the previous editor. Therefore this feature is no longer required. Other functions of the Office Connector (e.g. "Edit Attachments in Office") remain.

Functionality removed: linking to comments using commentid

Confluence 4.0 does not allow linking to comments by comment ID. Users will now have to use the permalink URL to link to comments. This will primarily affect plugin developers.

Functionality removed: Mail Page plugin

The Mail Page plugin is no longer bundled in Confluence. With the introduction of the "Share Page" feature, this is no longer needed.

Functionality removed: Social Bookmarking plugin

The Social Bookmarking plugin is no longer bundled with Confluence as of the 4.0 release. Our research has shown that this feature is not used much. If you are currently using this plugin, you will need to reinstall it from plugins.atlassian.com. Atlassian continues to fully support this plugin.

Drag-and-drop in Internet Explorer 9

Internet Explorer 9 does not support the drag-and-drop functionality of HTML5. This means that when using IE9, you will not be able to use the attachments drag-and-drop feature in Confluence 4.0.

Various admin settings removed

In Confluence 4.0, rarely used admin settings have been taken out. These are as follows:

  • The Set Site Support Address setting,
  • The CamelCase Links general configuration setting,
  • The Number of Ancestors to Show in Breadcrumbs setting,
  • The SnipSnap Importer settings.

Confluence Clustered delayed

Please be aware that Confluence Clustered is not available for version 4.0 yet. It will be forthcoming in a minor release, following the launch of version 4.0.

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.0. 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.0. The Confluence 4.0 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.0. 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.0.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.0 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