summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorVlastimil Zíma <vlastimil.zima@nic.cz>2017-08-25 11:47:59 +0200
committerTim Graham <timograham@gmail.com>2018-08-06 17:03:06 -0400
commita9f5652113f0721a7066e359ae28d14692ea3c47 (patch)
tree74cf27a6a93f3114d7360b2126a487e2256febbb /docs
parent93bd860710d9914cc077ee362d5f3647489ce5a5 (diff)
Fixed #28529 -- Fixed VariableDoesNotExist warnings in admin templates.
Diffstat (limited to 'docs')
-rw-r--r--docs/ref/templates/api.txt6
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/ref/templates/api.txt b/docs/ref/templates/api.txt
index c1a1754b29..f37c0a65c2 100644
--- a/docs/ref/templates/api.txt
+++ b/docs/ref/templates/api.txt
@@ -371,9 +371,9 @@ replaced with the name of the invalid variable.
While ``string_if_invalid`` can be a useful debugging tool, it is a bad
idea to turn it on as a 'development default'.
- Many templates, including those in the Admin site, rely upon the silence
- of the template system when a nonexistent variable is encountered. If you
- assign a value other than ``''`` to ``string_if_invalid``, you will
+ Many templates, including some of the Django's templates, rely upon the
+ silence of the template system when a nonexistent variable is encountered.
+ If you assign a value other than ``''`` to ``string_if_invalid``, you will
experience rendering problems with these templates and sites.
Generally, ``string_if_invalid`` should only be enabled in order to debug