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

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Corrected links that should have been relative instead of absolute.

Confluence 1.3.4 is a maintenance release which includes a few important bug fixes for anyone running Confluence. These release-notes include information about the (briefly available) 1.3.3 version of Confluence, which 1.3.4 has superseded.

1.3.4 is a free upgrade for all existing Confluence customers.

Who should upgrade?

We recommend that all 1.3.x users upgrade to Confluence 1.3.4. For customers running 1.3.2 and earlier, it includes a fix to the security issue described in Confluence Security Advisory 2005-02-09, and it thus an important upgrade for anyone who is still running an un-patched system.

For customers running 1.3.3, the upgrade is also recommended as this version fixes CONF-2740, a regression in 1.3.3 which could cause referrer and trackback data to disappear.

Upgrade Procedure

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

If you are upgrading from Confluence 1.2.3 or earlier, be sure to read the upgrade instructions in the Confluence 1.3 release notes.

Changes in 1.3.4

See also: Issues Resolved for 1.3.4

Since only five bug-fixes were made for this release, here is a quick run-down.

  • The patch for the security issue described in Confluence Security Advisory 2005-02-09 has been applied to 1.3.4
  • A regression in 1.3.3 that caused trackback and referrer data to be lost has been fixed – CONF-2731
  • An intermittent ClassCastException when viewing blog-posts has been fixed – CONF-1671
  • The image cache for Apache FOP is now cleared between exports, preventing a case where the wrong version of an attachment may end up in a PDF export – CONF-2647
  • A spurious "Connection already closed" log message in the JIRA user management bridge no longer occurs CONF-2656