[MGNLADVCACHE-107] Wrong cache keys generated for personalized pages with nested component variants Created: 30/Jan/20  Updated: 03/Jun/20  Resolved: 14/Feb/20

Status: Closed
Project: Advanced Cache
Component/s: None
Affects Version/s: 2.0.1
Fix Version/s: 2.1, 2.2.1

Type: Bug Priority: Neutral
Reporter: Mercedes Iruela Assignee: Roman Kovařík
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 0d
Time Spent: 6h 20m
Original Estimate: Not Specified

Issue Links:
Problem/Incident
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
Release notes required:
Yes
Date of First Response:
Epic Link: Support
Sprint: UI Framework 16, UI Framework 17
Story Points: 1

 Description   

Steps to reproduce:

  1. Create original page
  2. Create variant page with date trait, so page variant is always visible (e.g have date range for current month)
  3. Create component inside variant page.
  4. Create variant of that component (now you need to use cookie trait to be able to switch display for the component) - e.g set default provided cookie : weatherLocality : Basel
  5. Time to reproduce the problem: 
    a) no cookie exists --> variant page is displayed (due to date trait) together with original component of that variant page.
    b) add cookie : weatherLocality: Basel --> variant page is again displayed (due to date trait) and original component of variant page is displayed. Of course from logs it is easy to figure out why this is happening (cache is serving based only on page uuid - there is NO component uuid used on key generation)


 Comments   
Comment by Federico Grilli [ 14/Feb/20 ]

@Docuteam: for Magnolia 5.7.x advanced-cache module version has been raised to 2.1 and will be part of Magnolia EE as of version 5.7.7. Reason was the need to bump personalization dependency from 1.5.4 to 1.6.3 in order to fix this issue.

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