Preparing for Confluence 6.6
This documentation is intended for Confluence developers who want to ensure that their existing plugins and add-ons are compatible with Confluence 6.6.
Release Candidate - 7 December
This release contains minor improvements and fixes.
Update on editor context changes:
For those loading a custom editor experience in an add-on, 6.6.0-rc1 and Final versions will not require updating to include editor-v3 as described in Milestone 10 below. This means that your add-on should continue to work normally for 6.6. However, the steps described in Milestone 10 will still apply to future 6.7 EAPs.
Additionally, the Webresource issue has been resolved, and 6.6.0-rc1 and Final versions, as well as all future EAP’s, do not have the requirement of running in batched mode.
Beta 1 - 28 November
There is still some work to be done on our improvements to user mentions. For this reason we’ve decided to keep this feature dark for Confluence 6.6 and instead make it available in a future Confluence version.
For a complete run down of all the features and changes in this beta, head to our Confluence 6.6.0-beta release notes.
Milestone 22 - 20 November
There are no significant changes in this milestone.
Milestone 18 - 13 November
We've made some significant improvements to the performance and appearance of user mentions. The changes are still dark in this milestone, but you can go to
<confluence-url>/users/darkfeatures.action and add the
smart.mentions dark feature flag to try it out.
Milestone 10 - 6 November
This is our first public milestone for Confluence 6.6. Not much has changed yet, but keep an eye on this page, as we'll be releasing a milestone every week in the lead up to Confluence 6.6.
We are in the process of upgrading the Confluence editor from TinyMCE 3 to TinyMCE 4, and expect this work to land in or before Confluence 7.0. While this work is in progress we will be taking effort to make these changes in a backwards compatible way, so as not to impact upcoming Confluence 6.x releases. While we are working on it, however, it is possible that your plugin might experience some issues with the changes.
There is one issue that we're currently aware of, relating to the editor context, and we are looking intro ways to resolve it before we release Confluence 6.6.
In preparation for the upgrade to TinyMCE 4 we are splitting the editor context into 3 separate contexts internally. "editor" will remain the official context to contribute resources as a plugin developer. Internally, we will also be conditionally loading either "editor-v3" or "editor-v4" context depending on whether TinyMCE 3 or TinyMCE 4 is active, during the transition. TinyMCE 3 will continue to be the current editor until the announcement of TinyMCE 4. This means that any code loaded currently in "editor" context will continue to work normally in 6.6. However, if a plugin is loading the "editor" context on its own, for a custom editor experience, the resources loaded by "editor-v3" may not be loaded unless the atlassian-plugin.xml resources being used declare explicit dependencies on those resources. We are looking at mitigating this in releases leading to the final editor upgrade release by automatically loading "editor-v3" when "editor" is requested, but we may not be able to automatically account for all cases.
If your plugin is currently requesting the "editor" context, you can verify that your plugin will continue to work normally by also requesting the "editor-v3" context ahead of the "editor" context (the order is important). This is a backwards compatible change, and can be easily added to any plugin that is doing this, without adverse effects to previous Confluence versions. We are planning to remove the need to do this before the final 6.6 release, but if your plugin is doing something we are not expecting, it would be helpful to hear from you in an EAP Feedback ticket.
The specific bugs we are aware of have to do specifically with link insert and autocomplete, as well as mentions autocomplete. This is a quick way to check if your plugin editor is affected.
Additionally, there is currently an outstanding bug in Atlassian Web Resource Manager that makes it impossible to run Confluence in unbatched resource mode. We are relying on a dark feature condition to determine which version of the editor to load so that we can offer early testing via our dark feature mechanism once it is ready to be tested. Unfortunately, the condition is ignored in unbatched mode resulting in both versions of the editor being loaded. This can cause any number of problems. Until this bug can be resolved, it is necessary to run Confluence in batched mode. You may pass the following properties to run Confluence in batched mode:
We hope to have this resolved before the final 6.6 release.
We'll keep you updated throughout the process, and will provide additional communication about any API changes that might be necessary before the final upgrade release. We will also be providing additional EAP milestones so you can test the editor upgrade with your plugins.