[MGNLMIGRATION-202] FTL migration doesnt detect basic STK pattern Created: 08/Jan/13  Updated: 28/Mar/13  Resolved: 18/Mar/13

Status: Closed
Project: Migration 4.4 to 4.5 (closed)
Component/s: Template Script Migration
Affects Version/s: 1.2
Fix Version/s: 1.2.2-beta1, 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

Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

After the FTL update I still have code not correctly updated

  <div id="wrapper">

        [#if  def.header.enabled]
            [#include  def.header.template]
        [/#if]

        <div id="wrapper-2">
            <div id="wrapper-3">
                [#if  def.platformArea.enabled]
                    [#include  def.platformArea.template]
                [/#if]

                <div id="main">
                    [#if  def.breadcrumb.enabled]
                        [#include  def.breadcrumb.template]
                    [/#if]

                    [#--OLD [#include  def.mainArea.template] --][@cms.area name = "main" content=content /]

Header, platform, breadcrumd are standard STK pattern. We must do something.



 Comments   
Comment by Robert Šiška [ 15/Mar/13 ]
  • def.header.template -> three areas: branding, stage & sectionHeader
  • def.platformArea.template -> area 'platform'
  • def.breadcrumb.template -> breadcrumb is now part of 'main' area.
Comment by Jan Haderka [ 18/Mar/13 ]

junit tests?

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