[MGNLMIGRATION-201] Detected area template script should not be created with the name of the node collection Created: 08/Jan/13 Updated: 28/Mar/13 Resolved: 22/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 |
|
When in a FTL we detect something like this [@cms.contentNodeIterator contentNodeCollectionName="colLeft"] [@cms.includeTemplate /] [/@cms.contentNodeIterator] [@cms.newBar contentNodeCollectionName="colLeft" paragraph="stkTextImage,updatePageNavigationList,updateDocumentNavigationList" /] We create a new template script for the detected area which is named with the name of the node collection. Detected area 'colLeft' (save as /update-training/paragraphs/colLeft.ftl)
I could have another FTL that has a contentNodeIterator where nodeCollectionName is the same but need for its area a specific template script. |
| Comments |
| Comment by Cesar Desales [ 16/Jan/13 ] |
|
What would be a good name for the file? The collection name plus a random token? |
| Comment by Samuel Schmitt [ 17/Jan/13 ] |
|
Random doesn't mean unique. Maybe better is to create a folder with the name of "The FTL where you detected an area" and in this folder you add the template script of the area. ex: +paragraphs The script detect in test.ftl an area and want to create a script for it, the we do the following, we create a folder named "test" in paragraph: |
| Comment by Jan Haderka [ 18/Mar/13 ] |
|
junit tests? |