Welcome to django-reorder-items-widget
Links
Description
Reorder your items by simply dragging them to their new position. This works fine within admin changelists and inline formsets.
The main component is the ReorderItemsWidget which provides the drag and drop interface on top of an index field and updates the indexes of listed items on form submission.
Still there are some neccessary setups to make a full functional admin integration of the reorder items feature: we need a model field for the widget, an appropriate admin configuration and we probably do not want to update indexes manually when adding or removing items bypassing the widget. Therefore we use some signal handlers for the model field.
This app provides everything you need to make this setup as easy as possible.
Installation
Install via pip:
pip install django-reorder-items-widget
Add reorder_items_widget to your INSTALLED_APPS:
INSTALLED_APPS = [
'reorder_items_widget',
...
]
Getting started
Setup for a reorderable changelist
Add a ReorderItemsField field to your model:
from django.db import models
from reorder_items_widget import ReorderItemsField
class Item(models.Model):
...
index = models.ReorderItemsField()
class Meta:
ordering = ('index',)
Setup your model admin using the ReorderItemsModelAdmin:
from django.contrib import admin
from reorder_items_widget import ReorderItemsModelAdmin
class ItemModelAdmin(ReorderItemsModelAdmin):
...
You don't have to do anything with the index field in your model admin. It's already setup by the base class.
Now you can reorder your items within the changelist only by drag and drop. And completely forget about the index field which won't show up in the whole admin backend at all.
Setup for a reorderable inline
Again setup your models with a ReorderItemsField:
from django.db import models
from reorder_items_widget import ReorderItemsField
class Container(models.Model):
...
class Item(models.Model):
...
index = models.ReorderItemsField(grouped_by=['container'])
container = models.ForeignKey(Container, on_delete=models.CASCADE)
class Meta:
ordering = ('container', 'index')
Mind the grouped_by argument for the ReorderItemsField. This argument tells
the field, that the ordering should be container specific. For each container
object the indexes of the related items will start anew with zero.
Now setup the model admins using the ReorderItemsInline:
from django.contrib import admin
from reorder_items_widget import ReorderItemsInline
class ItemInline(ReorderItemsInline):
...
class ContainerModelAdmin(admin.ModelAdmin):
inlines = (ItemInline,)
Again there is no need to handle the index field.
Now visit the changeform of your container object and enjoy reordering its items.
Caveats
The widget will always number your items sequentially. So reordering a filtered list of items might have unexpected results. Paging however should not be a problem since the index of the first listed item will be used as a base.
Contribute
Feedback, feature requests, bug reports or pull requests are most welcome. Just use the common github infrastructure.
Metadata
Release files for django-reorder-items-widget 1.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| django_reorder_items_widget-1.2.0.tar.gz | 10.2 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| django_reorder_items_widget-1.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 23.3 kB
Release files / django_reorder_items_widget-1.2.0.tar.gz
| Download URL | django_reorder_items_widget-1.2.0.tar.gz |
|---|---|
| Size | 10.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a49ef1a8935d166595e4b147b10d12502f1b39e8990c2d1b66636a99098463a2
|
|
BLAKE2b-256 checksum How to use checksums |
6be0c1a4041f1ff4eedae5fd68edcd6068eee3f1be604067916fe03c3d65e235
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 3, 2026.
Transparency logRelease files / django_reorder_items_widget-1.2.0-py3-none-any.whl
| Download URL | django_reorder_items_widget-1.2.0-py3-none-any.whl |
|---|---|
| Size | 13.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f88242e328a54dc3843ea083c1847836f70afb8e64a23a2ef02bf43357b82860
|
|
BLAKE2b-256 checksum How to use checksums |
63004024582bb1410c073b2391ee748d3bb89042a4e326a831ac8f8cfa7a5cb2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 3, 2026.
Transparency log