[MGNLSTK-750] All relative includes of ftl's should be removed Created: 04/Mar/11  Updated: 04/Nov/15  Resolved: 04/Nov/15

Status: Closed
Project: Magnolia Standard Templating Kit (closed)
Component/s: paragraphs, templates
Affects Version/s: 1.3.5, 1.4.2
Fix Version/s: 1.4.x

Type: Bug Priority: Major
Reporter: Christian Ringele Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MGNLSTK-487 Template configs contain relative pat... Closed
is related to MGNLSTK-671 Singleton Template Definition (featur... Closed
is related to MGNLSTK-537 Change relative include paths to abso... Closed
Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

There are many related issues about the same topic (linked to them).
But I still have seen such relative includes in ftl's themselves:
for example in the section/mainArea.ftl ->

[#include "opener.ftl" ]

It is really important, that all get finally removed form all ftl's.
Its really annoying in projects, when you can't reuse templates just cause of relative includes.

A manuel search through all ftl's with

[#include "

and checking one by one if still relative is the only way to find all.



 Comments   
Comment by Christian Ringele [ 28/Mar/11 ]

I set prio top Major again:
If you have a relative include in STK, no way to use the template by itself. You have to copy all others too.
That is quite slowing down project implementations -> Major prio, for that the main scope of STK is creating projects.

Comment by Michael Mühlebach [ 04/Nov/15 ]

Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes.
Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
I'm going to close this to set expectations so the issue doesn't stay open for years with few updates. If the issue is still relevant please feel free to reopen it or create a new issue.

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