#16168: Form validation is bypassed on Admin Inline ModelForms that define extra
fields
-------------------------------------+-------------------------------------
Reporter: | Owner: nobody
izzaddin.ruhulessin@… | Status: new
Type: | Component: Documentation
Cleanup/optimization | Severity: Normal
Milestone: | Keywords: validation,
Version: SVN | modelforms
Resolution: | Has patch: 0
Triage Stage: Accepted | Needs tests: 0
Needs documentation: 1 | Easy pickings: 1
Patch needs improvement: 0 |
-------------------------------------+-------------------------------------
Changes (by melinath):
* needs_better_patch: => 0
* component: Forms => Documentation
* needs_tests: => 0
* version: 1.2 => SVN
* needs_docs: => 1
* type: Bug => Cleanup/optimization
* stage: Unreviewed => Accepted
Comment:
This does happen in svn as well. However, the problem is not that
validation is being bypassed; because of the invalid input type from the
form field, the attempt to construct an instance fails loudly. There is no
way to get around this cleanly - it's a programming error, not a problem
with django. The most we could do would be to add a note to the
[https://docs.djangoproject.com/en/dev/topics/forms/modelforms
/#overriding-the-default-field-types-or-widgets docs] about the dangers of
not mimicking data type conversion when overriding fields.
--
Ticket URL: <https://code.djangoproject.com/ticket/16168#comment:1>
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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.