[MGNLPN-80] Newly created variant has activation status inherited from parent but should be "unpublished" Created: 23/Apr/14  Updated: 05/May/14  Resolved: 29/Apr/14

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

Type: Bug Priority: Neutral
Reporter: Jaroslav Simak Assignee: Jaroslav Simak
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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:
Epic Link: Personalisation

 Description   

When creating new variant, we do not update activation status to unpublished. Since all properties are copied to the variant, we also "inherit" activation status of the master page.



 Comments   
Comment by Roman Kovařík [ 29/Apr/14 ]

Commit
https://git.magnolia-cms.com/gitweb/?p=enterprise/p13n.git;a=commitdiff;h=6503190e9e6b628a193badd341f547ca5634e0df

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