Sorry, I should have mentioned that this has only come up after deploying the project to a production server using mod_wsgi. It works absolutely fine under development.
Tom On Nov 25, 2:24 am, Tim Valenta <[email protected]> wrote: > Are you using the development server? There's definitely caching > funny-business in a production web server, but that should affect you > if you're using "manage.py runserver" > > Does stopping and starting the development server change anything? > > Tim > > On Nov 24, 6:54 pm, Tom <[email protected]> wrote: > > > > > Hi all, > > > I am experiencing TemplateDoesNotExist errors. Initially I thought I > > had my TEMPLATE_DIRS variable set incorrectly, but much > > experimentation yielded nothing. I then noticed that on the browser > > TemplateDoesNotExist error pages the TEMPLATE_DIRS setting reads as an > > empty tuple (). I then tried changing several other settings in > > settings.py including database name and engine, and adding and > > removing installed apps. None of these changes are showing up in the > > settings listed on error pages. > > > It seems like the settings file has been cached somewhere because > > nothing I do to my settings.py file is making any difference. I have > > even tried deleting the file altogether and still nothing changes. I > > have also tried recreating my project from scratch, but still no joy. > > > This is really weird; does anybody have any ideas what is going on? > > > Thanks in advance, > > > Tom -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected]. 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.
