Release Notes 2.9-m5 ("Milestone 5")

Do not use this release to upgrade your production systems.

For all production use and testing of Confluence, please use the latest official release.
This release is a milestone development release for 2.9. This is a public development release (DR) leading up to Confluence 2.9. Development releases are a snapshot of our work in progress, allowing our customers and especially plugin-developers to see what we're up to.

Who should upgrade?

Please note the following

  • Development releases are not safe. Development releases are snapshots of the ongoing Confluence development process. For that reason:
    • While we try to keep these releases stable, they have not undergone the same degree of testing as a full release.
    • Features in development releases may be incomplete, or may change or be removed before the next full release.
  • No upgrade path. Because development releases represent work in progress, we cannot provide a supported upgrade path between development releases, or from any development release to the eventual final release. Thus, it is possible that you will not be able to migrate any data you store in a Confluence development release to a future Confluence release.
  • Atlassian does not provide support for development releases.

Our milestone releases aim to provide plugin developers with an opportunity to see the latest changes in the code.

Each milestone release has passed all our automatic tests, and has been used for one week on our official internal Confluence server. Most of the issues solved have been reviewed too, and usually milestone releases even have been load- and performance-tested for a while.

However, since our milestones releases are timeboxed (i.e. they get released every two weeks, no matter how far we have come implementing features and bugfixes), there is always a chance that we have new known bugs, which are scheduled to be fixed in the next milestone, or completely new bugs unknown even to us.

Additionally, our performance-testing and compatibility testing for databases and application servers is not done to the full extent. So, for example, a milestone release might behave well on a small installation but show severe problems when subjected to many users.

Upgrade Procedure

Follow the normal upgrade instructions to upgrade from Confluence 2.8.x to this release. We strongly recommend that you backup your confluence-home directory and database before upgrading!


All development releases are available from Development Releases on the Atlassian website.

Issues resolved or improved in this release

We are rapidly approaching the end of the 2.9 release cycle. There will be a really small M6 later this week, and then that's it, we are going into bugfix and compatibility-testing mode, so we can release on the 29th of July.


We have done a significant amount of work in the area of plugin loading (and the plugin classloaders) to improve performance. There are no API changes, but it is very possible that these changes may expose bugs. While we tried to remain backwards compatible, it is crucial that you test for compatibility of your plugins.


The preview in the editor is now capable of rendering content exactly as it appears on the page. However, to do this, we have had to disable interaction with the preview. You will no longer be able to follow links or interact with the preview in any other way.

When drafts are saved automatically to the server, this will be shown to you at the top of the editor.

Engine room

Whisper the words "Action class hierarchy" anywhere close to a Confluence developer and he or she will cringe. Not anymore as of this Milestone. Plenty of inheritance trees have been cut, and miraculously Confluence still works. This will enable us to work faster and more efficiently in the future.

Page tree and UI

We had a few nasty UI bugs recently where plugin JavaScript code would interfere with our menus and other JavaScript code, and we had a few Pagetree bugs. The most important ones have been fixed in this release.

Discovery Team

Author auto-complete field added to the search result screen to allow filtering searches by contributor (author or editor).

The 'new search' (or reset search) link on the search screen filter left the building somewhere around milestone 3. This has now been re-instated.

A couple of 2.9 specific bug fixes are also included.

Known problems

Several small bugs, specifically around the new author-search.

Was this helpful?

Thanks for your feedback!

Why was this unhelpful?

3 Archived comments

  1. User avatar

    Bob Swift [Bob Swift Atlassian Add-ons]

    You will no longer be able to follow links or interact with the preview in any other way.

    Why would you disable this capability? Use this all the time to check that links are working before updating the page.

    11 Jul 2008
    1. User avatar

      Matt Ryall [Atlassian]

      Thanks for the feedback, Bob. Since your comment we've changed the preview a bit to restore this functionality. Let me explain the problem a bit further, and how we've ended up solving it.

      The new preview renders all content exactly as it would appear on the page, including with CSS and JS resources. The only practical way for us to do this for all possible content was with an iframe.

      The problem with iframes is that it becomes possible to navigate within the iframe without changing the page around it. For example, it would be possible to click on a link inside the preview window and just the preview window would navigate to the new site. Submitting a form inside the preview would do this too. We quickly showed the comical situation of rendering the preview window several times within itself, like a house of mirrors.

      To prevent users inadvertently "breaking the preview window" in this way, we put a transparent <div> element on top of the preview content – called a 'blanket' – so that it wasn't possible to click on or interact with the preview in any way. This seemed like the best option initially.

      Based on your feedback and speaking with some users at Atlassian, we implemented a slightly different solution for 2.9-m7 and later. When the preview page loads, we apply the following transformations with JavaScript to prevent some common types of preview iframe misbehaviour:

      • all anchor tags have their target attribute set to "_top"
      • all inputs have their event handlers unbound (jQuery handlers only)
      • all forms have an onsubmit handler attached which returns false, preventing form submission. Other jQuery event handlers on forms are removed.

      This helps with many cases but not all possible situations like the transparent blanket did. I'm sure we'll get some bug reports about preview window breakage with some dynamic macros and have to expand this list to include more JS tweaks to the preview. For the moment, though, this seems like a good compromise for having normal link functionality (hovering, right-clicking, etc.) available in preview.

      30 Jul 2008
      1. User avatar

        Bob Swift [Bob Swift Atlassian Add-ons]

        Matt, excellent (smile)! And the ability to validate javascript capabilities in preview mode is very nice! Haven't played much with it yet, but it already looks like a very good improvement.

        30 Jul 2008
Powered by Confluence and Scroll Viewport