Browse files

Fixes #2384,#2566 -- Clarify the role that TEMPLATE_STRING_IF_INVALID…

… plays in the template system, and the problems that can occur if it is used on a production site.

git-svn-id: bcc190cf-cafb-0310-a4f2-bffc1f526a37
  • Loading branch information...
1 parent f83e439 commit 73a6eb8ed08da2342baa7f4b4ed9b6743b5fb241 @freakboy3742 freakboy3742 committed Oct 13, 2006
Showing with 15 additions and 0 deletions.
  1. +15 −0 docs/templates_python.txt
15 docs/templates_python.txt
@@ -212,6 +212,21 @@ template tags. If an invalid variable is provided to one of these template
tags, the variable will be interpreted as ``None``. Filters are always
applied to invalid variables within these template tags.
+.. admonition:: For debug purposes only!
+ While ``TEMPLATE_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 non-existent variable is
+ encountered. If you assign a value other than ``''`` to
+ ``TEMPLATE_STRING_IF_INVALID``, you will experience rendering
+ problems with these templates and sites.
+ Generally, ``TEMPLATE_STRING_IF_INVALID`` should only be enabled
+ in order to debug a specific template problem, then cleared
+ once debugging is complete.
Playing with Context objects

0 comments on commit 73a6eb8

Please sign in to comment.