Magnolia 5.6 reached end of life on June 25, 2020. This branch is no longer supported, see End-of-life policy.
This Magnolia release fixes several bugs and delivers the following improvements:
The Synchronization module allows you to synchronize content nodes on a target Magnolia instance with a source instance.
Previously, the last created version of a node was synchronized; not necessarily the version approved and published in the workflow. In Magnolia 5.6.1, the last published version of a content node is synchronized. The new mgnl:lastActivatedVersion property stores the version when the node was published.
Note that only nodes published with the latest versions of Magnolia Core and Publishing module can be synchronized to the version set in mgnl:lastActivatedVersion. Content published using older versions of the modules is still synchronized to the last created version of the node.
This release adds the application/javascript media type (see sections 3 and 7.2 of RFC4329: Scripting Media Types), which makes sure that JavaScript files can be sent compressed in the gzip encoding format.
The configuration is defined under:
/modules/cache/config/contentCaching/defaultPageCache/browserCachePolicy/policies/resources/voters/contentType/allowed/modules/cache/config/compression/voters/contentType/allowedIn previous releases, the media type for JavaScript was defined as application/x-javascript, which did not compress JavaScript resources for HTTP transport.
Changes in the light modules folder now flush the server cache. This benefits light developers as you no longer have to flush the cache manually. Changes in light modules take effect immediately.
This behavior can be configured under:
/modules/cache/config/contentCaching/defaultPageCache/flushPolicy/policies/lightModule/pathToCacheMappings/defaultPageCache
Use the pattern property to specify the pattern for the operation. Its default value is .*/(templates|webresources|i18n)/.*.
The code of createAppScript, a Groovy script available in Dev > Groovy, has been updated to be compatible with the Publishing module.
See the 5.6.1 changelog for all the changes.
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.
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.