[MGNLPN-345] Personalized content stored in sub-nodes is not served Created: 08/Nov/16  Updated: 12/Dec/16  Resolved: 24/Nov/16

Status: Closed
Project: Magnolia Personalization
Component/s: None
Affects Version/s: 1.3
Fix Version/s: 1.3.1, 1.4.1

Type: Bug Priority: Neutral
Reporter: Ondrej Chytil Assignee: Roman Kovařík
Resolution: Fixed Votes: 0
Labels: support
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
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 72
Story Points: 3

 Description   

When the component is storing the data in the sub-nodes, for example using DelegatingMultiValueSubnodeTransformer, the component personalization is not providing the proper content.
The content object is serving the proper personalized properties but when accessing the sub-nodes, it always serves the original one instead of the variant.
The test component can be found in the linked SUPPORT-6831.



 Comments   
Comment by Roman Kovařík [ 09/Nov/16 ]
info.magnolia.personalization.decoration.PersonalizationNodeWrapper#getNodes
public NodeIterator getNodes() throws RepositoryException {
        if (VARIANT_NODE_NAME_PATTERN.matcher(variationNode.getName()).matches()) {
            return new PersonalizationNodeIterator(this.getOriginalNode().getNodes(), this.getContentDecorator()); //this should be applied only to pages variants!
        }
        return super.getNodes();
    }
Generated at Mon Feb 12 06:36:42 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.