Version bump to 2.1.11
Updated README.
This commit is contained in:
@@ -606,8 +606,8 @@ ordering on top of that just seemed a little much in my opinion.
|
|||||||
### Status
|
### Status
|
||||||
django-admin-sortable is currently used in production.
|
django-admin-sortable is currently used in production.
|
||||||
|
|
||||||
### What's new in 2.1.10?
|
### What's new in 2.1.11?
|
||||||
- Updated admin templates to use the `CSRF_HEADER_NAME` from [settings](https://docs.djangoproject.com/en/2.1/ref/settings/#csrf-header-name) instead of using a hard-coded value.
|
- Fixed missing `csrfmiddlewaretoken` in Ajax POST data. This affects Django 2.1.4 and higher.
|
||||||
|
|
||||||
### Future
|
### Future
|
||||||
- Better template support for foreign keys that are self referential. If someone would like to take on rendering recursive sortables, that would be super.
|
- Better template support for foreign keys that are self referential. If someone would like to take on rendering recursive sortables, that would be super.
|
||||||
|
|||||||
+2
-4
@@ -745,12 +745,10 @@ Status
|
|||||||
|
|
||||||
django-admin-sortable is currently used in production.
|
django-admin-sortable is currently used in production.
|
||||||
|
|
||||||
What’s new in 2.1.10?
|
What’s new in 2.1.11?
|
||||||
~~~~~~~~~~~~~~~~~~~~~
|
~~~~~~~~~~~~~~~~~~~~~
|
||||||
|
|
||||||
- Updated admin templates to use the ``CSRF_HEADER_NAME`` from
|
- Fixed missing `csrfmiddlewaretoken` in Ajax POST data. This affects Django 2.1.4 and higher.
|
||||||
`settings <https://docs.djangoproject.com/en/2.1/ref/settings/#csrf-header-name>`__
|
|
||||||
instead of using a hard-coded value.
|
|
||||||
|
|
||||||
Future
|
Future
|
||||||
~~~~~~
|
~~~~~~
|
||||||
|
|||||||
@@ -1,4 +1,4 @@
|
|||||||
VERSION = (2, 1, 10)
|
VERSION = (2, 1, 11)
|
||||||
DEV_N = None
|
DEV_N = None
|
||||||
|
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user