On Sat, Apr 11, 2009 at 5:13 PM, codecowboy <guy.ja...@gmail.com> wrote: > I've followed some examples from around the Django community and that > is why I use the reverse() method at all. What is the point of using > the reverse() method?
Well, there's a problem you'll run into fairly often. Suppose, for example, that you set up a weblog, and you have it at the URL "/weblog/". So in your templates you have links to "/weblog/", in your code the get_absolute_url() method of entries returns a string containing "/weblog/", any redirects involved have to have "/weblog/" in the URL, etc. And then one day you suddenly need to deploy another copy of the appliation, but on a site which wants the weblog at "/blog/". Reverse URL resolution lets you easily make this kind of change, or have an application reused on different sites without changing the code, by looking up the correct URL in your actual URL configuration instead of hard-coding it all over the place. But in order to work, all your URL patterns have to point to views which actually exist and which live in files that don't raise any kind of import or syntax errors, since the reverse resolution system has to scan through your URL patterns to find the right one. If you have any errors in a view file, or have a URL pattern pointing to a view that doesn't actually exist in your code, reverse resolution won't work. -- "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
