• Type: Bug
• Resolution: Fixed
• Priority: Major
• Fix Version/s: 4.0M10
• Affects Version/s: None
• Component/s: None
• Labels:

  None

1. 

   step5-backoffice.PNG

   4 kB

   13/Oct/15 12:13

2. 

   step5-frontoffice.PNG

   4 kB

   13/Oct/15 12:13

[CMS-6631] Wrong position of a page in the main section

Collapse comment: Thibaut Rizzi (Inactive) added a comment - 29/Oct/15 18:34

Thibaut Rizzi (Inactive) added a comment - 29/Oct/15 18:34

Changed fix version from 4.0beta to 4.0 because the changes are identified as too risky for the moment.

Expand comment: Thibaut Rizzi (Inactive) added a comment - 29/Oct/15 18:34

Thibaut Rizzi (Inactive) added a comment - 29/Oct/15 18:34 Changed fix version from 4.0beta to 4.0 because the changes are identified as too risky for the moment.

Collapse comment: Thibaut Rizzi (Inactive) added a comment - 16/Oct/15 19:03, Edited by Thibaut Rizzi - 16/Oct/15 19:11

Thibaut Rizzi (Inactive) added a comment - 16/Oct/15 19:03 - edited

The technical reason is that during live synchronization, ancestor node that need to be created in the live are not re-ordered.

In SynchronizeComponent.synchronizePage, we do:

1. cloneAncestorsAndPreserveUUID -> the ancestor page (and other nodes if necessary) is created but not reordered (remain the last child)
2. cloneEligiblePage -> the current page is created and immediately after re-ordered with _cloneComponent.orderNode

I added a FIXME comment in the SynchronizeComponent line 581.

Expand comment: Thibaut Rizzi (Inactive) added a comment - 16/Oct/15 19:03, Edited by Thibaut Rizzi - 16/Oct/15 19:11

Thibaut Rizzi (Inactive) added a comment - 16/Oct/15 19:03 - edited The technical reason is that during live synchronization, ancestor node that need to be created in the live are not re-ordered. In SynchronizeComponent.synchronizePage , we do: cloneAncestorsAndPreserveUUID -> the ancestor page (and other nodes if necessary) is created but not reordered (remain the last child) cloneEligiblePage -> the current page is created and immediately after re-ordered with _cloneComponent.orderNode I added a FIXME comment in the SynchronizeComponent line 581.