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. You have to add the request context to the application and views as well as account for it in the templates. Fair enough I guess and I refactored my application to handle this so far. I'm running into pretty big problems with using Django's login framework in this context. First there are the various login settings of 'LOGIN_URL' and such, and these can't be passed a context. I got around this by adding another variable to the settings file I can see in addition to having to read the SCRIPT_NAME in the views and templates. I continue to have a problem though in that the generic login functions seem to have no way to handle SCRIPT_NAME and I suspect this problem extends to generic views in general. Is there anyway around this? Anyone know if fixing this on the Django roadmap? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
