I appreciate all the comment here and I definitly could be missing
something.

I tried backing out to a fresh install as requested above.

The issue as best I can understand it lies in the default login
scripts provided which are called as follows in my urls.py file

    (r'^accounts/login/$', 'django.contrib.auth.views.login',
{'template_name': 'accounts/login.xhtml'}),
    (r'^accounts/logout/$', 'django.contrib.auth.views.logout',
{'template_name': 'accounts/logout.xhtml'})

The templates that normally handle rendering the SCRIPT_NAME property
don't do so here I think because this script isn't being passed the
RequestContext like other scripts.  I'll take a look at the source
code for these items and it's likely I can pass a property to it but
I'm a bit unsure how since the request object isn't passed to urls.py
as far as I know.

If you have more insight it would be helpful but so far my
investigation seems to be turning up that I can't use these magic
methods.

Thanks again and I'll keep looking this weekend and post if I find
what I'm doing wrong.

On Aug 7, 10:49 pm, Malcolm Tredinnick <malc...@pointy-stick.com>
wrote:
> On Fri, 2009-08-07 at 14:44 -0700, Streamweaver wrote:
>
> [...]
>
> > Is there anyway around this?  Anyone know if fixing this on the Django
> > roadmap?
>
> It was fixed over a year ago (before Django 1.0 came out). If you are
> using anything later than that, you don't have to do *anything* to worry
> about SCRIPT_NAME, although the variable is set in the request.META
> dictionary so you can use it to construct URLs if you want to do that
> manually.
>
> 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 
django-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to