#30014: Initialising disabled ModelChoiceField yields 'Select a valid 
choice'-error
despite initialised option being valid
-------------------------------------+-------------------------------------
     Reporter:  thoha                |                    Owner:  Etienne
                                     |  Chove
         Type:  Bug                  |                   Status:  closed
    Component:  Forms                |                  Version:  master
     Severity:  Normal               |               Resolution:  fixed
     Keywords:  forms, disabled      |             Triage Stage:  Ready for
  field, error, to_field_name        |  checkin
    Has patch:  1                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------

Comment (by Mariusz Felisiak <felisiak.mariusz@…>):

 In [changeset:"651299e1ef896210035cf9e6992b07aa02a5aac1" 651299e1]:
 {{{
 #!CommitTicketReference repository=""
 revision="651299e1ef896210035cf9e6992b07aa02a5aac1"
 [3.0.x] Fixed #30014 -- Fixed ModelChoiceField validation when initial
 value is a model instance.

 Thanks Carlton Gibson for reviews.

 Backport of e7cdb0cd7eb5eb677af8dae7bfc6845186f861b0 from master
 }}}

-- 
Ticket URL: <https://code.djangoproject.com/ticket/30014#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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.407af813708d94339954b612ce4b33ca%40djangoproject.com.

Reply via email to