Below are some important notes on upgrading to Confluence 3.4. For details of the new features and improvements in this release, please read the Confluence 3.4 release notes.
On this page:
As stated in the release notes, the Confluence Macro Browser and autocomplete can now show user macros as well as other macros. If your Confluence site already has some user macros, when you upgrade to Confluence 3.4 the upgrade task will set all existing user macros to be visible only to system administrators.
After upgrading, you will need to set each macro individually to be visible to all users, depending on your requirements. See the documentation on writing user macros.
If your Confluence installation is integrated with Atlassian Crowd for user management and single sign-on, you will need to upgrade to Crowd 2.0.7 when upgrading to Confluence 3.4. Note also that for Confluence 3.4, there is a new Seraph authenticator to be specified in the CONFLUENCE-INSTALLATION/confluence/WEB-INF/classes/seraph-config.xml file.
<authenticator class="com.atlassian.crowd.integration.seraph.v22.ConfluenceAuthenticator"/> |
Please follow the Crowd integration guide for complete instructions, including the update to the Seraph authenticator configuration. See our knowledge base article for symptoms of the problem that occurs if Crowd is not upgraded. And here are the Crowd 2.0.7 release notes.
This section is relevant to Confluence installations that use a custom authentication mechanism. You may run into problems with the Confluence security measure that requires password confirmation for administrative actions, change of email address and Captcha for failed logins.
If necessary, you can set the password.confirmation.disabled system property to disable the password confirmation functionality. See Recognised System Properties. We provide this configuration option as a workaround for issue CONF-20958.
We have tightened the security of Confluence's 'remember me' functionality. As a result of this change, any existing 'remember me' cookies will be invalid after you upgrade your Confluence installation. When accessing Confluence for the first time after the upgrade, users will be prompted to log in as usual.
As previously announced, we no longer offer support for:
Please see End of Support Announcements for Confluence.
We are planning on ending support for:
Please see End of Support Announcements for Confluence.
Confluence 3.2 introduced two new themes, the Documentation theme and the Easy Reader theme. At the same time, we announced the deprecation of the following two themes:
Deprecated Theme | Description | Suggested Replacement |
|---|---|---|
Clickr theme | This theme was inspired by the Flickr user interface, with Confluence content centred on the page. | Easy Reader theme |
Left Navigation theme | This theme provided a navigation bar on the left hand side of the screen. |
Please note the following:
If you do not wish your spaces to be migrated, you can start Confluence with the following JVM parameter to prevent the conversion of the space themes:
-Dconfluence.theme.skip.migration=true |
During the upgrade, the Left Navigation and Clickr themes will be removed from your Confluence site but, if you specify the above parameter, your spaces will still expect to use those themes. After the upgrade, you will need to download and install the Left Navigation and Clickr themes from the Atlassian Plugin Exchange so that your spaces can continue to use them. If you do not reinstall those themes, the affected spaces will use the default theme.
If the upgrade process converts your spaces to the new themes and you later decide to revert to the old themes, you can get some help from the Confluence logs written during the upgrade process. The logs contain a SQL query that you can run to revert the theme migration. The relevant part of the log file looks like this:
2010-08-05 15:13:22,572 INFO [main] [confluence.upgrade.upgradetask.ClickLeftNavMigrationUpgradeTask] doInTransaction To rollback the migration of spaces with Left Navigation Theme theme execute the following SQL:
update BANDANA set BANDANAVALUE = '<map>\n <entry>\n <string>theme.key</string>\n <string>com.atlassian.confluence.themes.leftnavigation:leftnavigation</string>\n </entry>\n</map>' where BANDANACONTEXT in ('~SPACE-KEY1', 'SPACE-KEY2', 'SPACE-KEY3') and BANDANAKEY = 'atlassian.confluence.theme.settings'
2010-08-05 15:13:22,573 INFO [main] [confluence.upgrade.upgradetask.ClickLeftNavMigrationUpgradeTask] doInTransaction To rollback the migration of spaces with Clickr theme execute the following SQL:
update BANDANA set BANDANAVALUE = '<map>\n <entry>\n <string>theme.key</string>\n <string>com.atlassian.confluence.themes.clickr:clickr</string>\n </entry>\n</map>' where BANDANACONTEXT in ('SPACE-KEY4', 'SPACE-KEY5', 'SPACE-KEY6') and BANDANAKEY = 'atlassian.confluence.theme.settings'
|
The words '~SPACE-KEY1', 'SPACE-KEY2', etc represent the keys of the spaces that were converted. If you run the SQL statements and install the Left Navigation and Clickr themes (see below), your spaces will be in the same state as before the upgrade task ran.
Some macros were never intended for external use, and we have always recommended that you do not add them to a wiki page. Nevertheless, it is possible that some Confluence sites have these macros on some pages. Please note that these macros no longer work in Confluence 3.4 onwards. They were part of the Plugin Repository, which we have now replaced with a new plugin manager.
These macros no longer work:
Please note that the space description no longer renders wiki markup. If your space descriptions include wiki markup, the markup will display as plain text.
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: