Opened 10 years ago

Closed 9 years ago

Last modified 8 years ago

#2474 closed enhancement (wontfix)

{% ssi %} should take variable as argument

Reported by: msw@… Owned by: nobody
Component: Template system Version: master
Severity: normal Keywords: SSI, ssi
Cc: Triage Stage: Design decision needed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:

Description

In documentation thereis only one method to use SSI in templates:
{% ssi /home/html/ljworld.com/includes/right_generic.html %}
I have necessity to use it in this format
{% ssi variable %}
but i bug in this... - nothing happened...
even use {% ssi {{ variable }} %} has same results...
so only directly path is be fit :(
I think you can do more generalise, like {% include template_name %}
Am i right? ;-)

Change History (6)

comment:1 Changed 10 years ago by Malcolm Tredinnick

Summary: {% ssi %} is " gedanken"{% ssi %} should take variable as argument

comment:2 Changed 10 years ago by anonymous

Type: defectenhancement

comment:3 Changed 10 years ago by Adrian Holovaty

This would have to be a backwards-incompatible change, as we'd start requiring that hard-coded strings would have quotes around them.

comment:4 Changed 10 years ago by Simon G. <dev@…>

Triage Stage: UnreviewedDesign decision needed

To avoid the backwards incompt. issue, would it be possible to check if the string is a variable first, before taking it as a string? (e.g. like the other template variables fall through objects/dictionaries/lists/etc)

comment:5 Changed 9 years ago by Jacob

Resolution: wontfix
Status: newclosed

I think the plan is to make ssi go the way of the dodo, so I'm going to mark this wontfix (you can always use include to the same effect).

comment:6 Changed 8 years ago by Thomas Capricelli

@jacob : with include it is only possible to include files that lie in "templates/" directories. It is not always possible to use it to get the same effect.

Note: See TracTickets for help on using tickets.
Back to Top