[MGNLDEMO-211] Tour type cookie component caches same entry for all variants Created: 23/Mar/17  Updated: 20/Jul/18  Resolved: 17/Jul/18

Status: Closed
Project: Magnolia Demo Projects
Component/s: None
Affects Version/s: 1.1.2
Fix Version/s: 1.3.1

Type: Bug Priority: Neutral
Reporter: Roman Kovařík Assignee: Antonín Juran
Resolution: Fixed Votes: 0
Labels: estimate-with-uncertainty
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MGNLPN-426 Pages with component variants breaki... 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:
Sprint: Kromeriz 156
Story Points: 2

 Description   

The tour variant is resolved in the FTL thus caching doesn't have a clue about it.
We should either have all variants as different components in JCR or disable caching for whole page.

To reproduce:

  1. On EE (with advanced cache for personalisation installed)
  2. Visit the home page on public instance as first visitor, choose tour type.
  3. Clear your cookies or use another browser to mimic another visitor.
  4. Choose the other type of the tour type.
  5. You get the tour type of the first visitor (cached home page created by the first visitor).


 Comments   
Comment by Antti Hietala [ 25/Jun/18 ]

rkovarik What are the acceptance criteria? What would the variant resolving on the home page look like once this ticket is done?

Comment by Roman Kovařík [ 26/Jun/18 ]

ahietala Updated the description so the acceptance criteria are clear.

Generated at Mon Feb 12 05:17:25 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.