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

Component hidden via personalisation still appears in delivery endpoint response

    XMLWordPrintable

Details

    • Bug
    • Resolution: Duplicate
    • Major
    • None
    • None
    • None
    • None

    Description

      A component hidden via the Personalization module's "Hide/Show original" action still appears in the delivery endpoint's model of a page.

      Steps to reproduce

      1.  Configure an endpoint exposing the website workspace that serves personalised content
      2.  Create a page that contains a personalised component and opt to hide the original

      Expected results

      1. If the endpoint is expected to respect the mgnl:hideOriginal property like the Freemarker renderer does, the component should not appear in the JSON response.

      Actual results

      1. The component appears in the response regardless.

      Workaround

      If the endpoint was configured to expose the necessary properties, a client could deduce that when mgnl:hideOriginal is true and either @variantNodeName is missing, or the node does not have mixin type mgnl:variant then the node should be discounted.

      Checklists

        Acceptance criteria

        Attachments

          Issue Links

            Activity

              People

                Unassigned Unassigned
                chris.jennings Chris Jennings
                DeveloperX
                Votes:
                2 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  Checklists

                    Bug DoR
                    Task DoD