[ http://jira.magnolia.info/browse/MAGNOLIA-1400?page=all ]
Grégory Joseph reassigned MAGNOLIA-1400:
----------------------------------------
Assignee: Grégory Joseph (was: Sameer Charles)
> Update mechanism : when updating from 3.0.x, remove metadata on expression
> nodes
> --------------------------------------------------------------------------------
>
> Key: MAGNOLIA-1400
> URL: http://jira.magnolia.info/browse/MAGNOLIA-1400
> Project: Magnolia
> Issue Type: Task
> Components: core, workflow
> Affects Versions: 3.0.2
> Reporter: Grégory Joseph
> Assigned To: Grégory Joseph
> Fix For: 3.1
>
>
> 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
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia.info/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------
