Closed m-melis closed 3 years ago
If you downgrade to version 1.0, does it still happen? I just changed one CSS class, 🤔
Works fine with version 1.0 and Django 3.2, yes!
Greetings fellows,
I can confirm that 1.0.1 (and #273 in particular) leads to the described issues (and broken inline behaviour in general).
Our setup:
And when rolling back to django-admin-sortable2 1.0.0 all works as expected. I wonder if we can fix custom admin interfaces and CSS frameworks in some other ways, however I don't see a good solution yet. :(
Best, Rust
Without having a setup where I can test this, could you please do me a favor: Use the latest version from GitHub and try again. If that helps, I'll release version 1.0.2
Working fine again after installing the latest github version. 👍🏼
Version 1.0.2 is available.
Just upgraded to django 3.2 and found the following. Using
TabularInline
withSortableInlineAdminMixin
a double "new item" row is added. This does not happen in the case of theStackedInline
.django-admin-sortable2 version 1.0.1
SortableInlineAdminMixin, admin.TabularInline:
admin.TabularInline:
SortableInlineAdminMixin, admin.StackedInline:
Thanks for your work.