Re: Continuing problems running Django when not site Root.

Okay I am finnally getting my brain around this. Thanks so much. I tried the code out and it works great, even on the login. I appreciate everyone's help and patience. On Aug 8, 9:49 pm, Malcolm Tredinnick wrote: > On Sat, 2009-08-08 at 13:41 -0700, Streamweaver

Re: Continuing problems running Django when not site Root.

On Sat, 2009-08-08 at 13:41 -0700, Streamweaver wrote: > Let me clarify. This method handles the RequestContext obviously since > it's a login but what I mean is the SCRIPT_NAME variable isn't set for > the template and can't be read as far as I can tell. Nothing is automatically set for a

Re: Continuing problems running Django when not site Root.

Let me clarify. This method handles the RequestContext obviously since it's a login but what I mean is the SCRIPT_NAME variable isn't set for the template and can't be read as far as I can tell. On Aug 8, 4:15 pm, Streamweaver wrote: > I appreciate all the comment here

Re: Continuing problems running Django when not site Root.

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/$',

Re: Continuing problems running Django when not site Root.

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

Re: Continuing problems running Django when not site Root.

Django since 1.0 onwards is usually fine with SCRIPT_NAME. Quite possibly you have tweaked something in settings or setup urls.py wrong to cause the issue. I would suggest you start over with a fresh Django installation and create the most minimal working example of what you are trying to do and

Continuing problems running Django when not site Root.

There's been some discussion here about what to do when you're trying to run a Django site not under the root domain. So for a site like http://mysite.com/django/ Django (or WSGI?) doesn't seem to be able to be able to handle the SCRIPT_NAME ('/django' in this example) portion of the url well.