Yes. At first I tried setting default=True or default=False for my BooleanField and kept getting the same error. So I went back in, deleted the model, tried again, got the same error. Then I deleted my db sqlite3 file, made new migrations, migrated (with the model not even a part of my models.py anymore) and am still getting this error.
On Friday, June 30, 2017 at 11:37:26 AM UTC-6, Guilherme Leal wrote: > > >>>>>>>django.core.exceptions.ValidationError: [u"'' value must be either > True or False."] > > > Have you tried to set the default value of the BooleanField as True or > False? BooleanFields must have a valid boolean as default value and so > happends that empty string is not a valid boolean. > > Change the default value to False (as exemple), run the migration again, > and it should work. > > > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/07fe41c0-25f9-491a-8af8-b6b4c20c4a09%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
