Changes between Version 57 and Version 58 of BetterErrorMessages

Timestamp:

Feb 26, 2014, 12:39:38 AM (10 years ago)

Author:

ANUBHAV JOSHI

Comment:

--

BetterErrorMessages

@@ -89 +89 @@
 I 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).
 
-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).
+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 (#13824).
+A similar issue occurs here: #13776
 
 Here are some tickets that must be paid attention to:
@@ -123 +124 @@
 == django.template ==
 
- 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.
- See #16383 for more details.
+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.
+See #16383 for more details.
 
- Looking at these might be useful: #6907 and #11421.
+Looking at these might be useful: #6907 and #11421.
 
 * 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.