Ramiro, thanks for the links. That other thread does seem to describe
the same problem and results in it being identified as a bug in the
core urlresolvers. Unfortunately the work around of "RewriteRule ^/
studio$ /studio/ [R] " doesn't work for me for some reason. Maybe I'm
misapplying it.
Either way. I'm going to drop this for now and see what happens with
the ticket that was opened. It seems like this would be a very big
issue if everyone using mod_wsgi had problems when using django from
anywhere other than the root url. But there are few posts about it.
So I'm going to start over and see if I missed something critical in
my setup.
Thank you -Shane
On Jan 3, 3:01 pm, Ramiro Morales <cra...@gmail.com> wrote:
> On Sun, Jan 3, 2010 at 4:44 PM, davathar <davat...@gmail.com> wrote:
> > Thank you for the responses so far. But I still haven't identified
> > the solution to this seemingly simple issue.
>
> > The behavior also happens when I use the URL tag in a template like
> > this "{% url case_url case.id %}" the result I get is "/support/case/
> > 1/ ".
>
> > So the inconsistency is that when I make a request for "http://
> >www.example.com/helpdesk/support/1/" django is correctly mapping to
> > the "case" view. But while processing the "case" view and explicitly
> > naming the "case_url" that points to it, any reverse lookups are not
> > returning the correct URL.
>
> > To me it looks like a bug since I would think it would work both ways
> > or neither.
>
> > I think it may have to do with my switch to django 1.1.1 and mod_wsgi
> > from an older 1.x version with mod_python.
>
> > When using mod_python, this was handled like so:
>
> > <Location "/mysite/">
> > SetHandler python-program
> > PythonHandler django.core.handlers.modpython
> > SetEnv DJANGO_SETTINGS_MODULE mysite.settings
> > PythonOption django.root /mysite
> > PythonDebug On
> > </Location>
>
> > But according to this:
> > http://code.google.com/p/modwsgi/wiki/IntegrationWithDjango
> > "Note that the django.root option introduced in Django 1.0 alpha
> > versions does not apply to mod_wsgi and is only necessary with
> > mod_python, due to mod_python not setting SCRIPT_NAME correctly. "
>
> > So where does that leave us? does mod_wsgi need some other
> > configuration?
>
> I'd suggest to read this recent django-users thread:
>
> http://groups.google.com/group/django-users/browse_frm/thread/ce14366...
>
> that point to this Django ticket:
>
> http://code.djangoproject.com/ticket/9435
>
> Another suggestion: Ty dropping the project name from all the imports
> and view names
> when setting your mod_wsgi deployment, just make sure themodules containing
> your
> settings.py, urls.py and all your apps are in the python module search path.
>
> HTH,
>
> --
> Ramiro Morales | http://rmorales.net
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-us...@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.
