Magnolia CMS 6.1.4 brings bug fixes, security updates and several usability improvements.
Depth of reference resolution in REST is configurable
With the new
referenceDepth property, you can configure the REST Delivery endpoint API v2 to provide more than one level of reference resolution. In addition, you can toggle the
referenceRepeat property to enable resolution of self-references into fully expanded nodes. For more details, see the configurable API v2 properties.
New configuration options for Find Bar
By listing user roles under the
editorRoles property, you can also mitigate a filter performance issue occurring if a large number of public users are registered in a shared user repository on the author instance. To further eliminate this performance issue, we have implemented a mechanism that fires up Find Bar filter querying only after a filter menu is accessed.
Multivalue fields can be exported again
This release also fixes a bug in the Content Translation Support module that prevented multivalue fields from being exported even though they were registered as additional field types.
Custom CKEditor configurations work correctly
Previously, custom CKEditor configurations coming from a JS file specified using the
configJSFile property were applied inconsistently in rich text fields. This has been fixed in this release as well.
Some of the screenshots in the documentation still show the legacy Magnolia 5 UI. Please bear with us as we work to update them.
See the 6.1.4 changelog for all the changes.
- Community Edition 6.1.4
- Content Translation Support 2.4.1
- DAM 2.6.1
- DX Core 6.1.4
- Magnolia 6.1.4
- Periscope 1.1.1
- Publishing 1.1.3
- Publishing Transactional 1.0.4
- REST Framework 2.1.4
- Third-party library BOM 6.1.4
- UI 6.1.4
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 Jarkko Mantysaari and Will Scheidegger.