Magnolia 6.3.11 known issues
Marketing Tags update task may lead to instance stalling
Upgrading to Magnolia 6.3.9, 6.3.10, 6.3.11, or 6.3.12 initiates a Marketing Tags version handler task that may cause instances to become unresponsive if the repository contains a large number of versions.
This issue is caused by MGNLTAGS-127 Page Template setting isn’t working and is fixed in the Magnolia 6.3.13 release with ticket MAGNOLIA-9701 NodeVisitorTasks iterates over the entire jcr:system tree.
| If you have already upgraded to 6.3.9 or later, this issue will not affect you. |
We apologize for any inconvenience caused.
Unexpected change in Nodes API
An unexpected change introduced by ticket MGNLREST-877 Introduce JacksonContextResolver to consistent JSON serialization affects the Nodes API functionality in Magnolia 6.3.11.
Affected functionality in more detail
-
The Nodes API operation is broken, impacting users who rely on this API to retrieve content.
-
The Nodes API - PUT and POST operations are also broken, resulting in error messages such as:
Unrecognized field 'properties' (class info.magnolia.rest.service.node.v1.RepositoryNode), not marked as ignorable
This issue is fixed in 6.3.12. We apologize for any inconvenience caused and appreciate your patience while we resolve this issue.