[DOCU-2191] Provide more details behaviors when can't synchronise node has been renamed on author and is not present on public) Created: 03/Jun/21  Updated: 01/Jul/21  Resolved: 01/Jul/21

Status: Closed
Project: Documentation
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Neutral
Reporter: Oanh Thai Hoang Assignee: Martin Drápela
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: 0.5h
Original Estimate: Not Specified

Attachments: PNG File after-msg.png     PNG File before-msg.png    
Issue Links:
documentation
documents MGNLSYNC-58 Synchronisation may output error mess... Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:

 Description   

Here is detail behaviors after improving.

User should config notifications group to receive exception msg in Notifications app. 

Before behaviors:

  • The sync will stop immediately when found one renamed/moved node (nodes has been renamed on author and is not present on public)
  • No meaning full log error. See 
    ERROR info.magnolia.module.scheduler.CommandJob : Cannot execute command [synchronize] for job [Synchronization] in catalog [synchronization]
    
  • Users in notifications group will receive one notification msg as below:

 

After improving:

  • Don't stop sync. Continue to sync for normal nodes. After finishing sync, 1 log warning will show all the list of moved nodes that can't sync. 
    info.magnolia.synchronization.commands.SynchronizationCommand 31.05.2021 11:06:56 – The following paths [/node1/node3, /node1/node10] have been moved from the last published original path. Please, publish manually before synchronising.
    
  • Users in notifications group will receive one notification msg as below:

 

NOTE: Update both 6.2 and 5.7 docs.



 Comments   
Comment by Julie Legendre [ 17/Jun/21 ]

Documented in 5.7.11 release notes: https://documentation.magnolia-cms.com/display/DOCS57/Release+notes+for+Magnolia+CORE+5.7.11

Generated at Mon Feb 12 01:24:51 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.