[MGNLSYNC-45] Synchronisation of new nodes - improve logs & docu Created: 02/Jun/20  Updated: 02/Dec/22

Status: Open
Project: Magnolia Synchronization Module
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Neutral
Reporter: Simon Lutz Assignee: Dominik Maslanka
Resolution: Unresolved Votes: 0
Labels: maintenance, versioning
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Epic Link: Maintenance of Synchronization module
Team: Nucleus

 Description   
  • Synchronization skips new nodes. Synchronization requires versioning; versioning is done by default when publishing.
  • 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


Generated at Mon Feb 12 07:39:20 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.