Re: Why does direct_to_template require a db?

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

Re: Why does direct_to_template require a db?

To clarify, in urlpatterns: (r'^$', 'django.views.generic.simple.direct_to_template', {'template': 'index.html'}) causes the mentioned problem, but (r'^$', 'highlighter.views.index'), works fine, where "highlighter.views.index" is def index(request): return

Re: Why does direct_to_template require a db?

Thanks for the reply... This is a simple application that highlights source code of a remote resource, so I don't need sessions either. After removing the sessions too, I end-up with a minimal settings file: http://dpaste.com/15278/ Now, django raises an AttributeError and complains that:

Re: Why does direct_to_template require a db?

On 7/24/07, omat <[EMAIL PROTECTED]> wrote: > Why does direct_to_template require a database at all? > It doesn't directly require it. You must be using something that does. Are you using sessions? It does use RequestContext, which runs TEMPLATE_CONTEXT_PROCESSORS, which includes