[MGNLPN-329] Page editor actions don't take variants of parent elements into account Created: 06/Sep/16  Updated: 12/Sep/16  Resolved: 07/Sep/16

Status: Closed
Project: Magnolia Personalization
Component/s: Component p13n
Affects Version/s: 1.3
Fix Version/s: 1.3

Type: Bug Priority: Critical
Reporter: Christopher Zimmermann Assignee: Roman Kovařík
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: XML File website.comp-p13n-area-problem.xml    
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 60
Story Points: 2

 Description   

When using component personalization on a component which contains an area, (such as the column-layout component in the travel demo) , when you add a new component to the area in any of the variants - the new component is added to the original, instead of to the currently active variant.

To reproduce:

  • Create a new page with template "Travel Standard"
  • Add a Column Layout component to the page (with 2 cols for simplicity)
  • Add an HTML component to the 1st column. Enter "In original" as the HTML content.
  • On the Column Layout component, Add a component variant.
  • On the new "Variant 0" variant, create an addition HTML component in the 1st column, with content "In variant-0".
    Result:
  • You don't see the new content in variant-0.
  • When you switch to the original - you see the content there.
  • In the JCR-browser, you see the content has indeed been placed in the original, not in the variant.

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