[MGNLMIGRATION-217] Footer content is not correctly migrated, the footer is transformed into a component but it should be an area Created: 24/Jan/13 Updated: 26/Jun/15 Resolved: 24/Jan/13 |
|
| Status: | Closed |
| Project: | Migration 4.4 to 4.5 (closed) |
| Component/s: | Migration Task |
| Affects Version/s: | None |
| Fix Version/s: | 1.2.1 |
| Type: | Bug | Priority: | Critical |
| Reporter: | Samuel Schmitt | Assignee: | Samuel Schmitt |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Date of First Response: | |||||||||
| Description |
|
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: 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.
TodoUpdate UpdateWebsiteMainContentMigrationTask and add a special treatment for the footer. The doc must also mention that, please update the page http://wiki.magnolia-cms.com/pages/viewpage.action?pageId=56363441#MigrationprocessVersionupto12-4TransformSTK-basedwebsites |
| Comments |
| Comment by Jan Haderka [ 24/Jan/13 ] |
|