Issue Type: Bug Bug
Affects Versions: 1.2.3
Assignee: Unassigned
Components: Migration Task
Created: 22/Jul/13 4:04 PM
Description:

Before Magnolia 4.5 a node representing an available component (paragraph in prototype for instance) will often have the same name as the value the node's name property (node data). When this is not the case (which is valid AFAIK) TransformStkBasedTemplateMigrationTask#updateAvailableComponent(node) will look for the wrong component name.

I believe the fix is to have this method use node.getProperty("name") (which is used when removing the old value!) instead of node.getName().

Project: Magnolia Migration
Priority: Neutral Neutral
Reporter: Nils Breunese
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira



----------------------------------------------------------------
For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: <dev-list-unsubscr...@magnolia-cms.com>
----------------------------------------------------------------

Reply via email to