Uploaded image for project: 'Magnolia Personalization'
  1. Magnolia Personalization
  2. MGNLPN-329

Page editor actions don't take variants of parent elements into account

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Critical Critical
    • 1.3
    • 1.3
    • Component p13n
    • None
    • Kromeriz 60
    • 2

      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.

        Acceptance criteria

              rkovarik Roman Kovařík
              czimmermann Christopher Zimmermann
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved:

                  Bug DoR
                  Task DoD