Release notes for Magnolia CMS 6.2.7
Magnolia CMS 6.2.7 is a bug-fixing and security release that also delivers a number of improvements.
The Categories app has been
migrated to the Magnolia 6 UI framework. To ensure backward compatibility,
magnolia-categorization-app-compatibility is bundled in
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
Enabling and using
As part of this effort,
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
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.
- name: multiValueChild # i18n: true fieldType: multiValue field: name: text fieldType: text transformerClass: info.magnolia.ui.form.field.transformer.multi.MultiValueChildNodeTransformer
multiValueChild: $type: jcrMultiValueField # i18n: true itemProvider: class: info.magnolia.ui.editor.MultiValueAsMultipleProperties$Definition field: $type: textField
sortBy property in
jcrDatasource allows you to define a list of JCR
properties for the data source to sort by. Possible values for
sortBy: lastName: ascending firstName: descending
See JCR data source for more information.
As part of this effort, both
BaseDatasourceDefinition have been deprecated.
This means that
sortable can now only be used in
You no longer need to define default actions for detail subapps. The
commit action would equate to the following configuration:
commit: 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
In the Solr module, we have added the
deleteNoIndex property to the
The property allows you to remove pages whose
robots meta tag is set to
noindex. For more information, see Configuration of crawler commands.
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.
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
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.
A browser tab open with Magnolia now shows
<title> | <appName> | <instanceName> instead of
Admincentral - Magnolia. For example:
In the Digital Asset Management module, binary data nodes in the
damworkspace were stored incorrectly as
For this, we have implemented a faster executor (
QueryTask). In case of any inconsistencies when upgrading the module, run the upgrade task manually (MGNLDAM-939).
Exporting and importing content for translation are now supported for switchable and multi fields (MGNLCTS-126). A workaround exists for composite fields (see Partial export of content for translation in multi fields).
An import error occurred when fields that were not defined in
supportedFieldDefinitionswere still exported for content translation (MGNLCTS-131).
When an app was renamed in the registry, the same app appeared twice in the App launcher until restart.
Now any existing app will be deregistered before an app with the same definition location can take its place (MAGNOLIA-7483).
There were some performance issues with the tags column in the browser subapp as every row would fetch all nodes from the
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:
jQuery updated to 3.5.0 (MGNLUI-6634).
Kotlin Standard Library updated to 1.4.21 (EXTDAM-231).
Netty updated to 4.1.59.Final (IMGREC-101).
PDFBox updated to 2.0.23 (BUILD-442).
Tomcat updated to 9.0.43 (MGNLTOMCAT-18).
Vaadin and GridFastNavigation updated to 8.12.4 and 2.6.3 respectively (BUILD-441).
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
A workaround is to remove the
itemProvider configuration from the composite fields.
See the 6.2.7 changelog for all the changes.
Barebones Tomcat Bundle 1.2.4
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
DX Core 6.2.7
External DAM 1.0.5
Image Recognition 1.2.4
Solr Search Provider 5.5.5
Text Classification 1.1.3
Third-party library BOM 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.