-
Notifications
You must be signed in to change notification settings - Fork 15
dat version 1.3 #7
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
base: master
Are you sure you want to change the base?
Conversation
…".field-foo"). keep previous for compatibility.
… set their own `order` field. (provides easier migration in the event of an existing database with a similar field.)
… bug that prevented editing of inputs inside OrderableTabularInline
…lows ordering in the change list)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This (and L37 below) are basically equivalent to {% static "orderable/orderable.js" %}. Don't know why it's not in django docs, but simply prepending STATIC_URL isn’t always helpful (especially when using django-storages + S3).
|
even funnier is that someone else took the name in the intervening two years |
|
Bummer. :( @tkaemming Could this stuff still be merged back, or released on PyPI? |

Changes/Fixes
orderable.teststo it's owndemosrcdir in the repo.BaseOrderableModelthat provides all of theOrderableModelbehavior without definingorderfield. (So thatordercan be defined manually by an implementing class.) Done because I needed to throw this on top of an existing model.staticfilesinstead of relying on user to copyorderable.jsinto MEDIA_ROOT.Bugs/Notices
Upgrade caveats
staticfiles. (Admin in 1.4+ relies on it, anyway.) Existing installs can remove the previously user-copiedorderable.js.