#30014: Initialising disabled ModelChoiceField yields 'Select a valid
choice'-error
despite initialised option being valid
-------------------------------------+-------------------------------------
Reporter: thoha | Owner: nobody
Type: Bug | Status: closed
Component: Forms | Version: 1.11
Severity: Normal | Resolution: needsinfo
Keywords: forms, disabled | Triage Stage:
field, error, to_field_name | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Simon Charette):
> Even if the problem with get_initial can't be tracked down, fixing the
unhelpful error message itself would be an improvement, too.
thoha, the main problem here is that we can't reproduce your problem with
the details you provided. If you can provide a minimal test project that
reproduces your issue against Django 2.1 we'll certainly investigate more
but at this point nothing proves Django is at fault.
--
Ticket URL: <https://code.djangoproject.com/ticket/30014#comment:6>
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/063.859a50d20f8bb5f74925fae87b0ebc9d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
