Magnolia 6.3.1 known issues
Some in-app search fields and filters not working
We’re investigating an issue with the search improvements introduced in 6.3.1. In-app search for the following apps isn’t working as expected due to a build issue:
-
Definitions app
-
Resource Files app
-
Tasks app
For more details, see:
If you rely on search in these apps, please wait until the release of Magnolia 6.3.2. We’re actively working on resolving the issues.
Assets can’t be loaded or served
This issue is caused by the upgrade of the commons-io library to version 2.17.0, where the constructor of AutoCloseInputStream changed to
...
public AutoCloseInputStream(InputStream in) {
super(ClosedInputStream.ifNull(in));
}
...A fix for this issue will be delivered as BUILD-1297.
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.
Performance issues with the Assets app
| This issue is described in the Magnolia 6.3.0 known issues. It is addressed in 6.3.4 with MGNLUI-9115. |