[MGNLACTIVATION-139] Wrong nodes order after publishing Created: 04/Jan/17  Updated: 20/Aug/19  Resolved: 05/Apr/17

Status: Closed
Project: Activation
Component/s: None
Affects Version/s: 5.4.5, 5.5
Fix Version/s: 5.4.6, 5.5.3

Type: Bug Priority: Major
Reporter: Viet Nguyen Assignee: AntonĂ­n Juran
Resolution: Fixed Votes: 2
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File activation-ordering-author.png     PNG File activation-ordering-public.png    
Issue Links:
Relates
relates to MGNLACTIVATION-140 Problem with order when nodetypes are... Closed
relates to PUBLISHING-62 Nodes order is not respected after pu... Closed
causality
duplicate
is duplicated by MGNLACTIVATION-140 Problem with order when nodetypes are... Closed
relation
is related to PUBLISHING-52 Wrong order after recursive nodes pub... 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
Sprint: Kromeriz 90
Story Points: 2

 Description   

Wrong nodes order after publishing in multiple nodetypes content app.
Steps to reproduce:
Open asset app and create a structure as below:

Publish it to public instance, then the '0' folder has been dropped to the bottom:

Thanks to mchruscielewski for your provided info:

In ActivationCommand, method protected List getOrderingInfo(Content node) builds list of siblings in correct order for reordering after publication, but it will work only if siblings are of the same type. As we can have multiple node types in one content app (like I have here), it cause order problem I experienced.
Please consult somebody if this is expected behaviour, and maybe document it somewhere?
My workaround was to extend activationCommand class and change this sibling type check, to accept all my custom node types.


Generated at Sun Feb 11 23:00:03 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.