[MAGNOLIA-6436] FilterOrderingTask doesn't work with nested filters Created: 05/Nov/15  Updated: 15/Mar/22  Resolved: 15/Mar/22

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: 5.4.2
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Roman Kovařík Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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   

FilterOrderingTask doesn't allow to order nested filters such config:server/filters/cms/myFilter.

The cause: info.magnolia.module.delta.FilterOrderingTask#getLastChild looks only for direct children instead of collecting all descendants.

Workaround: Use MoveNodeTask and then FilterOrderingTask.



 Comments   
Comment by Richard Gange [ 07/Dec/17 ]

This can be easily worked around using info.magnolia.i18n.url.translation.setup.OrderNodeAfterTask

//private final FilterOrderingTask placeURLtransFilter = new FilterOrderingTask("urltrans", new String[] { "repositoryMapping" });
// becomes
    private final OrderNodeAfterTask placeURLtransFilter = 
            new OrderNodeAfterTask(
                    "Place urltrans filter", 
                    "/server/filters/cms/urltrans", 
                    "repositoryMapping");
Generated at Mon Feb 12 04:14:30 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.