Confluence 3.0 Known Issues

We have an enthusiastic and dedicated group of testers and customers who jump in there, try out the new Confluence release, and report any problems so that we can fix them quickly. Below is a list of known issues. We're working on them, and will have a point release out as soon as possible.

A big thank you to everyone who helps us ensure that Confluence keeps getting better and better.

While you're waiting, take a look at the great new features in Confluence 3.0 Release Notes.

You can also browse the Confluence project in our issue tracker to see what's fixed and what's not, for each release.

Issues to be Fixed

Other Issues

Early 3.0 Build Issue Note that an early build of 3.0 (Build number 1626) had a problem when moving a page from one space to another. If the default filesystem attachment storage was configured then any attachments on the page would fail to be moved if the page was moved to a new space. The attachment would only be accessible again if the page was moved back to its original space. The current 3.0 release (3.0.0_01) does not have this problem. See CONF-15986 for more details.

Confluence on MySQL databases

Some customers who run Confluence on a MySQL database may find that when they upgrade to Confluence 3.0 or later, their Confluence 3.0 upgrade fails, with the Confluence logs revealing a "Specified key was too long" error. This issue is known to occur when MySQL's MyISAM storage engine and UTF-8 character set is used with Confluence.

If this is the case, please refer to the Upgrade to Confluence 3.0 with MySQL database fails with messages like "specified key was too long" knowledge base article on how to resolve this upgrade issue.