Changes between Version 51 and Version 52 of BetterErrorMessages

Timestamp:

Nov 13, 2013, 9:04:21 PM (10 years ago)

Author:

Elena Williams

Comment:

--

BetterErrorMessages

@@ -66 +66 @@
 '''Context:''' This error gets raised when a server started by runserver is (by accident) accessed via `https://`. [http://thinkhole.org/wp/2007/03/01/django-wsgirequesthandler-error/ Details here].[[BR]]
 '''Suggestion:''' runserver does not support https, please use it only via http.
+
+
+== django.core.urlresolver ==
+
+{{{
+ImproperlyConfigured: The included urlconf %s doesn't have any patterns in it.
+}}}
+
+Uninformative foremost as '''%s''' is top-level urls (problem usually in included urls).
+
+Caused by using '''reverse''' rather than '''reverse_lazy''' in some view.
+
+No feedback whatsoever is given as to:
+- that the error is caused by view rather than url
+- which view this might be, or even which app it is in.
+
+
+'''Context:''' You get this error starting the developer server. The error is cached (#11712) and fixing it doesn't make the error go away adding to the confusion.[[BR]]
+'''Suggestion:''' At least more specificity as to where the error lies.
+
+Related tickets:
+
+- https://code.djangoproject.com/ticket/17084
+- https://code.djangoproject.com/ticket/15685
+- https://code.djangoproject.com/ticket/11712  
 
 == django.db ==