#24377: UUIDField as primary key breaks inline admins
---------------------------------+-------------------------------------
Reporter: yoyoma | Owner: timgraham
Type: Bug | Status: assigned
Component: Forms | Version: master
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
---------------------------------+-------------------------------------
Comment (by yoyoma):
@timgraham - I tried to debug this some and ended up down a deep rabbit
hole.
I ended up '''possibly''' finding another bug. With stable/1.8.x (without
your changes), given the example models, if you create a {{{Child}}}
instance for an existing {{{Parent}}}, set {{{max_num = 1}}} on the inline
(just to avoid empty forms, since you only created 1 child), then visit
the change view for that {{{Parent}}} and save it, all should be well, but
all is not well. The global {{{Please correct the errors below.}}} appears
at the top, but there are no errors. Removing the inline admin fixes that
issue, and checking "delete" on the inline instance is not met with this
issue, so the issue is certainly pertaining validation of the inline form
or instance.
--
Ticket URL: <https://code.djangoproject.com/ticket/24377#comment:8>
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/064.88de09d0953ccc052223575e84e2cff7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
