On Fri, 2007-02-16 at 12:27 -0800, cory wrote: > Hello all, > > I keep getting a very strange error in my latest Django project. It > repeatedly sends back a ValueError saying 'Empty module name', but in > the debug output all of the settings from the settings files are > displayed correctly and the settings file that's listed is the correct > one.
You may need to provide a little more information for this: where is the error coming from? Can you work out what sort of "module name" it is expecting? Your problem may be simple to fix, though... > The only thing I can think of is, something isn't right with how > mod_python is accessing the project. There are two locations in my > httpd.conf file for this project: > > <Location "/"> [...] > </Location> > > <Location "/demo/"> [...] > </Location> "Location" directives in Apache are processed in the order they appear in the file. So your first block will catch *all* URLS and the second block will never be applied. In this case, you can probably work around that by just reversing the order of the Location blocks. In other, more complicated cases, you can use LocationMatch (instead of Location) to exclude certain match patterns. Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
