Changes between Version 57 and Version 58 of BetterErrorMessages


Ignore:
Timestamp:
02/26/2014 12:39:38 AM (15 months ago)
Author:
anubhav9042
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • BetterErrorMessages

    v57 v58  
    8989I think it would be a really good idea to make it really clear from the error message what you need to do (blank=True requires null=True on foreign key fields).
    9090
    91 Unfortunately we can't automatically fix it, because if the field is left blank, the developer might be intending to supply the value automatically before save (https://code.djangoproject.com/ticket/13824).
     91Unfortunately we can't automatically fix it, because if the field is left blank, the developer might be intending to supply the value automatically before save (#13824).
     92A similar issue occurs here: #13776
    9293
    9394Here are some tickets that must be paid attention to:
     
    123124== django.template ==
    124125
    125  When resolving a template variable that calls an object method/property. If that method/property has errors we get a {{{VariableDoesNotExist}}} exception without what errors happened, which might confuse the user.
    126  See #16383 for more details.
     126When resolving a template variable that calls an object method/property. If that method/property has errors we get a {{{VariableDoesNotExist}}} exception without what errors happened, which might confuse the user.
     127See #16383 for more details.
    127128
    128  Looking at these might be useful: #6907 and #11421.
     129Looking at these might be useful: #6907 and #11421.
    129130
    130131* See [http://groups.google.com/group/django-developers/browse_thread/thread/42aff5c291a69041/d006eb5292b8aac3 this thread on the django-developers list] for discussion of suppression of TypeError in the template engine.
Back to Top