Preparing for Confluence 6.9
This documentation is intended for Confluence developers who want to ensure that their existing plugins and add-ons are compatible with Confluence 6.9.
We plan to release weekly milestones during the development of Confluence 6.9. Watch this page to find out when a new milestone is available and what’s changed. We will publish formal release notes once we release a beta.
Issues with this milestone?
Hit the Feedback button on the Confluence EAP header or raise an issue to tell us about it.
Changes in Confluence 6.9
Release candidate - 1 May 2018
No significant changes in this release candidate.
Beta 1 - 24 April 2018
There are no significant changes in this beta. For the full run-down on features in this release, head to Confluence 6.9.0-beta release notes.
Note that read-only mode will not be available in Confluence 6.9.
Milestone 70 - 16 April 2018
We plan to announce IPv6 support for Confluence in 6.9. If your add-on connects to a remote server or has configuration options that involve entering an IP address, we recommend testing your add-on in an IPv6 environment.
In Confluence we found a number of minor compatibility issues, for example some database drivers do not recognise raw IPv6 addresses. Most of the issues we found were solved by using the DNS name rather than the raw IPv6 address, and this is the workaround we will be recommending to customers who wish to run Confluence in an IPv6 environment.
Update on read-only mode
With the 6.9 beta shortly due to be released next week, we have made the hard decision to delay this feature, as it is not quite production ready. The good news is that we expect to be complete from the Atlassian side in the next few weeks, which will give you a little extra time to make your add-on compatible before it's released in 6.10.
Milestone 61 - 9 April 2018
Editor footer changes
We've made some changes to the editor footer. A new ellipsis menu provides options to preview, view a diff of unpublished changes, revert back to the last published version, and, if the page has never been published, delete the unpublished page. The close button now just closes the editor. There is no longer an option to discard changes on the way out.
Read-only mode changes
In milestone 43 we mentioned a known issue with the
@BypassReadOnlyAccess annotation. This has been replaced by
@ReadOnlyAccessAllowed which can be used to allow POST/PUT/DELETE requests, when necessary.
By default we allow GET requests through the filter/interceptor, but have now also added a new
@ReadOnlyAccessBlocked annotation which can be used in the rare case you do need to block GET requests.
Head to our developer documentation How to make your add-on compatible with read-only mode for more information about this change.
Milestone 52 - 3 April 2018
We're continuing to make improvements to read-only mode in this milestone. There are no other significant changes.
Milestone 43 - 27 March 2018
Read-only mode is coming
As previously mentioned, we're currently working on a great new feature to help Data Center customers perform routine maintenance, recover from unexpected problems, or prepare to migrate content to a new site.
Admins will be able to temporarily put their site in "read-only mode" to limit the actions that end users can do. Users will be able to view pages and their history, but not create, edit, comment, copy or move content . Administration actions such as changing site configuration are not restricted.
In order to limit the actions that end users can do, we need add-ons to make sure they they also do not allow users to create or update content, while the site is in read-only mode.
Head to How to make your add-on compatible with read-only mode in our developer documentation to find out what you need to do.
The @BypassReadOnlyAccess annotation is not currently working as expected. We'll have a fix for this problem in an upcoming milestone.
Milestone 27 - 20 March 2018
This is our first public milestone for Confluence 6.9. There's no significant changes in this milestone.