-
Notifications
You must be signed in to change notification settings - Fork 281
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
custom ModelMultipleChoiceField, initial values #137
Comments
couldn't there be a check if the field inherits from a multiple base field, so the |
Can you provide the code needed to reproduce your example? |
the field (widget is not really interesting/important).
point is, the model/modelmultiple only makes sense if one adds the queryset, so there normally is one field per model...probably why the modelmultiple is not at all in the available fields. the error might only occur with modelmultiplechoicefields, I couldnt check this yet. |
adding forms.ModelMultipleChoiceField to *fields.MULTIPLE would help already, and then dealing with subclasses in the .is_a method even more. |
I've developed a new custom field, a custom multiple select. I guess it should be added to this tuple:
otherwise, initial values don't seem to be calculated correctly (I have {{request.GET.offer}}, when passing offer=60, it populates with 60 and 6...).
what would be the proper way to add my field to the MULTIPLE tuple?
The text was updated successfully, but these errors were encountered: