[Django] #34097: when i create objects in admin page, it is not posted to server that is selection of ModelMultipleChoiceField with FilteredSelectMultiple widget

9 views

Skip to first unread message

Django

unread,

Oct 14, 2022, 7:27:36 AM10/14/22

to django-...@googlegroups.com

#34097: when i create objects in admin page, it is not posted to server that is
selection of ModelMultipleChoiceField with FilteredSelectMultiple widget
-------------------------------------+-------------------------------------
Reporter: Byoungjun | Owner: nobody
Chung |
Type: Bug | Status: new
Component: | Version: 4.1
contrib.admin | Keywords:
Severity: Normal | ModelMultipleChoiceField,
Triage Stage: | FilteredSelectMultiple, admin
Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
I customized form for UserCreate and UserChange based on UserCreationForm
and UserAdminForm

because My User Model have a many-to-many field.

for the field, I use a ModelMultipleChoiceField with
FilteredSelectMultiple widget.

I works fine for view and change about already created user.

but, when i create new user with the field, selection is not saved.

I cannot find a solution about this with googling.

finally, i found this is a bug after 4.1 version

when i change django version to 4.0.8, it work normally.

this can be reproduced in django default user group creating with several
permission.

4.1, permission is not saved.

4.0.8, permission is saved.

--
Ticket URL: <https://code.djangoproject.com/ticket/34097>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

Django

unread,

Oct 14, 2022, 9:12:42 AM10/14/22

to django-...@googlegroups.com

Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------

Changes (by Tim Graham):

* status: new => closed
* resolution: => duplicate

Comment:

This looks like a duplicate of #33893, fixed in Django 4.1.1. If you're
using that version or later, be sure that an old version of
`admin/js/change_form.js` isn't cached by your browser.