Preparing for Confluence 7.11

Insight categories: AtlassianTechnology

✓ Planned changes

✓ Implemented changes

Last milestone
4th January 2020 7.11.0-m37 Download

Planned changes

In this section, we provide an overview of the planned changes so that you can think about how they might affect your app. We indicate when a change was implemented and in which milestone.

Removing Editor-v3


When Atlassian updated the editor to TinyMCE v4 in Confluence 6.14, an unsupported dark feature was introduced with which you could return to the v3 editor (frontend.editor.v4 / frontend.editor.v4.disable). However, they plan to remove this dark feature flag in a future Confluence release as they are no longer tested or reliable.

As soon as this is the case, the Editor-v3-WRM context will no longer be loaded. All resources that are only used in this context can be completely removed. The editor and editor-v4 contexts remain unchanged, and with this change, resources in editor-v4 can be safely moved to editor.

Team Calendars and Analytics for Confluence are now part of the Confluence Data Center


Team Calendars and Analytics for Confluence are now part of Confluence Data Center. Locations with a data center license no longer need separate app licenses for these applications.

Changes to the application log files


Currently, most of the log entries are written to the application log file (atlassian-confluence.log), which can be difficult to parse and rotates too quickly when you are trying to troubleshoot a problem. To remedy this, some entries are now written to the following dedicated log files, which are located in the same directory.

  • atlassian-confluence-index.log contains events related to the search index. The following packets are logged in this file:
    • com.atlassian.confluence.internal.index
  • atlassian-confluence-outgoing-mail.log contains events related to outgoing mail, such as: B. Notifications. The following packets are logged in this file:
    • com.atlassian.confluence.mail
    • com.atlassian.confluence.jmx
    • com.atlassian.plugin.notifications.dispatcher
    • javax.mail
    • com.sun.mail
    • com.atlassian.mail
  • atlassian-confluence-security.log  contains events that relate to your users and user directories. The following packets are logged in this file:
    • com.atlassian.user
    • com.atlassian.confluence.user
    • com.atlassian.seraph
    • com.atlassian.crowd
    • org.springframework.ldap.core

This should make troubleshooting problems a lot easier. If you send your logs to a third party tool for easy access and analysis, you may need to update your configuration to include these new files.

Switch to flags


This change relates specifically to the AMD confluence / flag module, not the AUI flag component. For the AUI component, see the documentation and the AUI version used in Confluence.

The markup for flags and the attached functionality has been changed to better match the AUI 9 version of the flag component:

  • The visibility is determined by the attribute “open”. Compared to the AUI 9 component, however, the “aria-hidden” attribute is retained and can be used as a selector or to check the visibility of flags.
  • The “Close” button has been changed from “span” to “button” and can now get 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 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>

Support for PostgreSQL 11


Atlassian plans to add support for PostgreSQL 11 in this release. We’ll let you know if we discover any issues that may be relevant to plugins.

Upgrade for the embedded crowd


In this release, Atlassian plans to upgrade Embedded Crowd from 2.3 to 4.2. There are several performance and stability improvements.

AUI 9.x upgrade


The Atlassian team is currently working on an upgrade to AUI 9.x. See Upgrading from 8.x to 9.0 in the AUI documentation for information about the changes that may affect your app. 7.12 is currently targeted for this upgrade.

Implemented changes

This section provides details on the changes Atlassian has implemented, ordered by the milestone in which they are first available. This will help you decide which milestone to use when testing.

EAP 2 – January 4, 2021

Milestone 7.11.0-m37

In this milestone:

  • Analytics for Confluence is now bundled with Confluence Data Center.
  • Team Calendars for Confluence is now bundled with the Confluence Data Center.
  • Some log entries are now written to dedicated log files. See info above for details.

EAP 1 – December 21, 2020

Milestone 7.11.0-m23

In this milestone:

  • The logging of Tomcat valve accesses is now activated by default.
  • The page index macro is now limited to 1000 pages.
  • You can now flag logs when troubleshooting a problem. Go to  > General Configuration  > Logging and Profiling to try it out.


  • URL copied!