Page History
...
When a new version of a content node is created in one workspace, the improved Magnolia observation mechanism (info.magnolia.observation.*) makes sure that Magnolia does not react unnecessarily to any event that creates a node in /jcr:system.
...
Targeted notifications when node synchronization fails
In the Synchronization module, the following have been implemented to improve synchronization when nodes are moved or renamed:
...
failure occurs when you rename a node or move it between different subtrees. A workaround is to publish any problematic node manually before syncing again.
When synchronization fails, a notification is sent to configured users. To allow notifications for certain users, in the modules/synchronization-app/config folder, create a user group called notificationGroups and add
...
a list of string properties
...
to it. Each property represents the user group name you wish to notify.
Third-party library updates
...
Overview
Content Tools