[MGNLSYNC-51] Synchronisation may fail when nodes are moved into different sub trees Created: 08/Oct/20  Updated: 29/Mar/22  Resolved: 03/Dec/20

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

Type: Bug Priority: Neutral
Reporter: Jaroslav Simak Assignee: Jorge Franco
Resolution: Fixed Votes: 0
Labels: cs-bk, maintenance
Remaining Estimate: 0d
Time Spent: 0.25d
Original Estimate: Not Specified

Issue Links:
Relates
relates to MGNLSYNC-52 Improve information the user gets via... Closed
dependency
depends upon MAGNOLIA-7935 Store original path versioning Closed
documentation
to be documented by DOCU-2067 Add information to the user about imp... Closed
relation
is related to PAGES-357 DOC: Best practice for moving pages a... Closed
is related to MGNLSYNC-58 Synchronisation may output error mess... Closed
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)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Release notes required:
Yes
Documentation update required:
Yes
Date of First Response:
Epic Link: Support
Sprint: Maintenance 30, Maintenance 31, Maintenance 32, Maintenance 33, Maintenance 34, Maintenance 35, Maintenance 36
Story Points: 5
Team: Nucleus

 Description   

Investigation: initial estimate 3sp


Investigation outcome and action taken

Failure happens when you move/rename a node between different subtrees. There is a workaround: you can publish by hand the node with problems and then sync again.

As there is a workaround, first we are going to improve communication to the user. When user launches synchronization process and there is an error related to this problem, we will send a notification to the user with the error, description of the problem and way to fix manually starting a publish of parent. Later we will review the api way to launch synchronization to give similar information in the response.



 Comments   
Comment by Jorge Franco [ 22/Oct/20 ]

It fails when you move/rename a node between different subtrees. There is a workaround, you can publish by hand the node with problems and then sync again.

Comment by Jorge Franco [ 22/Oct/20 ]

As there is a workaround, first we are going to improve communication to the user. When user launch synchronization process and there is an error related to this problem, we will send a notification to the user with the error, description of the problem and way to fix manually starting a publish of parent. Later we will review the api way to launch synchronization to give similar information in the response.

Comment by Jorge Franco [ 27/Oct/20 ]

Created MGNLSYNC-52 to improve error information via REST.

Comment by Jorge Franco [ 26/Nov/20 ]

Implemented solution:

  • Now when a node is published, publication path is stored in Jcr.
  • When you run synchronization and a node has different path that stored, synchronization fails.
  • When synchronization fails, a notification is sent to groups configured.
  • You can configure groups to receive this notifications in: modules/synchronization-app/config folder. A content group called notificationGroups, and inside a list of string properties.
  • When an error occurs, as a workaround you can publish failing node manually.

 

I have created DOCU-2067 to document this improvement.

Comment by Ashraf Khamis [ 14/Dec/20 ]

For 5.7.9 & 6.2.6 release notes:

https://documentation.magnolia-cms.com/display/DOCS57/Release+notes+for+Magnolia+CORE+5.7.9#ReleasenotesforMagnoliaCORE5.7.9-Targetednotificationonsynchronizationfailure

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