Release notes for Magnolia CMS 6.2.54
LTS release • Delivered on January 6, 2025 • Changelog: 14830
Magnolia 6.2.54 is primarily a bug-fixing and security release, delivering also performance improvements for caching, JCR observation, and publishing.
As with any Magnolia release, this release also delivers critical bug and security fixes. We keep the details of security fixes private in line with our security policy. Contact our Support team if you need more information.
Announcements
-
Solr module
6.1.12
released on December 5, 2024. -
Image Focal module
2.4.12
released on December 10, 2024. -
Content Translation Support Extended module
3.4.15
released on December 12, 2024. -
Hybrid Assets module
2.0.15
released on December 17, 2024.
Improvements
Caching and JCR observations
We’ve optimized caching performance through new FlushFromPublishingEvent
policies (FlushAllFromPublishingEventPolicy
and SiteAwareFlushFromPublishingEventPolicy
) that intelligently reduce JCR observation resource usage when publishing events occur.
For more, see SiteAwareFlushFromPublishingEventPolicy and FlushAllFromPublishingEventPolicy.
-
MGNLADVCACHE-139 Introduce new flush policy and rely on completion of publish process to flush cache per site
-
MGNLCACHE-399 Introduce new flush policy and do execute flush when receiving publishing events
To improve the overall system performance even further, we’ve integrated optimizations to reduce the number of events triggered.
-
MAGNOLIA-9533 Optimize
config
workspace observation setup
Publishing
-
PUBLISHING-352 The publication thread pool’s size should be configurable for performance
For more, see Thread pool size.
-
PUBLISHING-355 Receivers whitelist isn’t strictly respected
For more, see Defining trusted publishing receivers.
Miscellaneous
-
MGNLREST-836 Use latest
javax.json
dependencies -
MGNLTOMCAT-49 Update
org.apache.tomcat:tomcat
dependency to9.0.98
Third-party library updates
This release comes with third-party library updates, see the Magnolia Third-party library BOM 6.2.54.
Notable updates
-
BUILD-1298
org.bouncycastle:*
to1.79
-
BUILD-1300
javax.json
to1.1.5-magnolia
The fix in
javax.json
introduces a new configuration propertyorg.eclipse.parsson.maxDepth
to limit the maximum level of nesting when parsing a JSON string. The default value is1000
.You can set it as a system property and pass it to the JVM as follows:
-Dorg.eclipse.parsson.maxDepth=<value>