#21881: Clarify that `{% ssi ... parsed %}` has the same limitations as `{%
include
%}`
-------------------------------+------------------------------------
Reporter: nagyv | Owner: nobody
Type: Bug | Status: new
Component: Documentation | Version: 1.5
Severity: Normal | Resolution:
Keywords: ssi block | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------+------------------------------------
Changes (by bmispelon):
* component: Template system => Documentation
* easy: 0 => 1
* stage: Unreviewed => Accepted
Comment:
That sentence is not completely clear, I'll admit.
The fact is that `{% ssi %}` has the same limitations as `{% include %}`:
even when you use the `parsed` option, included templates are rendered
separately, so you can't for example alter the context or define blocks.
This is what the note in `{% include %}` tries to convey.
I'm going to mark this ticket as `accepted` (and change its description)
but as I see, it's a documentation issue.
We should make it more clear that the `parsed` option has the same
limitation as `{% include %}`.
What do you think?
--
Ticket URL: <https://code.djangoproject.com/ticket/21881#comment:3>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/063.785e4b1808e911de4b5381ee43430d2f%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
