[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: PNG File Screen shot 2010-08-02 at 12.18.48 PM.png    
Issue Links:
Cloners
is cloned by MGNLCAT-21 CLONE -Singleton Template Definitiona... Closed
relation
is related to MGNLSTK-750 All relative includes of ftl's should... Closed
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.
The relative include is the executed on the new location (relative to the new main.ftl).
We had the same problem with all Section templates and removed the relative pathes from the Section templates.
The the singleton paragraph templates still contain these relative includes, see print screen.

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.


Generated at Mon Feb 12 07:29:18 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.