id,summary,reporter,owner,description,type,status,component,version,severity,resolution,keywords,cc,stage,has_patch,needs_docs,needs_tests,needs_better_patch,easy,ui_ux 30014,Initialising disabled ModelChoiceField yields 'Select a valid choice'-error despite initialised option being valid,Thomas Hamann,Etienne Chove,"I have a form with a ModelChoiceField that gets initialised to a specific value using get_initial in that form's View. This value is a valid choice for that Model. I don't want the user to be able to change the option on the form, but it needs to be displayed nonetheless. When I set disabled=True on that field in forms.py, submitting the form yields the following error: . Firstly, I would like to comment on the general quality of the error message, as it is not very useful: It does not return ''which'' choice it considers invalid. Including this information would make the message much more informative, and would avoid sending people on a wild goose chase to discover what the message could possibly mean. Secondly, if a field is disabled but does contain a valid choice, validating the form should work and not trigger an error. Edit: Adding the **to_field_name** option to the form field fixes the problem. However, when disabled=True is not present, this is not required. This is probably related to the bugfix for this bug: #28387",Bug,closed,Forms,dev,Normal,fixed,"forms, disabled field, error, to_field_name",Etienne Chove,Ready for checkin,1,0,0,0,0,0