Preparing for Confluence 7.11
This documentation is intended for Confluence developers who want to ensure that their existing plugins and apps are compatible with Confluence 7.11.
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.
|14 January 2020|
Issues with this milestone?
Hit the Feedback button on the Confluence EAP header or raise an issue to tell us about it.
On this page:
In this section we'll provide an overview of the changes we intend to make, so you can start thinking how it might impact your app. We'll indicate when a change has been implemented, and in which milestone.
Removal of editor-v3
Status: ADVANCE NOTICE
When we upgraded our editor to TinyMCE v4 way back in Confluence 6.14, we introduced an unsupported dark feature that could be used to revert to the v3 editor (
frontend.editor.v4.disable). We plan to remove this dark feature flag in a future Confluence release, as they are no longer tested or reliable.
Once that happens, the
editor-v3 WRM context will no longer be loaded. Any resources used only in this context can be removed completely. The
editor-v4 contexts are unchanged, and with this change, resources in
editor-v4 can be safely moved to
AUI 9.x upgrade
Status: ADVANCE NOTICE
We're currently working on upgrading to AUI 9.x. See Upgrading from 8.x to 9.0 in the AUI documentation for information on changes that may affect your app. We're currently targeting 7.12 for this upgrade.
Team Calendars and Analytics for Confluence are now part of Confluence Data Center
Team Calendars and Analytics for Confluence are now bundled with Confluence Data Center. Sites with a Data Center license will no longer require separate app licenses for these apps.
Changes to application log files
Currently most log entries are written to the application log file (atlassian-confluence.log), which can be difficult to parse, and can rotate too quickly when you're attempting to troubleshoot a problem. To help with this, some entries will now be written to the following dedicated log files, in the same directory.
- atlassian-confluence-index.log contains events related to the search index. The following packages will be logged to this file:
- atlassian-confluence-outgoing-mail.log contains events related to outgoing mail, such as notifications. The following packages will be logged to this file:
- atlassian-confluence-security.log contains events related to your users and user directories. The following packages will be logged to this file:
This should make troubleshooting problems significantly easier. If you send your logs to a third party tool for easier access and analysis, you may need to update your config to include these new files.
Change to flags
This change specifically relates to AMD module
confluence/flag , not the AUI Flag component. For AUI component, see the documentation and the AUI version used in Confluence.
The markup for flags and attached functionality has changed to align better with AUI 9 version of the Flag component:
- The visibility is determined by "open" attribute. However compared to AUI 9 component, the
aria-hiddenattribute is preserved and can be used as a selector or to check flag visibility.
- The close button changed from
buttonand can now receive focus.
<div id="aui-flag-container" style="top: 71px;"> <div class="aui-flag " aria-hidden="false"> <div class="aui-message aui-message-info info closeable shadowed"> <p class="title"><strong>Flag title</strong></p> Detailed message <!-- .aui-message --> <span class="aui-icon icon-close" role="button" tabindex="0"></span> </div> </div> </div>
<div id="aui-flag-container" style="top: 71px;"> <div class="aui-flag " aria-live="polite" open="open" aria-hidden="false"> <div class="aui-message aui-message-info info closeable shadowed"> <p class="title"><strong>Flag title</strong></p> Detailed message <!-- .aui-message --> <button type="button" class="aui-close-button" aria-label="Close"></button> </div> </div> </div>
Embedded Crowd upgrade
In this release we plan to upgrade embedded Crowd from 2.3 to 4.2. There are several performance and stability improvements.
When you create an application link, the URL is automatically added to the Confluence allowlist. From Confluence 7.11, outbound requests from these URLs require users to be authenticated. We've updated the allowlist screen to allow admins to specify which URLs allow anonymous users, and to set the default behaviour for all new application links.
Support for PostgreSQL 11
Status: IN PROGRESS
We plan to add support for PostgreSQL 11 in this release. We'll let you know if we discover any issues that might be relevant to plugins.
In this section we'll provide details of changes we have implemented, organised by the milestone they are first available in. This will help you decide which milestone to use when testing.
Beta - 14 January 2021
In this beta release:
- Upgraded Embedded Crowd from 2.3 to 4.2.
- Upgraded atlassian-gadgets from 4.4.12 to 6.0.1
- Upgraded Atlassian Whitelist from 4.3.1 to 5.0.3
- Upgrade UPM from 4.2.6 to 4.3.0
See Confluence 7.11 beta release notes for full details of everything in this release.
EAP 2 - 4 January 2021
Happy new year everyone! In this milestone:
- Analytics for Confluence is now bundled with Confluence Data Center.
- Team Calendars for Confluence is now bundled with Confluence Data Center.
- Some logs entries are now written to dedicated log files. See info above for details.
EAP 1 – 21 December 2020
In this milestone:
- Tomcat valve access logging is now turned on by default.
- The Page Index macro is now limited to 1000 pages.
- You can now mark logs when troubleshooting an issue. Go to > Logging and Profiling to give it a try. > General Configuration