Re: Template lookup order not behaving as expected

On Apr 28, 6:41 pm, creecode wrote: > You could add a "pages" directory to your templates directory. > Something like... > > ./pages > ./pages/templates > ./pages/templates/pages > > And then you would do... > > return render_to_response( 'pages/index.html'... Thanks! It looks like that is also h

Re: Template lookup order not behaving as expected

Hello Thomas, On Apr 28, 2:33 pm, Thomas Allen wrote: > I have noticed that the first app in my INSTALLED_APPS tuple overrides > all of the others for an ambiguous template name. "accounts" does not > have one, but "dashboard" does, which is why I am seeing what I am > seeing (if I place "ads" ab

Re: Template lookup order not behaving as expected

I have noticed that the first app in my INSTALLED_APPS tuple overrides all of the others for an ambiguous template name. "accounts" does not have one, but "dashboard" does, which is why I am seeing what I am seeing (if I place "ads" above "dashboard", the "ads" template precedes all others). I thou

Template lookup order not behaving as expected

Hi everyone, In my "pages" app, I have the following view function which renders index.html: @login_required def index(req): return render_to_response( 'index.html', context_instance=RequestContext(req) ) What really has me stuck here is that it doesn't render pages/ template