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.
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.
New showOptions property in link field
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 |
As part of this effort, buttonSelectOtherLabel in linkField has been deprecated.
Using link field for external targets
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.
- name: multiValueChild
# i18n: true
fieldType: multiValue
field:
name: text
fieldType: text
transformerClass: info.magnolia.ui.form.field.transformer.multi.MultiValueChildNodeTransformermultiValueChild:
$type: jcrMultiValueField
# i18n: true
itemProvider:
class: info.magnolia.ui.editor.MultiValueAsMultipleProperties$Definition
field:
$type: textFieldNew 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.
sortBy:
lastName: ascending
firstName: descendingSee 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:
commit:
class: info.magnolia.ui.contentapp.detail.action.SaveDetailSubAppActionDefinition
browserName: browserSaveDetailSubAppActionDefinition 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.
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 |
|---|---|
|
|
|
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
-
In the Digital Asset Management module, binary data nodes in the
damworkspace were stored incorrectly asmgnl:contentNodeinstead ofmgnl:resource.
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). -
In the Content Translation Support module:
-
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).
-
Exporting content for translation is now also possible for rich text fields (MGNLCTS-128).
-
An import error occurred when fields that were not defined in
supportedFieldDefinitionswere still exported for content translation (MGNLCTS-131). -
NullPointerExceptionwas thrown when a multi field contained fields that should not be translated (MGNLCTS-132).
-
-
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
tagsworkspace (MGNLUI-6569).
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:
-
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).
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)
Others
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 info.magnolia.translation.io.ExportVisitor#buildTranslationBundle
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 RepositoryExceptionto
List<TranslationItem> buildTranslationBundle(final Node parentNode, final PropertyToTranslate propertyToTranslate) throws RepositoryExceptionPartial 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.
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
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 Simon Aebli, Riste Drangovski, Marty Glaubitz, Antti Hietala, Marc Johnen, Marek Lesiak, David Martin, Frank Sommer, Tom Wespi and Andrey Zavodnik.