#13338: adding custom template context processor(s) to settings.py screws up
admin
----------------------------------------+-----------------------------------
Reporter: marshall....@gmail.com | Owner: nobody
Status: new | Milestone:
Component: Template system | Version: 1.1
Keywords: template context processor | Stage: Unreviewed
Has_patch: 0 |
----------------------------------------+-----------------------------------
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?
--
Ticket URL: <http://code.djangoproject.com/ticket/13338>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
