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 issue on this page was discovered after the release of 6.3.1.

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

  1. If you use H2 for local development only, as a workaround you can downgrade to the previous version of the database.

    ⚠️ Downgrading in this case means potentially exposing your setup to a known vulnerability in the H2 database (see mvnrepository.com/artifact/com.h2database/h2). ⚠️

  2. A second workaround is to switch to and use the Derby DB instead. In this case, be aware that such a move might create the Too many open files issue, which can occur on some UNIX-based systems.

    For more details and a solution, see Too many open files.
Feedback

DX Core

×

Location

This widget lets you know where you are on the docs site.

You are currently perusing through the DX Core docs.

Main doc sections

DX Core Headless PaaS Legacy Cloud Incubator modules