#13776: is_valid() with null field value on ModelForms from models with non-
nullable ForeignKeys causes ValueError
-------------------------------------+-------------------------------------
Reporter: peterbe | Owner:
| anubhav9042
Type: Bug | Status: closed
Component: Forms | Version: master
Severity: Normal | Resolution: fixed
Keywords: ModelForm | Triage Stage: Accepted
ForeignKey |
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Claude Paroz <claude@…>):
In [changeset:"158b0a28374054b1c3f94a9602b69f93fc980448" 158b0a28]:
{{{
#!CommitTicketReference repository=""
revision="158b0a28374054b1c3f94a9602b69f93fc980448"
[1.8.x] Fixed #25431 -- Readded inline foreign keys to modelformset
instances
Too much field exclusions in form's construct_instance() in _post_clean()
could lead to some unexpected missing ForeignKey values.
Fixes a regression from 45e049937. Refs #13776.
Backport of 65a1055a3 from master.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/13776#comment:23>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" 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].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.3ff4596a51a9553d7197c9df63392d6e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
