-
Improvement
-
Resolution: Unresolved
-
Neutral
-
None
-
None
-
None
- Synchronization skips new nodes. Synchronization requires versioning; versioning is done by default when publishing.
- That may lead to confusion with e.g. unactivated child nodes with modified parent nodes, see for example: https://jira.magnolia-cms.com/browse/MGNLSYNC-42?focusedCommentId=220810&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-220810
- We should improve the
- logging (not throwing exceptions; maybe provide a log of skipped nodes)
- documentation (https://documentation.magnolia-cms.com/display/DOCS/Synchronization+module) by making it more explicit that versioning is required - currently it is only implicitly mentioned as
If content was versioned when it was published (Magnolia default behavior), the module publishes the last known version
Acceptance criteria
