Thanks, this solved the problem. So, render_to_response does not use context_processors, as it works fine with the default TEMPLATE_CONTEXT_PROCESSORS setting.
On 25 Temmuz, 16:08, "Jeremy Dunck" <[EMAIL PROTECTED]> wrote: > On 7/25/07, omat <[EMAIL PROTECTED]> wrote: > > > > > Thanks for the reply... > > > This is a simple application that highlights source code of a remote > > resource, so I don't need sessions either. > > OK, but you've still not set TEMPLATE_CONTEXT_PROCESSORS. This > setting is used any time RequestContext is used-- and > direct_to_template uses it. > > The default TEMPLATE_CONTEXT_PROCESSORS setting includes the auth > processor. As previously mentioned, you'll need to override the > default to *not* use it. > > This is the default: > TEMPLATE_CONTEXT_PROCESSORS = ( > 'django.core.context_processors.auth', > 'django.core.context_processors.debug', > 'django.core.context_processors.i18n', > 'django.core.context_processors.media', > ) > > If you don't override it in your settings file, that's what you get. > > So, you probably want this in your settings file: > > TEMPLATE_CONTEXT_PROCESSORS = ( > 'django.core.context_processors.debug', > 'django.core.context_processors.i18n', > 'django.core.context_processors.media', > ) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
