Migration task that creates an Area definition is missing when in the FTL the 
pattern paragraph="${def.subParagraphs}" is found
-------------------------------------------------------------------------------------------------------------------------------

                 Key: MGNLMIGRATION-200
                 URL: http://jira.magnolia-cms.com/browse/MGNLMIGRATION-200
             Project: Magnolia Migration
          Issue Type: Bug
    Affects Versions: 1.2
            Reporter: Samuel Schmitt
            Assignee: Robert Šiška
            Priority: Major
             Fix For: 1.2.1
         Attachments: threeColumns.ftl, threeColumns_before.ftl

Look at the two FTLs attached. One is before the FTL migration and one after.

In the FTL threeColumns.ftl, the area tags are correctly created. I expect that 
in the report there is something about that and about the code to add is the 
version.. but nothing.

This is the log of the report

{code}
updateThreeColumns
Log records:

    [INFO] [updateThreeColumns] Migrating component updateThreeColumns 
(/update-training/paragraphs/threeColumns.ftl)
    [INFO] [updateThreeColumns] OK 
{code}


OK is really meaningful !!

Here I expect something that tell me that 3 areas were detected and that the 
template definitions referencing /update-training/paragraphs/threeColumns.ftl 
must be updated. If we cannot provide the code that will update these 
definitions, at least we could mention that something must be done.




-- 
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]>
----------------------------------------------------------------

Reply via email to