The AutoModelSelect2Field does not work for new added form when used with admin.StackedInline

[yflau]

I want to use the AutoModelSelect2Field in django admin within a inline form like this:

forms.py

class ProductChoices(AutoModelSelect2Field):
    queryset = Product.objects
    search_fields = ['name__icontains', ]

class OrderItemAdminForm(forms.ModelForm):
    product = ProductChoices(required=False, label=_("Product"))
    performlist = forms.DateTimeField(required=False, widget=PerformList)
    pricelist = forms.IntegerField(required=False, label=_("Price List"), widget=PriceList)
    class Meta:
        model = OrderItem

admin.py

class OrderItemInline(admin.StackedInline):
    form = OrderItemAdminForm
    model = OrderItem
    extra = 1
    fields = ('product', 'performlist', 'pricelist', 'price', 'quantity', 'receivable', 'received')
    raw_id_fields = ['price',]

it is all ok but when I click the add another inline form, the AutoModelSelect2Field of the new added form does not work, I think I should use jquery live method to bind new add element, but I don't know how to do? Can you give me some hints, thanks

[applegrew]

It is hard to say. What is the js code you are talking about? Also it would be helpful if u have a demo page to show your problem.

[yflau]

Maybe I did not express my problem exactly , so I forked the django-select2 and modify the testapp to give a example, you can find it here:

https://github.com/yflau/django-select2

If you run the example, you need to login django admin with username admin and password admin , then
you can navigate to this url:

http://127.0.0.1:8000/admin/testmain/dept/add/

the screen look like this:

here we can use the word field normally, then click the Add another Employee link, the screen look like this:

and the word field of the new added Employee form will not work.

[applegrew]

There doesn't seem to be an easy way. The admin JS makes an empty clone which it uses to replicate when new rows are added. However it simply clones, not the event-handlers, only the DOMs and data associated. Still not sure how to handle this.

[applegrew]

The only way I see of fixing this.. Develop a new Admin portal, where on clicking Add new row, instead of cloning the DOMs it would make an Ajax call to server. The server would then just render only the row and return that. The JS on Admin side would then have to simply insert that html code in a new row.

[BertrandBordage]

Good news!

I spent 4 hours on this issue today. And I finally managed to make a workaround: https://gist.github.com/BertrandBordage/8288704.

Of course, it's totally unperfect, but I wanted to point out the fact that we can get it working without any modification on Django itself.

[applegrew]

Cool. The best solution is to create custom add and list pages for this library.

[BertrandBordage]

Are you sure that would be the best solution? Adding custom ModelAdmins in django-select2 means even complex setups when using several third-party apps (like django-reversion, django-polymorphic, django-mptt, etc).

[applegrew]

I did not try that, but seems to be the cleanest approach. Due to the nature of this library it needs to depend on some hacky JS codes. The best way to handle is to have custom page which is aware of that and takes care to not break those codes. Unless and until there are other third party hacky apps which too needs to inject some JS code into admin pages to get them working, then we are okay.