[MGNLMIGRATION-92] Subtemplates are not migrated for all templates Created: 05/Oct/12 Updated: 22/Apr/13 Resolved: 12/Oct/12 |
|
| Status: | Closed |
| Project: | Migration 4.4 to 4.5 (closed) |
| Component/s: | None |
| Affects Version/s: | 1.1.3 |
| Fix Version/s: | 1.1.4 |
| Type: | Bug | Priority: | Neutral |
| Reporter: | wolf bubenik | Assignee: | Cesar Desales |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Mgnl core 4.5.4-patched-magnolia-4533 |
||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Date of First Response: | |||||||||
| Comments |
| Comment by Lars Fischer [ 09/Oct/12 ] |
|
This seems to be a problem with the content of the specific sub-template file. If the content of the Freemarker template script is changed, the file gets migrated (even the previously untouched content). |
| Comment by Lars Fischer [ 10/Oct/12 ] |
|
Asked for more examples because I cannot reproduce the problem at the moment. Maybe it was the file encoding, ... |
| Comment by Lars Fischer [ 12/Oct/12 ] |
|
Issue was tested again by two developers in different environments. The corresponding sub-template were always migrated. We did not get any of the requested test results from the partner so it seems to be working. If it would be the case that the file is still not migrated in the partner's environment, we offer to send a migrated version of the sub-template. |