[MGNLMIGRATION-211] Transformation of extra area is not correct, custom template scripts previously set on extras must be set to extras1 and extras2 Created: 14/Jan/13 Updated: 29/Mar/13 Resolved: 28/Mar/13 |
|
| Status: | Closed |
| Project: | Migration 4.4 to 4.5 (closed) |
| Component/s: | Migration Task |
| Affects Version/s: | 1.2 |
| Fix Version/s: | 1.2.2 |
| Type: | Bug | Priority: | Major |
| Reporter: | Samuel Schmitt | Assignee: | Robert Šiška |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Template: |
|
| Acceptance criteria: |
Empty
|
| Date of First Response: |
| Description |
|
Many issues identified:
Things has to be reviewed in info.magnolia.migration.task.stk.TransformStkBasedTemplateMigrationTask.transformExtrasToSubAreas(Node) ####### If you set on extra another_extrasArea.ftl, after the migration the extras configuration must be like that:
And in the report you must have a message that tell you to review another_extrasArea.ftl:
|
| Comments |
| Comment by Jan Haderka [ 23/Jan/13 ] |
|
Please update title of the ticket. Think of it as changelog ppl will read when looking at what changes were made and what issues were fixed in this release. Or the problem description one might search for when running into same issue. So probably something mentioning state of enabled property and extras or extras1/2 area definitions should be mentioned in the title. |
| Comment by Natascha Desmarais [ 24/Jan/13 ] |
|
Title and description are missing from the extras area - afaik these are completely new messages keys in the bundle: Not sure if they are supposed to be set in the post-migration but this already does not work for a plain STK migration. |