[MGNLPN-782] Component hidden via personalisation still appears in delivery endpoint response Created: 20/May/22  Updated: 08/Feb/24  Resolved: 08/Feb/24

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

Type: Bug Priority: Major
Reporter: Chris Jennings Assignee: Unassigned
Resolution: Duplicate Votes: 2
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
duplicate
duplicates MGNLPN-781 Hidden original variants are shown as... In Progress
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
Epic Link: Headless p13n Backlog
Team: DeveloperX

 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.


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