[PUBLISHING-117] DOC: Document new default ordering of nodes on public instance Created: 17/May/21  Updated: 29/Mar/22  Resolved: 10/Jun/21

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

Type: Task Priority: Neutral
Reporter: Federico Grilli Assignee: Ashraf Khamis
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
documentation
documents PUBLISHING-82 Wrong order of nodes after publishing... Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:
Epic Link: Order of nodes after publishing
Sprint: UI FW 30
Story Points: 2
Team: Nucleus

 Description   

All siblings of the published node are ordered as part of the publication process according to the actual order on the author instance at the time of publication approval.

Be aware that this does not take into account order at any other point in time, such as time of the published version creation (as this order might be already obsolete by publication of other versions).

The original behavior can be restored by setting /modules/publishing-core/config@orderSiblings=false. For details, Roman is the man

NOTE: Update both 6.2 and 5.7 docs.



 Comments   
Comment by Ashraf Khamis [ 10/Jun/21 ]

Added a section about the default ordering of nodes on the public instance to the 6.2 and 5.7 DOC spaces:

Reviewed by Roman.

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