[MAGNOLIA-5432] Do not remove mix:lockable while versioning nodes Created: 31/Oct/13  Updated: 15/Mar/21  Resolved: 15/Mar/21

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

Type: Bug Priority: Neutral
Reporter: Jan Haderka Assignee: Unassigned
Resolution: Outdated Votes: 0
Labels: next
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MAGNOLIA-5423 Primary node type is not updated duri... Closed
is related to MAGNOLIA-5362 Introduce mechanism for performing wr... Closed
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

 Description   

Since introduction of locking in MAGNOLIA-5362 we add mix:lockable to all page nodes. This mixin is however still removed by CopyUtil.updateNodeTypes() method when versioning/restoring the node. Mixin should be honoured.



 Comments   
Comment by Jan Haderka [ 15/Mar/21 ]

Why should it be honoured? Reopen when more info available.

Generated at Mon Feb 12 04:05:07 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.