Change History (8)

I don't think that's a bug but rather a limitation of the current system. It's documented as a note for the {% include %} tag [1]:

The include tag should be considered as an implementation of “render this subtemplate and include the HTML”, not as “parse this subtemplate and include its contents as if it were part of the parent”. This means that there is no shared state between included templates – each include is a completely independent rendering process.

Maybe that should be made clearer in the paragraph for {% ssi %} too.
What do you think?

Summary
changed from block tags behavior with {% ssi %} is broken to Clarify that `{% ssi ... parsed %}` has the same limitations as `{% include %}`

Triage Stage
changed from Unreviewed to Accepted

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 %}.