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.
Better synchronization when nodes are moved or renamed
In the Synchronization module, the following have been implemented to improve synchronization when nodes are moved or renamed:
- When a node is published, the publication path is stored in JCR.
- When a node has a publication path different from the one stored, run synchronization fails.
- When synchronization fails, a notification is sent to configured users. To allow notifications for certain users, in the
modules/synchronization-app/configfolder, create a group callednotificationGroupsand add to it a list of string properties. - When an error occurs, you can publish failing nodes manually as a workaround.
Third-party library updates
...
Overview
Content Tools