Magnolia 5.6 reached end of life on June 25, 2020. This branch is no longer supported, see End-of-life policy.
Magnolia CORE 5.6.7 corrects security vulnerabilities, several bugs and also brings the following changes and improvements:
This release fixes an issue occurring in Magnolia 5.6.6 where exporting an XML bootstrap file opens the file directly in the active browser window instead of offering a download dialog. The issue does not appear for YAML format exports.
To make sure that fields are not broken by ignoring existing decorations of deprecated field definitions, we have changed the logic of registering field type definitions by prioritizing decorated definitions. The field registration process now follows this order:
Since Magnolia 5.6.3 the Definitions app reports many types of deprecated or non-existing items. With the current release it also reports references to non-existing and deprecated block definitions.
This release also comes with the property called dialogLabelItemProperty already introduced with Magnolia 5.7. It allows you to set a dialog's name via a property holding the preferred value for the dialog caption, for example via the jcrName property. If no dialogLabelItemProperty is configured for the dialog, Magnolia tries to retrieve the dialog's name from the language bundle associated with the dialog.
You can see the new property implemented in the Security app dialogs for example.
In Magnolia 5.6.7, the new dialogLabelItemProperty property is set:
As a result, the dialog's caption now shows eric which is the value of the jcrName property for the dialog:
For comparison, here's the same dialog in older Magnolia 5.6.6, where the property is not available and the "User" caption of the dialog is defined with security-app.user.label=User in the app's language bundle:
Magnolia 5.6.7 updates magnolia-module-groovy to version 2.6.3 for security reasons. It ships Apache Groovy 2.4.15.
We have fixed several security issues with this release. We keep details of this kind of fix private in line with our Security Policy. Contact our Support team if you need more information.
MGNLPN-422, MGNLDAM-754 ( restricted access)
If you are upgrading from an earlier version, read the Upgrading to Magnolia 5.6.x page first and check the Known issues section on it.
See the 5.6.7 changelog for all the changes.
Please be aware that the version numbers for the Magnolia main and UI projects are not in sync with the version number of this release.
If you are updating from an earlier version:
Projects based on an older maven archetype may not build correctly starting with Magnolia 5.6.3 - because the version of the Magnolia main modules is not the same as the Magnolia bundle anymore. If you experience a problem, please update your project parent pom.
info.magnolia.ui.form.field.factory.TwinColSelectFieldFactory - An old deprecated constructor has been removed. (See diff.)
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 Nils Breunese, Arne Diekmann, Thomas Duffey, Gernot Fussan, Rico Jansen, Michiel Meeuwissen, Frank Sommer, James Spence and Tom Wespi.