[PUBLISHING-82] Wrong order of nodes after publishing single page Created: 23/Apr/20  Updated: 29/Mar/22  Resolved: 17/May/21

Status: Closed
Project: Publishing
Component/s: None
Affects Version/s: 1.1.5, 1.2.4
Fix Version/s: 1.1.9, 1.2.6

Type: Bug Priority: Neutral
Reporter: Jaroslav Simak Assignee: Roman Kovařík
Resolution: Fixed Votes: 10
Labels: maintenance
Remaining Estimate: Not Specified
Time Spent: 2h 14m
Original Estimate: Not Specified

Attachments: PNG File Screenshot 2020-03-19 at 14.29.50.png     PNG File Screenshot 2020-03-19 at 14.30.00.png     PNG File Screenshot 2020-03-19 at 16.58.06.png     PNG File Screenshot 2020-03-19 at 16.58.16.png    
Issue Links:
Cloners
clones PUBLISHING-79 Wrong order of nodes after publishing... Closed
Problem/Incident
is caused by PUBLISHING-52 Wrong order after recursive nodes pub... Closed
Relates
causality
is causing PUBLISHING-129 mgnl:lastModified Metadata Property I... Closed
documentation
to be documented by PUBLISHING-117 DOC: Document new default ordering of... Closed
duplicate
duplicates MGNLDAM-794 Incorrect status icons after moving f... Closed
relation
is related to MGNLSYNC-58 Synchronisation may output error mess... 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 55, Maintenance 56, Maintenance 57
Story Points: 13
Team: Nucleus

 Description   

Steps to reproduce (taken from PUBLISHING-62)

1. Create 4 nodes (names 1-4 and in that order) on the same level, publish them all.
2. Move node 1 between 3 and 4.
3. Move node 2 between 3 and 1.
4. Publish node 2.
5. Publish node 1.
6. See the difference between author and public

Note: the order can be fixed by publishing node 3 as well.

Most likely there's insufficient ordering info we send during the activation process (only the siblings are included and not the whole structure).

Old description which was probably copied from wrong ticket:

Steps to reproduce:

  • create page tree
  • publish everything
  • check node order on public instance
  • modify page3, page4, page5 so they have orange status
  • publish page2
  • observe wrong order of nodes on public instance

Meeting minutes 2020-04-06



 Comments   
Comment by Thomas Martin [ 22/Oct/20 ]

Hi,

this bug causes us some headache, as the order of nodes is sometimes important, how a page is rendered (e.g. different order of menu items on author and public instance).

When will this be fixed? Or is there a workaround beside manual intervention (reordering on public, publishing the parent node)?

Comment by Chris Jennings [ 16/Dec/20 ]

Hello,

This is causing issues when managing configuration as well.

A UK client on Cloud One has recently experienced a problem with the filter chain. After creating a new CORS filter in the author filter chain, they published it and saw it had no effect. On investigating, the filter was found at the bottom of the public instances' filter chains.

Publishing the entire chain (recursively publishing /filters) will preserve the order but then requires the author and public instances to have identically configured filter chains. It also moves the /filters node to be the last child of /server which is inconvenient when you need to manually view the config workspace.

Comment by Chris Jennings [ 16/Dec/20 ]

Still present in 1.2.4 (verified via demo.magnolia.cms.com)

Comment by Mercedes Iruela [ 11/Feb/21 ]

Workaround: To make sure that the orders of nodes on both instances are aligned, always publish the parent node of the node(s) that have been moved.

Comment by Roman Kovařík [ 28/Apr/21 ]

Is somebody able to reproduce this on latest http://localhost:8080/.magnolia/admincentral#app:pages-app:browser;::?

Is some information missing to reproduce (e.g. is has workflow to be used or is this reproducible e.g. via JCR browser)?

Edit: description updated and reproducible.

Comment by CysNET Software [ 30/Apr/21 ]

Hi:

I think we are being affected by this issue. We are using Publisihing 1.1.8 on Magnolia 5.7.9 EE Pro. Our customer is experimenting issues like this one. 

  • Is there any solution without having to publish the parent node and his children?
  • Is there an estimated resolution date?

Kind regards,
Gabri

Comment by Federico Grilli [ 18/May/21 ]

cysnet Hi Gabri, we plan to release Magnolia 5.7.11 in the second half of June but publishing 1.1.9 (as well as publishing-transactional 1.1 which depends upon the latter) should be released earlier as single modules.
As an EE customer, Support should notify you of relevant releases, if you have any open support ticket related to this issue. 

Hope this helps,

Federico for the Magnolia team

Comment by CysNET Software [ 19/May/21 ]

Thank you for your information Federico.

We will wait for the Magnolia 5.7.11 release and the release of the modules 

Generated at Mon Feb 12 10:35:14 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.