Changes between Version 51 and Version 52 of BetterErrorMessages


Ignore:
Timestamp:
11/13/2013 09:04:21 PM (17 months ago)
Author:
elena
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • BetterErrorMessages

    v51 v52  
    6666'''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]]
    6767'''Suggestion:''' runserver does not support https, please use it only via http.
     68
     69
     70== django.core.urlresolver ==
     71
     72{{{
     73ImproperlyConfigured: The included urlconf %s doesn't have any patterns in it.
     74}}}
     75
     76Uninformative foremost as '''%s''' is top-level urls (problem usually in included urls).
     77
     78Caused by using '''reverse''' rather than '''reverse_lazy''' in some view.
     79
     80No feedback whatsoever is given as to:
     81- that the error is caused by view rather than url
     82- which view this might be, or even which app it is in.
     83
     84
     85'''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]]
     86'''Suggestion:''' At least more specificity as to where the error lies.
     87
     88Related tickets:
     89
     90- https://code.djangoproject.com/ticket/17084
     91- https://code.djangoproject.com/ticket/15685
     92- https://code.djangoproject.com/ticket/11712 
    6893
    6994== django.db ==
Back to Top