[ 
http://jira.magnolia-cms.com/browse/MGNLMIGRATION-201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Samuel Schmitt updated MGNLMIGRATION-201:
-----------------------------------------

    Component/s: Template Script Migration

> Detected area template script should not be created with the name of the node 
> collection
> ----------------------------------------------------------------------------------------
>
>                 Key: MGNLMIGRATION-201
>                 URL: http://jira.magnolia-cms.com/browse/MGNLMIGRATION-201
>             Project: Magnolia Migration
>          Issue Type: Bug
>          Components: Template Script Migration
>    Affects Versions: 1.2
>            Reporter: Samuel Schmitt
>            Assignee: Robert Šiška
>            Priority: Critical
>             Fix For: 1.2.1
>
>
> When in a FTL we detect something like this 
> {code}
> [@cms.contentNodeIterator contentNodeCollectionName="colLeft"] 
> [@cms.includeTemplate /] [/@cms.contentNodeIterator] [@cms.newBar 
> contentNodeCollectionName="colLeft" 
> paragraph="stkTextImage,updatePageNavigationList,updateDocumentNavigationList"
>  /]
> {code}
> We create a new template script for the detected area which is named with the 
> name of the node collection.
> See in the log:
> {code}
>  Detected area 'colLeft' (save as /update-training/paragraphs/colLeft.ftl) 
> {code}
> I could have another FTL that has a contentNodeIterator where 
> nodeCollectionName is the same but need for its area a specific template 
> script.

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