Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Fixed #33317 -- Added note about unconditional evaluation of {% block %} tags. #15865

Merged
merged 3 commits into from
Jul 22, 2022
Merged

Fixed #33317 -- Added note about unconditional evaluation of {% block %} tags. #15865

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
b1f6aa1
Fixed #33317 -- Add note about not overriding parent blocks within co…
ViggieM Jul 21, 2022
3320c15
Update docs/ref/templates/language.txt
ViggieM Jul 22, 2022
3216e7d
add wording suggestion
ViggieM Jul 22, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
9 changes: 9 additions & 0 deletions docs/ref/templates/language.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -431,6 +431,15 @@ Here are some tips for working with inheritance:
In larger templates, this technique helps you see which ``{% block %}``
tags are being closed.

* :ttag:`{% block %}<block>` tags are evaluated first. That's why the content
of a block is always overridden, regardless of the truthiness of surrounding
tags. For example, this template will *always* override the content of the
``title`` block::

{% if change_title %}
{% block title %}Hello!{% endblock title %}
{% endif %}

Finally, note that you can't define multiple :ttag:`block` tags with the same
name in the same template. This limitation exists because a block tag works in
"both" directions. That is, a block tag doesn't just provide a hole to fill --
Expand Down