#8997: Misleading error message when calling get_absolute_url ------------------------------------------------+--------------------------- Reporter: Rob <[EMAIL PROTECTED]> | Owner: nobody Status: new | Milestone: Component: Uncategorized | Version: 1.0 Keywords: | Stage: Unreviewed Has_patch: 0 | ------------------------------------------------+--------------------------- If a model has a get_absolute_url method that has an error in it (such as a trivial syntax area like a typo in a field name), when you try to view the page, django reports the error as "<Foo> objects don't have get_absolute_url() methods".
This is very misleading and makes it difficult to debug the error if you are not especially familiar with django. I'm guessing the appropriate exceptions are being swallowed somewhere and turned into the wrong error message. -- Ticket URL: <http://code.djangoproject.com/ticket/8997> Django Code <http://code.djangoproject.com/> The web framework for perfectionists with deadlines --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django updates" 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-updates?hl=en -~----------~----~----~----~------~----~------~--~---
