On Sep 25, 3:26 pm, Steve Potter <[EMAIL PROTECTED]> wrote:
> On Sep 24, 6:16 pm, Graham Dumpleton <[EMAIL PROTECTED]>
> wrote:
>
>
>
> > > Are you sure that the user Apache is running as has permissions
> > > to read directories/files under the missed user's home dir?.
>
> > The permissions issues along with other common issues are described
> > in:
>
> > http://code.google.com/p/modwsgi/wiki/ApplicationIssues
>
> > What you might do if permissions is an issue is use mod_wsgi daemon
> > mode to delegate your Django instance to a separate daemon process
> > that runs as you rather than the default Apache user.
>
> > Graham
>
> Thanks,
>
> That took care of the error I was receiving, as well as a few
> subsequent ones. Now I am stuck with another one.
>
> I am able to load the admin properly, but when I try to access my app
> I get the following error:
>
> ViewDoesNotExist at /imglog/
> Tried index in module projectsmt.imglog.views. Error was: 'module'
> object has no attribute 'models'
>
> But the view does exist and works properly with the development
> server.
>
> After looking through the archives, I thought I was running up against
> a path problem. However I added both the project directory as well as
> its parent directory to the PythonPath.
>
> Still no luck... So then I decided that I still had a permissions
> issue, but I went as far as moving the project into /var/django and
> setting all of the permissions to 777 and I still get the error.
>
> I am at a complete loss, what is the above error referring to when it
> says 'module' object?
>
> I looked through the view.py file for my app, and the only occurrence
> to the word 'models' I could find was in an import statement.
This sort of odd error can sometimes come up if you have chosen names
for directories/modules which clash with standard Python module names.
Where you have in your WSGI script file for mod_wsgi something like:
sys.path.append('/usr/local/django')
sys.path.append('/usr/local/django/mysite')
change it to:
sys.path.insert(0, '/usr/local/django')
sys.path.insert(0, '/usr/local/django/mysite')
This will ensure that your site directories are first in the path
before any of the standard Python modules directory and if you have
used a name which is the same as some standard module, your module
will take precedence.
Other than that, would need to see the full error and traceback and if
related to something in urls.py, show the contents of your rules as
well so can see what target modules/properties are.
Graham
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
