Closed selected-pixel-jameson closed 2 years ago
The same. DAL which is coming from django-taggit breaks django3.2 native autocomplete...
+1 - Django-taggit > autocompleate-light > PermissionDesined
BTW the issue is appearing only when taggit & native autocomplete are on the same page.
@Atorich That is not the case for me. I don't have taggit on the page in question, but it is installed.
This issue happens for me when I use DAL in conjunction with native django autocomplete. It's been fixed on this PR: https://github.com/yourlabs/django-autocomplete-light/issues/1239
It has been fixed in 3.9.0rc1 pip install https://github.com/yourlabs/django-autocomplete-light/archive/refs/tags/3.9.0rc1.tar.gz
When I upgrade to Django 3.2 (works fine on Django 3.1) I'm running into the error described in the link below. https://code.djangoproject.com/ticket/32659?cversion=2&cnum_hist=2
I've come to find that this error is not being generated by a Django AutoComplete Light field however, It is being generated by autocomplete_fields = [field_name] in the Django Admin.
My best guess is that there is some kind of conflict with the Django 3.2 updates and the Select2.js script.
I have a need to be able to use both Djangos autocomplete_fields as well as custom DAL AutoComplete queries.
I currently have DAL 3.8.2 installed.
Any insight into this issue would be very helpful. Thank you.