#34119: Admin: ArrayField in inlines are not properly validated
-------------------------------------+-------------------------------------
Reporter: Benjamin Rigaud | Owner: nobody
Type: Bug | Status: new
Component: Uncategorized | Version: 3.2
Severity: Normal | Resolution:
Keywords: admin, arrayfield, | Triage Stage:
forms | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by David Sanders):
This is because the inline form is considered to be changed on the first
submission but not on the second submission.
Fields with callable defaults have a hidden widget which then used to
detect if it's changed – a mechanism implemented long ago to preserve
changing defaults between submissions like `timezone.now`.
I think the problem here is that the hidden widget is being populated with
the submitted data instead of the result of the callable default. I've
submitted a PR to prevent these hidden widgets from being overridden by
submitted values.
--
Ticket URL: <https://code.djangoproject.com/ticket/34119#comment:3>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/01070184141bd7f8-812af925-04e8-43a3-b9da-de0458b7aa93-000000%40eu-central-1.amazonses.com.
