Meelogic Atlassian Blog

Preparing for Confluence 7.11

✓ Planned changes

✓ Implemented changes

 

 
Latest milestone
4 January 2020

7.11.0-m37

Download

 

Planned changes

In this section we’ll provide an overview of the changes that Atlassian intends 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 Atlassian upgraded their editor to TinyMCE v4 way back in Confluence 6.14, they introduced an unsupported dark feature that could be used to revert to the v3 editor (frontend.editor.v4 / frontend.editor.v4.disable). The team now plans 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 and editor-v4 contexts are 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 Confluence Data Center

Status: COMPLETE

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

Status: COMPLETE

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:
    • com.atlassian.confluence.internal.index
    • com.atlassian.confluence.search.lucene
    • com.atlassian.bonnie.search.extractor
  • atlassian-confluence-outgoing-mail.log contains events related to outgoing mail, such as notifications. The following packages will be logged to this file:
    • com.atlassian.confluence.mail
    • com.atlassian.confluence.jmx
    • com.atlassian.plugin.notifications.dispatcher
    • com.atlassian.confluence.plugins.email
    • javax.mail
    • com.sun.mail
    • com.atlassian.mail
  • atlassian-confluence-security.log contains events related to your users and user directories. The following packages will be logged to this file:
    • com.atlassian.user
    • com.atlassian.confluence.user
    • com.atlassian.seraph
    • com.atlassian.crowd
    • com.atlassian.confluence.security
    • org.springframework.ldap.core

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

Status: IN PROGRESS

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-hidden  attribute is preserved and can be used as a selector or to check flag visibility.
  • The close button changed from span  to button and can now receive focus.

Before

<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>

After

<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>

 

Support for PostgreSQL 11

Status: IN PROGRESS

Atlassian plans 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. 

 

Embedded Crowd upgrade

Status: IN PROGRESS

In this release they plan to upgrade embedded Crowd from 2.3 to 4.2. There are several performance and stability improvements.

 

AUI 9.x upgrade

Status: ADVANCE NOTICE

Atlassian is 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. They’re currently targeting 7.12 for this upgrade.

 

Implemented changes

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.

EAP 2 – 4 January 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 Confluence Data Center. 
  • Some logs entries are now written to dedicated log files. See info above for details.

EAP 1 – 21 December 2020

Milestone 7.11.0-m23

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  > General Configuration > Logging and Profiling to give it a try.