[MAGNOLIA-1400] Update mechanism : when updating from 3.0.x, remove metadata on expression nodes Created: 23/Feb/07  Updated: 23/Jan/13  Resolved: 22/Oct/07

Status: Closed
Project: Magnolia
Component/s: updatemechanism
Affects Version/s: 3.0.2
Fix Version/s: 3.5 RC1

Type: Task Priority: Major
Reporter: Magnolia International Assignee: Magnolia International
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
depends upon MAGNOLIA-1602 Update mechanism Closed
relation
is related to MAGNOLIA-1448 update: lists configuration updates t... Closed
is related to MAGNOLIA-1320 workflow storage : Expressions don't ... Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty

 Description   

In magnolia 3.0.2, we removed metadata from the "expression" nodetype definition. (MAGNOLIA-1320)
However, if using an existing repository, the metadata are still used, since the actual nodetype definition is used is in repositories/magnolia/repository/nodetypes/custom_nodetypes.xml
Changing the definition there results in warnings.

So there are actually 2 things to do :

  • make it possible to actually update existing nodetype definitions
  • have an update task (i.e with the update mechanism we should introduce in 3.1 - is this on Jira already ?) that will actively remove metadata from existing expression nodes, when updating a workspace created prior to 3.0.2


 Comments   
Comment by Magnolia International [ 22/Oct/07 ]

Done - see MAGNOLIA-1792 for nodetype updates.

Generated at Mon Feb 12 03:26:33 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.