[MGNLPN-595] Compatibility trait detectors are not correctly ordered in /server/filters on clean install Created: 14/Oct/21  Updated: 18/Oct/22  Resolved: 11/Mar/22

Status: Closed
Project: Magnolia Personalization
Component/s: None
Affects Version/s: 2.1
Fix Version/s: 2.1.1

Type: Bug Priority: Neutral
Reporter: Jaroslav Simak Assignee: Yen Lac Tue
Resolution: Fixed Votes: 0
Labels: VN-Implementation, VN-Testing
Remaining Estimate: Not Specified
Time Spent: 4d 2.25h
Original Estimate: Not Specified

Attachments: PNG File screenshot-1.png    
Template:
Acceptance criteria:
Empty
Task DoD:
[X]* Doc/release notes changes? Comment present?
[X]* Downstream builds green?
[X]* Solution information and context easily available?
[X]* Tests
[X]* 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: AuthorX Maintenance
Sprint: AuthorX 4, AuthorX 5
Story Points: 3

 Description   

Problem

  1. Traits provided by the personalization-compatibility (date, cookies, country, visitor) module are not working due to the trait detectors being ordered as last in the filter chain.

Steps to reproduce

  1. Do a clean install of DX Core with personalization 2.1.0

Expected results

  1. Compatibility trait detectors are correctly ordered correctly in /server/filters

Actual results

  1. Compatibility trait detectors are at the bottom in /server/filters

Workaround

  1. Order filters manually


 Comments   
Comment by Christopher Zimmermann [ 21/Feb/22 ]

Can you add to the description what impact this has on users or develoers? How is the p13n functionality affected?

Generated at Mon Feb 12 06:39:11 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.