[MGNLPN-406] Personalized pages are not activated correctly Created: 03/Nov/17  Updated: 06/Feb/18  Resolved: 06/Feb/18

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

Type: Bug Priority: Neutral
Reporter: Viet Nguyen Assignee: Jaroslav Simak
Resolution: Not an issue Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
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 133
Story Points: 2

 Description   

Please reference to SUPPORT-8076 for more detail. In a nutshell:
Use 'publish' page action in our page app, the variants get published. If we use 'publish incl. subpages / subnodes' then it doesn't work. Tested on demo instances.



 Comments   
Comment by Jaroslav Simak [ 06/Feb/18 ]

I tried to reproduce problem described in the support ticket (component variants are not published). I migrated from 5.4.13 to 5.4.14 with component personalization and tried activation, components are published successfully on public instance, clean install of 5.4.14 works fine as well.

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