Release Notes 1.0rc6

Confluence 1.0rc6

Confluence 1.0rc6 fixes more bugs. Lots of them. There aren't many new and interesting features to report, although we have implemented the much-requested ability to mask email addresses and prevent public signup. Mostly, we've been toiling away fixing the lots of little problems that are getting in the way of us calling Confluence truly worthy of the 1.0 label.


  1. New Features
  2. New Macros
  3. Improvements
  4. Notable Bug-fixes
  5. Outstanding Issues

See also: Issues Resolved for 1.0rc6

New Features

Private Confluence Configuration

In private mode, the only way to add users to Confluence is through the administrative interface: users can not sign up on their own. This way, you can prevent random passers-by from signing on to your Confluence installation. The site administrator can configure this in the general administration settings.

Email Address Privacy

Another much-requested feature, the site administrator has three options for email-address privacy:

  • Public: just like pre-rc6, users email addresses are displayed publicly.
  • Masked: email addresses are still displayed publicly, but masked in such a way to make it harder for spam-bots to harvest them.
  • Private: only site administrators can see users' email addresses.

Administrators should be aware that even in private mode, anyone in the confluence-admin group will still be listed (with their email address) on the administrators page, although their addresses will be masked.

Share User Management with JIRA

For sites with both a Confluence and a JIRA installation, Confluence can be set up to delegate its user-management to JIRA.

Template Field Types

Templates now support drop-down menus and text-input areas.

@variablename|textarea(5,10)@ will give you a 5 x 10 text-area called 'variablename'.
@variablename|list(one,two,three,four)@ will give you a drop-down list called 'variablename', with options one, two, three and four.

New Macros

  • The {html} will allow you to insert arbitrary HTML code into a page. This macro is turned off by default, as it is a security-risk on public systems. We only recommend you enable it on private or intranet-based Confluence installations where you trust your users not to write malicious HTML code. Here's a trivial example of its use:

    <p>This HTML is <b>inserted</b> into the page</p>
  • The {junitreport} macro has an option: "reportdetails=failuresonly" that will cause it to only show details of tests that have failed. For example: {junitreport:directory=file:///var/tests|reportdetail=failuresonly}


  • Users are now taken to their preferred homepage rather than the dashboard after logging in
  • Text-fields in a template are disabled during preview and viewing
  • Orphaned and Undefined page reports are now paginated
  • Macros such as {code} or {noformat} are now made part of a list if they are placed adjacent to them

Notable Bug-fixes

  • User->Group relationships should no longer disappear during manual or scheduled backups
  • Search results no longer allow people to see content they might not be allowed to see
  • Comments should no longer appear out of order on a page
  • Moving a page between spaces no longer breaks #anchor links
  • Many rendering fixes, some subtle, some not so
  • Many stability fixes, especially regarding import and export

Outstanding Issues

Random MySQL Disconnections

If you are running Confluence against MySQL using Confluence's built-in datasource, the connection with the database server may be lost after long periods of inactivity. We are pretty sure we have a fix for this, but since the bug takes several hours to manifest, we were not able to test the fix before the release of rc6.

The good news is that if we are right, it will only require a quick edit of your configuration file to implement the fix. Further announcements will be made both on, and the confluence-user mailing-list.

In the meantime, the workaround is to not use Confluence's built-in datasource, but to configure Confluence to use your application-server's JNDI datasources instead. Instructions for doing this with Tomcat can be found here, and if you need more help, don't hesitate to contact us at

Latin Characters under Resin

We've tested creating pages with non-ASCII titles and content across several different browsers and several different operating systems, and they seem to be working reliably now... except on Resin. This will be quite noticeable since itself is running under Resin, but we have so far been unable to come up with a solution that works on this application server.

For users who need this functionality, we suggest running under Tomcat.


  • On MySQL, the "orphaned pages" report may include the space's homepage CONF-766
  • You can create a link to a page with an illegal title: prompting the user to create a page that can not exist CONF-810
  • Trackbacks are not sent for shortcut links CONF-888
Last modified on Aug 22, 2017

Was this helpful?

Provide feedback about this article

In this section

Powered by Confluence and Scroll Viewport.