[MGNLACTIVATION-140] Problem with order when nodetypes are not the same Created: 04/Jan/17  Updated: 16/Mar/17  Resolved: 16/Mar/17

Status: Closed
Project: Activation
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Karel de Witte Assignee: Unassigned
Resolution: Duplicate Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MGNLACTIVATION-139 Wrong nodes order after publishing Closed
duplicate
duplicates 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:

 Description   

Investigate why the same nodetype ordering is still necessary, and remove otherwise the same nodetype ordering. Customers Photobox, vi.nl etc all have this issue when having nodes of different nodetypes in certain order on author.

[2:28 PM] Karel De Witte: while (nodeIterator.hasNext()) {
                Node sibling = nodeIterator.nextNode();
                if (sibling.isNodeType(thisNodeType))

{                     siblings.add(sibling.getUUID());                 }

            }
[2:28 PM] Karel De Witte:

in ActivationCommand



 Comments   
Comment by Mariusz Chruscielewski [ 04/Jan/17 ]

I think it should be linked with my support request:

https://jira.magnolia-cms.com/browse/SUPPORT-7059

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