mirror of
https://github.com/django/django.git
synced 2025-04-10 08:19:39 +00:00
[4.1.x] Fixed #33317 -- Added note about unconditional evaluation of {% block %} tags.
Backport of 2fac0a18081dcc77fc860c801e5d727dc90435b3 from main
This commit is contained in:
parent
70147215bb
commit
8a2e65c2e6
@ -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 --
|
||||
|
Loading…
x
Reference in New Issue
Block a user