id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
1338	Undefined context variables should not resolve to the value of TEMPLATE_STRING_IF_INVALID	django@…	Russell Keith-Magee	"The new TEMPLATE_STRING_IF_INVALID is a useful setting but it seems to have some problems currently.  With the current implementation undefined context variables are actually resolved to the value of TEMPLATE_STRING_IF_INVALID.  This means that {% if
some_undefined_variable %} can evaluate true.  Also {{{FilterExpression}}} is passing the
TEMPLATE_STRING_IF_INVALID value through the filters, which is probably not going to fit with user expectations.

Perhaps {{{resolve_variable}}} should be consistently raising an exception
for all unresolvable variables and {{{Node}}} renderers and {{{FilterExpression}}} should be returning TEMPLATE_STRING_IF_INVALID directly where appropriate.  This would be slightly backwards
incompatible for people using the guts of the template renderer in their template tags."	task	closed	Generic views	dev	trivial	fixed			Unreviewed	0	0	0	0	0	0