This Magnolia release fixes several bugs and delivers the following improvements:
Synchronizing to the last published version
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
gzip encoding format.
The configuration is defined under:
Changes in light modules folder trigger cache flushing
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:
pattern property to specify the pattern for the operation. Its default value is
Update of Groovy createAppScript
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.
- Cache 5.6.1
- Community Edition 5.6.1
- Content Editor 1.1.1
- Content Tags 1.0.1
- Demo Projects 1.2.1
- Enterprise Edition 5.6.1
- Groovy 2.6.1
- Magnolia 5.6.1
- Personalization 1.5.1
- Publishing 1.0.1
- REST Framework 2.0.1
- SiteMesh 1.1.2
- Synchronization 1.8.1
- Templating Samples 5.4.1
- Third-party library BOM 5.6.1
- UI 5.6.1
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.