[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: PNG File extras.png     PNG File message.png    
Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

Many issues identified:

  • if you define your own ftl for the extra, it's simply overridden by the migration
  • extra 1 is not created for a page template, extra is in fact not well created for a page

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.
Since you also mention that results produced by this change force review of generated changes by developer, this should be documented as well (so there should be related documentation ticket linked to this issue).

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:
title: areas.templates.extras.title
description: areas.templates.extras.description

Not sure if they are supposed to be set in the post-migration but this already does not work for a plain STK migration.

Generated at Mon Feb 12 10:18:12 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.