Magnolia 6.3.0 known issues
Refer to the Known issues section of the Release notes for Magnolia CMS 6.3 for information about issues that existed upon the release of 6.3.0 and are being addressed in the next 6.3 maintenance releases.
The issues on this page were discovered after the release of subsequent 6.3.x versions.
Variants unintentionally valued
Switching between variants during editing replaces the target variant being edited with the current value, even if the changes are not saved. This behavior can result in unintended updates to the target variant.
If you use variants, we recommend waiting until the release of Magnolia 6.3.2.
A fix for this issue is delivered with MGNLUI-9095.
H2 database: Persistence or corruption problems
If you’re using the H2 database, you may experience occasional persistence or corruption problems. To follow the latest development of this issue, please see MAGNOLIA-9522.
We don’t recommend using H2 for production environments. For a list of production-supported databases, see Certified stack: Databases. Workarounds
|
Performance issues with the Assets app
Some customers have reported performance problems with the Assets app after upgrading to version 6.3.2, particularly when working with large datasets. The issue arises when the system generates thumbnails for .png images, which can result in higher memory usage and potential performance degradation.
This issue affects all 6.3.x versions and is addressed in 6.3.4 with MGNLUI-9115.
There is no workaround available. If you manage a large number of .png assets, we recommend postponing upgrades until the fix is available. |