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

Changing $type of a trait breaks trait resolution due to the old class being present in the voter stored in JCR

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Neutral
    • 2.1
    • 2.1
    • None
    • None

    Description

      Steps to reproduce

      1.  Define trait in YAML with $type property
      2.  Create a page or component variant
      3.  Choose audience for the variant, pick newly created trait
      4.  Preview content to see that it displays right variant
      5.  Change $type of the trait to something else
      6.  Preview content -> variant didn't match

      Expected results

      Variant is displayed

      Actual results

      Original is displayed

      Workaround

      Modify traitClass property in the VoterSet under the variant

      Checklists

        Acceptance criteria

        Attachments

          Activity

            People

              jsimak Jaroslav Simak
              jsimak Jaroslav Simak
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Checklists

                  Bug DoR
                  Task DoD