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
13338	adding custom template context processor(s) to settings.py screws up admin	marshall.ent@…	nobody	"I added my own template context processor:

{{{
TEMPLATE_CONTEXT_PROCESSORS = (
    'www.context_processor.static_url',
)
}}}

and the admin system stopped receiving its context and I got TemplateSyntaxErrors. It worked again when I added:


{{{
TEMPLATE_CONTEXT_PROCESSORS = (
    'www.context_processor.static_url',
    'django.core.context_processors.auth',
)
}}}

is there a reason I have to manually add the context processor for auth after creating a custom processor? A user in #django told me to add the following: 


{{{
from django.conf.global_settings import TEMPLATE_CONTEXT_PROCESSORS
}}}

to the top of my settings.py, I did that and added my template context processor using: 


{{{
TEMPLATE_CONTEXT_PROCESSORS += (
    'www.context_processor.static_url',
)
}}}

which seems to have worked. What's going on? Is this the way it's supposed to be or have I done something I'm not supposed to?"		closed	Template system	1.1		invalid	template context processor		Unreviewed	0	0	0	0