[MGNLDEMO-266] Broken diff in demo with personalized component Created: 24/Jan/18  Updated: 09/Feb/18  Resolved: 08/Feb/18

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

Type: Bug Priority: Neutral
Reporter: Federico Grilli Assignee: Federico Grilli
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
caused by MGNLDIFF-100 Compare current with previous version... 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: Basel 132, Basel 133
Story Points: 2

 Description   

Steps to reproduce the problem:

  1. go to Pages
  2. publish travel
  3. edit the page
  4. add a component to the main area
  5. go back to Pages
  6. click 'Compare to previous version'
  7. the diff is completely broken

Steps to fix the problem:

The broken diff view can be resolved by changing how component variants are composed on travel home. Delete the Featured Tours by Tour Type component and make it a variant of Tour Type Teaser Row:

  1. Delete component 01 in the main area.
  2. In component 00, change variant-1's template to Featured Tours (by TourType) and set variant audience to Cookie: Tour type = any value. NoSuchDefinitionException error is thrown when you try to change the variant's template to Featured Tours (by TourType). This needs to be fixed.
  3. Verify that the page layout still works.

Caveat: The proposed solution fixes the problem on travel demo home page. It does not prevent a customer from potentially composing the same problematic component scenario on their own site.


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