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

Confluence 2.3.1 is a maintenance release that resolves an assortment of issues users may have encountered using Confluence 2.3.

2.3.1 is a free upgrade for all customers who purchased their Confluence license after January 23rd, 2006.

Who should upgrade?

Confluence 2.3.1 is a bugfix release which resolves some significant issues in Confluence 2.3. Customers running Confluence 2.3 should review the list of resolved issues below, and upgrade if this release fixes any problems with their current Confluence installation.

Customers running releases older than 2.3 and wishing to upgrade should use this version also.

Significant issues for customers upgrading to Confluence 2.3

  • LDAP integration: Confluence 2.3 shipped with a broken user migration script for customers wishing to integrate LDAP servers with their Confluence installation. 2.3.1 ships with a fixed version of this script which can also be obtained from CONF-7585
  • Upgrading with MySQL: Customers using Confluence with MySQL may have had difficulty upgrading their instances to Confluence 2.3. This issue has been resolved in 2.3.1.

Significant issues for existing Confluence 2.3 users

  • Backup import: Confluence 2.3 users wishing to import backups into their Confluence instance should upgrade to 2.3.1 or apply the patch listed against CONF-7584

Upgrade Procedure

Upgrading Confluence should be pretty easy. If you are upgrading from another Confluence 2.2.x or Confluence 2.3 version, you can find instructions here. We strongly recommend that you backup your confluence.home directory and database before upgrading!

Upgrading from Confluence 2.1 and earlier

Users upgrading directly from 2.1 or earlier should also read the 2.2 Release Notes for caveats regarding the 2.1 -> 2.2 upgrade.

Changes in 2.3.1

2.3.1 resolves 20 issues. All these issues are listed below:

Unable to locate JIRA server for this macro. It may be due to Application Link configuration.