[PUBLISHING-52] Wrong order after recursive nodes publication with different node type Created: 31/Aug/18  Updated: 29/Mar/22  Resolved: 06/Sep/19

Status: Closed
Project: Publishing
Component/s: None
Affects Version/s: 1.0.5
Fix Version/s: 1.0.8, 1.1.2

Type: Bug Priority: Neutral
Reporter: Jonathan Ayala Assignee: Aleksandr Pchelintcev
Resolution: Fixed Votes: 2
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File AUTHOR.png     PNG File PUBLIC.png    
Issue Links:
Problem/Incident
causes PUBLISHING-79 Wrong order of nodes after publishing... Closed
causes PUBLISHING-82 Wrong order of nodes after publishing... Closed
Relates
relates to PUBLISHING-62 Nodes order is not respected after pu... Closed
causality
relation
is related to MGNLACTIVATION-139 Wrong nodes order after publishing 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
Date of First Response:
Epic Link: Order of nodes after publishing
Sprint: Maintenance & Releases
Story Points: 2
Team: Nucleus

 Description   

When publishing recursively a node and its children having those different node types, order is not preserved in the public instance.

Steps to reproduce:

  1. From JCR browser create a node of type folder in any workspace.
  2. Create different child nodes with different types
  3. Publish node created in step 1 with subnodes
  4. Go to Public instance and check that the order is not preserved

Repeat these steps without changing node types, now order is preserved in the public instance.

The attached AUTHOR.png shows test-ordering node with different types and test-ordering2 with same type. In the PUBLIC picture it can be seen that the order is not preserved.

It seems that info.magnolia.publishing.sender.AbstractSender.getOrderingInfo(Node) method takes into account the type of node by calling info.magnolia.jcr.util.NodeUtil.getSiblingsAfter(Node, String) 

This problem was already fixed in Activation Module (not yet applied to Publishing). Check linked tickets.



 Comments   
Comment by Thomas Duffey [ 09/Jan/19 ]

Is it possible this is also a problem with nodes of the same type? Experiencing this on SUPPORT-9474

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