On Tuesday, May 3, 2011 6:38:40 PM UTC+1, Jeff Blaine wrote: > > I've read the following and am still stuck and wondering what piece of this > puzzle > I am missing. If anyone has any ideas, please do comment! > > http://docs.djangoproject.com/en/1.3/howto/deployment/modwsgi/ > > http://code.google.com/p/modwsgi/wiki/IntegrationWithDjango > > Using the Django 1.3 development webserver, everything works fine. > Migrating to > Apache 2.x with WSGI 3.3, not so much. The WSGI part of the picture seems > to > function as intended, but not with my Django stuff. > > Visiting / gives me the *expected* 404 (see urls.py below) > > Visiting /admin (which is really the entirety of my needs) gives me: "Site > matching query does not exist." > > <snip> > Exception Type: DoesNotExist at /admin/ Exception Value: Site matching > query does not exist. > > I don't know why you think this is a WSGI error. As you say, Apache is finding your WSGI app with no problem, and the error you get is a Django one - you simply don't seem to have any data in your Site table, whereas the Django admin requires one. -- DR.
-- 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 django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
