#2474 closed enhancement (wontfix)
{% ssi %} should take variable as argument
Reported by: | Owned by: | nobody | |
---|---|---|---|
Component: | Template system | Version: | dev |
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: | no | UI/UX: | no |
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 by , 18 years ago
Summary: | {% ssi %} is " gedanken" → {% ssi %} should take variable as argument |
---|
comment:2 by , 18 years ago
Type: | defect → enhancement |
---|
comment:3 by , 18 years ago
comment:4 by , 18 years ago
Triage Stage: | Unreviewed → Design 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 by , 17 years ago
Resolution: | → wontfix |
---|---|
Status: | new → closed |
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 by , 16 years ago
@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.
This would have to be a backwards-incompatible change, as we'd start requiring that hard-coded strings would have quotes around them.