Release notes for Magnolia CMS 6.2.11
LTS release • Delivered on July 29, 2021 • Changelog: 11711
Magnolia CMS 6.2.11 is a bug-fixing and security release that also delivers a number of updates and improvements.
Connector Pack and Special Feature updates
-
Analytics Connector Pack 1.1.1 and 1.2.1 released on July 9, 2021.
-
Commerce Connector Pack 1.2.5 and 1.3 released on July 21, 2021 (the latter comes with a new intuitive product chooser).
-
A/B/n Testing 1.0.1 released on July 26, 2021.
See the Connector Pack and Special Feature changelog for details on these releases.
Content Editor 2.0.1 bundled with magnolia-dx-core-demo-webapp
From this release, Content Editor 2.0.1 comes bundled with magnolia-dx-core-demo-webapp
only. As always, the easiest way to
install the module is with Maven.
Improvements
Global and user configuration for home screen
The home screen is what appears by default when a user logs in or closes an app. To configure the home screen globally for
your project, set the homeScreen
property in /modules/admincentral/config.yaml
to APP_LAUNCHER
or FIND_BAR
(default).
See Admincentral module: Configuration.
Additionally, every user can select App launcher or Find Bar suggestions as their home screen. For the user configuration, see Setting home screen.
New form with tabs and fields
You can now use the new info.magnolia.ui.editor.TabWithFieldsFormDefinition
(tabbedForm
) to
configure fields in tabs. This is similar to how a form is defined by default in Magnolia 5 UI.
form:
$type: tabbedForm
tabs:
firstTab:
fields:
foo:
label: foo
$type: textField
secondTab:
fields:
bar:
label: bar
$type: textField
required: true
i18n keys from Magnolia 5 UI are still not compatible with this form and must be reconfigured. |
Item count validation in multi fields
With the new minItems
and maxItems
properties, you can now specify the minimum and maximum number of items in a multi field.
See Common multi field properties for more information.
Node name validation with regular expression pattern
You can now define a regular expression using the new pattern
property in nodeNameValidator
to validate JCR node names. The default value for the property is .+
.
validators:
nodeName:
$type: nodeNameValidator
mode: ADD
pattern: _.+
errorMessage: The name must start with an underscore
See Field validators for more information.
Notable bug fixes
-
The following metadata properties are automatically set again when creating pages and adding items via the detail subapp of any content app (MGNLUI-6766) or when uploading assets via the Magnolia Assets subapp (MGNLDAM-969):
-
mgnl:created
-
mgnl:createdBy
-
mgnl:lastModified
-
mgnl:lastModifiedBy
To recover a missing
mgnl:created
property, update the following Groovy script accordingly:repository = "dam" nodeType = "mgnl:asset" nodes = NodeUtil.asList(() -> QueryUtil.search(repository, "select * from [" + nodeType + "] where [mgnl:created] IS NULL", "JCR-SQL2")) println "found ${nodes.size()} nodes without mgnl:created property" nodes.each{ println "${it.getPath()}" creationDate = it.getProperty("jcr:created").getDate() it.setProperty("mgnl:created", creationDate) if (!it.hasProperty("mgnl:lastModified")) { it.setProperty("mgnl:lastModified", creationDate) } } MgnlContext.getJCRSession(repository).save() return "done"
-
-
You can now also upload an asset to the root level in the asset chooser dialog (MGNLDAM-976).
-
It is again possible to export content with nested multi fields (MGNLCTS-146).
-
Forms are no longer created for all available locales at once. To significantly improve performance, a form is now only created for the currently selected language and every time the user switches to another language (MGNLUI-6724).
-
An exception is no longer thrown when saving multi-language forms where
showOptions
is set totrue
indamLinkField
(MGNLUI-6696). -
To render variant icons more efficiently, personalized pages now use by default the new CachingVariantAwareTitleColumnDefinition (MGNLPN-560).
-
Path-based locking no longer adds a leading slash. Previously, this would cause publication to fail on Windows where JDK would interpret the path as a server host and throw an error about a missing sharename (EEPUBLISH-37, PUBLISHING-122).
java.nio.file.InvalidPathException: UNC path is missing sharename: /\website\/
Third-party library updates
This release comes with the following third-party library updates to fix some security and compatibility issues:
We keep the details of security fixes private in line with our security policy. Contact our Support team if you need more information.
Security advisory
We have fixed a security vulnerability in JDOM to prevent potential XXE attacks. As a result of this, we are releasing Publishing 1.3 to address API-breaking changes in the module.
We keep the details of that fix private in line with our security policy. Contact our Support team if you need more information.
MAGNOLIA-8134 (restricted access)
Others
Known issues
If you are upgrading from an earlier version, read the Upgrading to Magnolia page first and check the Known issues page.
Updated modules
-
Advanced Cache 2.3.4
-
Campaign Publisher 2.0
-
Community Edition 6.2.11
-
Content Editor 1.3.9, 2.0.1
-
Content Tags 2.0.4
-
Content Translation Support 2.5.4
-
DAM 3.0.9
-
Demo Projects 1.6.2
-
DX Core 6.2.11
-
GraphQL 1.0.1
-
Language Bundles 1.1.5
-
Magnolia 6.2.11
-
Mail 5.5.8
-
Marketing Tags Manager 1.4.4
-
Pages 6.2.10
-
Personalization 2.0.9
-
Publishing 1.3
-
Publishing Transactional 1.1.1
-
Repository Tools 1.9.2
-
REST Framework 2.2.8
-
RSS Aggregator 2.6.4
-
Soft Locking 3.1
-
Third-party library BOM 6.2.11
-
UI 6.2.11
Acknowledgements
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 Christopher Chard, Riste Drangovski, Boris Faniuk, Marty Glaubitz, Stefan Jahn, Matthias Jakob, Pierre Sandrin, Daniel Schneeberger, René Schubert, Bence Vass and Jeffrey van der Heide.