Release notes for Magnolia CMS 6.2.7

LTS release • Delivered on March 30, 2021 • Changelog: 20241

Magnolia CMS 6.2.7 is a bug-fixing and security release that also delivers a number of improvements.


Categories app migrated to Magnolia 6 UI

The Categories app has been migrated to the Magnolia 6 UI framework. To ensure backward compatibility, magnolia-categorization-app-compatibility is bundled in magnolia-community-webapp.

The category overview and category cloud templates have been deprecated and moved to magnolia-categorization-app-compatibility. If you still want to use those templates, you have to add the Categories compatibility app to your custom bundle.

There is now a showOptions property in linkField that is set to false by default. For options to appear in a combobox and filtering to work, you have to set both showOptions and textInputAllowed to true.

Enabling and using showOptions with a data source that contains large data sets may lead to performance issues.

As part of this effort, buttonSelectOtherLabel in linkField has been deprecated.

You can now use linkField to select targets both inside and outside Magnolia. For the link field to also work with external targets, you have to set showOptions to false and textInputAllowed to true.

Magnolia 6 UI port for 5 UI MultiValueChildNodeTransformer

As a replacement for info.magnolia.ui.form.field.transformer.multi.MultiValueChildNodeTransformer in 5 UI, you can use jcrMultiValueField with the now deprecated info.magnolia.ui.editor.MultiValueAsMultipleProperties$Definition in 6 UI.

The following configurations in both frameworks will produce the same results.

  • Magnolia 5 UI

  • Magnolia 6 UI

- name: multiValueChild
  # i18n: true
  fieldType: multiValue
    name: text
    fieldType: text
  transformerClass: info.magnolia.ui.form.field.transformer.multi.MultiValueChildNodeTransformer
  $type: jcrMultiValueField
  # i18n: true
    class: info.magnolia.ui.editor.MultiValueAsMultipleProperties$Definition
    $type: textField

New sortBy property in jcrDatasource for sorting direction

The sortBy property in jcrDatasource allows you to define a list of JCR properties for the data source to sort by. Possible values for SortDirection are ascending and descending.

  lastName: ascending
  firstName: descending

See JCR data source for more information.

As part of this effort, both sortable and sortByProperties in BaseDatasourceDefinition have been deprecated. This means that sortable can now only be used in optionListDatasource.

Default commit action for detail subapps

You no longer need to define default actions for detail subapps. The default commit action would equate to the following configuration:

  class: info.magnolia.ui.contentapp.detail.action.SaveDetailSubAppActionDefinition
  browserName: browser

SaveDetailSubAppActionDefinition saves and closes the detail subapp and selects the edited item in the browser. The default value for browserName is browser.

New deleteNoIndex property in cleanSolr command

In the Solr module, we have added the deleteNoIndex property to the cleanSolr command.

The property allows you to remove pages whose robots meta tag is set to noindex. For more information, see Configuration of crawler commands.

Support for passing source locale to content transporter

The API of the Content Translation Support module now allows you to select the source language. The default language is used as the fallback language.

Registry definition access optimized for high throughput

To improve the performance of configuration registries, we have optimized the implementation of AbstractRegistry#getAllProviders(), removed the synchronized keyword from RegistryMap and made the map rely on the thread-safe ConcurrentHashMap instead of the non-synchronized HashMap.

Expanded root folder in asset chooser dialog

In the asset chooser dialog, if there is only a single asset provider, the root folder of that provider will be the root of the whole dialog.

Previously, you had to expand the root folder manually to see its content.

Asset chooser dialogs in 6.2.7 with root folder auto-expanded

Contextual page titles for open tabs

A browser tab open with Magnolia now shows <title> | <appName> | <instanceName> instead of Admincentral - Magnolia. For example:

Title URL


Travel Home | Pages | UAT

supportI18N property deprecated

With this release, the supportI18N property has been deprecated. Setting supportI18N to false is still necessary in certain compatibility configurations (for example, when porting configurations that use Magnolia 5 UI multi field transformers).

Notable bug fixes

Third-party library updates

This release comes with third-party library updates to fix some security and compatibility issues as well as improve performance. The following are the most notable updates:

Security advisory

We have fixed additional issues in the UI module to prevent persistent and non-persistent XSS attacks. We keep the details of those fixes private in line with our security policy. Contact our Support team if you need more information.

MGNLUI-6584 (restricted access)


Known issues

If you are upgrading from an earlier version, read the Upgrading to Magnolia page first and check the Known issues page.

API incompatibility in Content Translation Support module

In the Content Translation Support module, we had to break binary compatibility in to allow support for multiple translation items in multi fields.

We have changed the method signature from

TranslationItem buildTranslationBundle(final Node parentNode, final PropertyToTranslate propertyToTranslate) throws RepositoryException


List<TranslationItem> buildTranslationBundle(final Node parentNode, final PropertyToTranslate propertyToTranslate) throws RepositoryException

Partial export of content for translation in multi fields

When exporting content from multi fields for translation, the exported file will not contain all items of composite fields.

A workaround is to remove the itemProvider configuration from the composite fields.

Documentation screenshot updates

Some of the screenshots in the documentation still show the legacy Magnolia 5 UI. Please bear with us as we work to update them.

Updated modules

  • Barebones Tomcat Bundle 1.2.4

  • Categorization 2.8

  • Community Edition 6.2.7

  • Contacts App 1.8.4

  • Content Editor 1.3.6

  • Content Tags 2.0.3

  • Content Translation Support 2.5.2

  • DAM 3.0.6

  • DX Core 6.2.7

  • External DAM 1.0.5

  • Form 2.7.3

  • Groovy 3.0.1

  • Image Recognition 1.2.4

  • JavaScript Models 1.1.2

  • License 1.7.3

  • Magnolia 6.2.7

  • Mail 5.5.7

  • Pages 6.2.6

  • Personalization 2.0.6

  • Publishing 1.2.5

  • Resources 3.0.3

  • Solr Search Provider 5.5.5

  • Text Classification 1.1.3

  • Third-party library BOM 6.2.7

  • UI 6.2.7

  • Usage Metrics 1.1.2


The Magnolia team would also like to thank everyone who reported issues, contributed patches or simply commented on issues for this release. Your continued interest helps us make Magnolia better. Special thanks go to Simon Aebli, Riste Drangovski, Marty Glaubitz, Antti Hietala, Marc Johnen, Marek Lesiak, David Martin, Frank Sommer, Tom Wespi and Andrey Zavodnik.


DX Core



This widget lets you know where you are on the docs site.

You are currently perusing through the DX Core docs.

Main doc sections

DX Core Headless PaaS Legacy Cloud Incubator modules