[MGNLSTK-671] Singleton Template Definition (feature pages): Contain relative include of mainArea.ftl which doesn't work if using a custom main.ftl Created: 02/Aug/10 Updated: 23/Jan/13 Resolved: 20/Oct/10 |
|
| Status: | Closed |
| Project: | Magnolia Standard Templating Kit (closed) |
| Component/s: | templates |
| Affects Version/s: | 1.3.4 |
| Fix Version/s: | 1.3.6, 1.4 |
| Type: | Bug | Priority: | Major |
| Reporter: | Christian Ringele | Assignee: | Ondrej Chytil |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||||||
| Issue Links: |
|
||||||||||||||||
| Template: |
|
||||||||||||||||
| Acceptance criteria: |
Empty
|
||||||||||||||||
| Description |
|
Relative includes of sub templates/sub snippets don't work, if you use a main.ftl located in a different location/module. Best would be to check all template definitions (and all ftl's for include of macros) if there are still any relative includes left. All includes, no matter where, should be absolute paths. |