Migrate TemplateScripts Task
(MGNLMIGRATION-112)
|
|
| Status: | Closed |
| Project: | Migration 4.4 to 4.5 (closed) |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 1.2.1 |
| Type: | Sub-task | Priority: | Neutral |
| Reporter: | Robert Šiška | Assignee: | Robert Šiška |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | ToDo_for_1_2_1 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Date of First Response: |
| Description |
|
In the time of running migration tool on custom project, all the Magnolia modules like stk, form or pur can be already migrated. When custom modules use FTLs from these modules, areas should be "detected" without need of parsing the old versions of these FTLs. Also, when extending template definition with area, copy the area definition and add available components. |
| Comments |
| Comment by Eric Hechinger [ 20/Dec/12 ] |
|
@Robert: Could you check the status of this ticket (Open, but commit!) |
| Comment by Jan Haderka [ 24/Jan/13 ] |
General remark:
|
| Comment by Robert Šiška [ 04/Mar/13 ] |
|
@Jan All points have been resolved in the meantime by other tickets... |