Thanks so much for this. Exactly what I needed. Works great and I've also discovered reverse_lazy() for use with my urls.py in cases such as the next_page variable for authentication. One issue I have found is when wanting to have urls with optional arguments. Overloading the view function with several urls can cause issues with the reversing although I guess this forces one to write better URLs...
Again many thanks for the help with this - much appreciated. Kind regards Huw On Monday, 3 June 2013 15:50:21 UTC+1, huw_at1 wrote: > > Hi there, I've run into an issue whereby on production my Django project > is accessed from a URL such as http://example.com/django_project/. Apache > is configured to host the code under this URL since I do not want the > entire site managed by the Django project. My problem is that when I run > the Django test server I have a lot of broken links as it wants to run the > project from 127.0.0.1 instead of 127.0.0.1/django_project/. Ideally I'd > like to have the Django test server reproduce the apache configuration. > What is the best way to resolve this does anyone have any experience? > > Many thanks > > Huw > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users. For more options, visit https://groups.google.com/groups/opt_out.
