Footer content is not correctly migrated, the footer is transformed as an
component but it should be an area
------------------------------------------------------------------------------------------------------------
Key: MGNLMIGRATION-217
URL: http://jira.magnolia-cms.com/browse/MGNLMIGRATION-217
Project: Magnolia Migration
Issue Type: Bug
Components: Migration Task
Reporter: Samuel Schmitt
Assignee: Samuel Schmitt
Priority: Critical
Fix For: 1.2.1
Attachments: footer-config-4.4.png
The task that transform the primary type
({{info.magnolia.migration.task.content.UpdateWebsitePrimaryTypeMigrationTask}})
change the primary type of a STK footer area into {{mgnl:component}} instead
of {{mgnl:area}}.
Why? Because the logic that return the new type is doing the following:
If the "old type" is Content, then the "new type" is page.
If the "old type" is ContentNode, then the new type is Area only if the node
has no template assigned to it,otherwise it's a component.
Check here
{{info.magnolia.migration.task.content.UpdateWebsitePrimaryTypeMigrationTask.getNewType(Node)}}.
Footer is a special case, it an area for the 4.4 world of Magnolia but is has a
template. Now in 4.5 it is still an area but its transformation must be handled
differently by the migration.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
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: <[email protected]>
----------------------------------------------------------------
