[MGNLCAT-21] CLONE -Singleton Template Definitiona (feature pages): Contain relative include of mainArea.ftl which doesn't work if using a custom main.ftl Created: 06/Oct/10  Updated: 29/Nov/10  Resolved: 06/Oct/10

Status: Closed
Project: Magnolia Categorization Module
Component/s: None
Affects Version/s: None
Fix Version/s: 1.1.5

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

Issue Links:
Cloners
clones MGNLSTK-671 Singleton Template Definition (featur... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 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.



 Comments   
Comment by Tobias Mattsson [ 29/Nov/10 ]

Clone.

Generated at Mon Feb 12 04:42:20 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.