On Apr 29, 7:55 pm, Graham Dumpleton <[EMAIL PROTECTED]>
wrote:
> On Apr 30, 3:26 am, Rajesh Dhawan <[EMAIL PROTECTED]> wrote:
>
>
>
>
>
> > Hi,
>
> > > I could use some help getting my Django website back up after an
> > > upgrade to Hardy Heron. Instead of using svn to get Django, I used
> > > synaptic this time. Now my site doesn't work and I'm a bit confused
> > > on path names.
>
> > > I believe Hardy installed Django to /var/lib/python-support/python2.5/
> > > django
> > > My website is at /home/published/www/django/catalog
>
> > > My httpd used to look like:
>
> > > <VirtualHost *:80>
> > > ServerName www.example.com
> > > DocumentRoot /home/published/www/django/
> > > SetHandler python-program
> > > PythonHandler django.core.handlers.modpython
> > > PythonDebug On
> > > PythonPath "['/home/published/www/django', '/home/
> > > published/www/django/catalog'] + sys.path"
> > > SetEnv DJANGO_SETTINGS_MODULE catalog.settings
> > > </VirtualHost>
>
> > > At this point I can't remember where I brought Django down with SVN.
> > > I thought it was /home/publisehd/www/django
>
> > > Any advice on setting up mod_python using the default Hardy install
> > > path?
>
> > First drop into a python shell and try:
>
> > import django
>
> > Does that work without any errors? If so, Hardy has already installed
> > Django in your Python path and you can remove the part "'/home/
> > published/www/django'," from your Apache conf's PythonPath directive.
>
> Sorry, I suspect that what you are telling him is wrong and you
> misunderstand what he is telling you about his setup. I don't believe
> he is saying that that is where Django is installed, but where his
> Django site is being held. It is known that when using mod_python that
> you must list the parent directory of where the site is placed.
> Depending on how you set up stuff in urls.py and other places, you
> must also list the site directory itself.
Graham, you are quite right. I misunderstood the OP. It seems that
from his pre-upgrade Apache conf, that Django was in his Python path
previously and that '/home/published/www/django' in PythonPath is
merely there to ensure that catalog.settings is resolvable.
So, it seems that the OP needs to:
1. Check if "import django" works in a Python shell to verify that
Django is still in Python's path and
2. Show us a trace of the errors he is seeing (from Apache logs and
his browser screen)
Thanks,
-Rajesh D
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
