From f2de56223540c1e728c82baf206ffa6e6f285eab Mon Sep 17 00:00:00 2001 From: Tim Graham Date: Thu, 30 Oct 2014 18:42:54 -0400 Subject: [PATCH] [1.7.x] Fixed #23736 -- Corrected the description of the value that silent_variable_failure uses. Thanks Aymeric Augustin for the report. Backport of e7cb4f2fba from master --- docs/ref/templates/api.txt | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/ref/templates/api.txt b/docs/ref/templates/api.txt index 294e3a6b67..9e5964c9ff 100644 --- a/docs/ref/templates/api.txt +++ b/docs/ref/templates/api.txt @@ -170,7 +170,9 @@ straight lookups. Here are some things to keep in mind: propagated, unless the exception has an attribute ``silent_variable_failure`` whose value is ``True``. If the exception *does* have a ``silent_variable_failure`` attribute whose value is - ``True``, the variable will render as an empty string. Example:: + ``True``, the variable will render as the value of the + :setting:`TEMPLATE_STRING_IF_INVALID` setting (an empty string, by default). + Example:: >>> t = Template("My name is {{ person.first_name }}.") >>> class PersonClass3: @@ -198,7 +200,7 @@ straight lookups. Here are some things to keep in mind: silently. * A variable can only be called if it has no required arguments. Otherwise, - the system will return an empty string. + the system will return the value of :setting:`TEMPLATE_STRING_IF_INVALID`. .. _alters-data-description: