Hello, On Wed, Oct 22, 2008 at 5:15 PM, Karen Tracey <[EMAIL PROTECTED]> wrote: > Other than the actual server code, are there any differences in config between > when you see this error and when you do not? For example, DEBUG setting, > caching, etc.?
The only difference is the FORCE_SCRIPT_NAME setting: that's needed on my preferred setup (lighttpd+fcgi). The test I made with apache+mod_python was meant to tell me whether the bug has something to do with that setting or not. So I tried mod_python, commenting out FORCE_SCRIPT_NAME and using the django.root PythonOption in apache's configuration. That results in the same odd behavior. Your email made me think of trying to install the site on the root of the webserver, and try apache+mod_python without FORCE_SCRIPT_NAME _and_ without the django.root option. Unfortunately, I still get the bug (although it's seems a bit less frequent now, but it's not a scientific measure). > Also, can you recreate the problem on the most recent trunk or 1.0.X branch > code? Your line numbers from the traceback don't match up with current so > I'm guessing you are using 1.0? I just tried with trunk, and the problem persists. Alberto --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
