-
Notifications
You must be signed in to change notification settings - Fork 660
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
Django 3.0 #927
Comments
see d1e697a |
Bug - TabularInlines do not clone the SELECT lists when using Versions:
The first element works but clicking "Add Another" does not retain the SELECT2 settings nor reinitialised the forms. Example
The SELECT list that is created looks like this
So the SELECT2 classes are not being copied. I have removed Grappelli and re-tested using the native Django Admin templates and those work. |
Related. I find that if you use both StackedInline and TabularInline classes within the same django admin page then SELECT2 errors. Though I can see that it is loading in both the Grappelli and normal Django admin autocomplete JS and CSS files (even with caching disabled within the browser). This results in both a JS warning and a JS error
UPDATE 1 : On further testing this also happens when using just the StackedInline. UPDATE 2: Having now had this error I can not even get the page to render the contents the first time around anymore. I have using local storage for testing, where the static files are collected two folders up. I have deleted all of the files from that folder and then re-run collect static but it is still including the original files including UPDATE 3 I have grappelli as my first entry within INSTALLED_APPS as well as within the projects base urls.py but do still get clashes with these files though it should ignore the default Django ones over Grappelli as that one comes first.
Update 4 |
@StevenMapes thanks for the extensive testing. we'll take a look asap. |
I've added a fix to stable/2.14.x which works with my setup. Please let me know if this also fixes your issue – if so, I'll do a release. |
I can confirm that the issues I was seeing with both TabularInline and StackedInline are both now working with Django 3.0.3 using the latest 2.14.x branch |
No description provided.
The text was updated successfully, but these errors were encountered: