Using FORCE_SCRIPT_NAME is only appropriate for certain WSGI hosting mechanisms. Using it may simply hide the fact that the OPs application code is wrong to begin with.
OP should indicate how they are hosting their application for real site. Ie., mod_python, mod_wsgi, fastcgi or other. Graham On Jul 31, 6:04 am, Alex Koshelev <[email protected]> wrote: > If you are using `{% url %}` template tag or `reverse` function you can set > FORCE_SCRIPT_NAME [1] settings variable specified for your deployment > project root. Or working with right web-server in front of django project > force it to tell proper SCRIPT_NAME himself. > > [1]:http://docs.djangoproject.com/en/dev/ref/settings/#force-script-name > > --- > Alex Koshelev > > On Thu, Jul 30, 2009 at 10:55 PM, Streamweaver <[email protected]>wrote: > > > > > > > I have a django project that has worked just fine in development but > > I'm trying to move it to a demo site and the application is not on a > > root domain or sub-domain. > > > Instead the site root URL is suppose to be something like > >https://site.domain.com/appname/ > > > This is causing all my template links to break. The {% url %} tag > > seems to work only for the site root and doesn't bring in the > > subdirectory name. > > > What's the Django way of handling this? I'm surprised I haven't been > > able to find something about this. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
