I have yet to take the time to understand why this problem only comes some of the time, but anyways, most of the time a hard refresh of a site takes care of clearing the browser cache of a page. Every once in a while the actual DNS entry to a sites is pointing at the wrong place. In those situations (on a OS X Leopard) do the following:
SetEnv DJANGO_SETTINGS_MODULE <project>.settings
PythonPath "['/parent', '/parent/project'] + sys.path"
I found the instructions a bit confusing on the site. So I hope this clears up things a bit. My thought is they think the setup for live systems and where those files reside is different in the minds of the developers although that pathway isn’t really brought to light in the docs. It’s kind of hinted at, but here it goes.
In order to get my project up on Apache I had to include both the path for my project as well as its parent. The reason being is that it needs to be able to tie into your settings.py file and wants to know the project that’s a part of. In order to get that relationship it needs the folder of the project itself. I also added the path for the project so that it could tie into the applications.
What this means.
Replace <project>: with the name of your project
Replace /parent:Â with the directory of the parent directory to your project
Replace /parent/project: with the directory of your project
Save the file and then restart apache: