[MGNLSYNC-58] Synchronisation may output error message during ordering nodes if content has been renamed on author and is not present on public Created: 26/Nov/20  Updated: 29/Mar/22  Resolved: 03/Jun/21

Status: Closed
Project: Magnolia Synchronization Module
Component/s: None
Affects Version/s: 1.9.1
Fix Version/s: 1.9.2

Type: Bug Priority: Neutral
Reporter: Jaroslav Simak Assignee: Oanh Thai Hoang
Resolution: Fixed Votes: 0
Labels: VN-Analysis, VN-Implementation, cs-bk, maintenance
Remaining Estimate: 0d
Time Spent: 3d 56m
Original Estimate: Not Specified

Issue Links:
Relates
documentation
to be documented by DOCU-2191 Provide more details behaviors when c... Closed
relation
is related to MGNLSYNC-51 Synchronisation may fail when nodes a... Closed
is related to PUBLISHING-82 Wrong order of nodes after publishing... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[X]* Doc/release notes changes? Comment present?
[X]* Downstream builds green?
[X]* Solution information and context easily available?
[X]* Tests
[X]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[X]* Steps to reproduce, expected, and actual results filled
[X]* Affected version filled
Release notes required:
Yes
Documentation update required:
Yes
Date of First Response:
Epic Link: Order of nodes after publishing
Sprint: Maintenance 60, Maintenance 61
Story Points: 5
Team: Nucleus

 Description   

Steps to reproduce

  1. Create a node under the root called “node1”.
  2. Create a node under “/node1" called “node2” (path to the node is: /node1/node2).
  3. Publish each nodes couple of times, so that they have a version history.
  4. Go to public instance and remove /node1/node2
  5. Rename “node2" to “node3” and start synchronization of “node3" (do not publish “node3”, let it stay in modified state)  

Expected results

No error in logs, node order is preserved.

  • Don't stop sync. Continue to sync for normal nodes. After finishing sync, log warning will show all the list of moved nodes that can't sync.
  • Exception notification will send the list of move nodes only 1 time instead of multiple times according to number of moved node as before

Actual results

Errors in logs, node order may be broken.

Workaround

Publish content before synchronizing.

Development notes

Transferred node name in the xml used to describe the content is not correct because it's taken from actual node, and not the versioned one.
Packager#addResources that is responsible for building the xml should take versioned node name into account, not the actual node name.
Also it would be worth checking if it’s possible to get the original path of the versioned node and set that one as well (in case it’s a renamed moved node)
Finally, consider emphasising in docu that synchronization != publication so that users don’t expect yellow nodes / red nodes to be synced to public in the exact same state as they are on author



 Comments   
Comment by Oanh Thai Hoang [ 03/Jun/21 ]

Docu update can be found in https://jira.magnolia-cms.com/browse/DOCU-2191 :Bow

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