From f23c03ebc81c64b8b41f3aae0dbe93fc283cc43d Mon Sep 17 00:00:00 2001 From: Tim Graham Date: Fri, 30 Sep 2016 14:49:50 -0400 Subject: [1.10.x] Refs #27186 -- Fixed model form default fallback for CheckboxSelectMultiple. Backport of 87c5e7efebd040aef0f0479ccf86877155bb5cea from master --- docs/topics/forms/modelforms.txt | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'docs/topics/forms') diff --git a/docs/topics/forms/modelforms.txt b/docs/topics/forms/modelforms.txt index 3d5bc746fe..768dc3938c 100644 --- a/docs/topics/forms/modelforms.txt +++ b/docs/topics/forms/modelforms.txt @@ -335,7 +335,8 @@ doesn't validate -- i.e., if ``form.errors`` evaluates to ``True``. If an optional field doesn't appear in the form's data, the resulting model instance uses the model field :attr:`~django.db.models.Field.default`, if there is one, for that field. This behavior doesn't apply to fields that use -:class:`~django.forms.CheckboxInput` (or any custom widget whose +:class:`~django.forms.CheckboxInput` and +:class:`~django.forms.CheckboxSelectMultiple` (or any custom widget whose :meth:`~django.forms.Widget.value_omitted_from_data` method always returns ``False``) since an unchecked checkbox doesn't appear in the data of an HTML form submission. Use a custom form field or widget if you're designing an API -- cgit v1.3