there is a very comfortable api for adding actions to the model admin in
the admin site.
These actions are then integrated into the admin's object list view of
the given model type in the admin area.
It seems to be also very logical to provide a way of showing these actions
in the object detail view.
This would be also very comfortable because it would not require a
django developer to override the object detail view template.
And would make django development more object oriented: it would require
to define all specific actions in the admin model.
I will try to develop the required functionality.
With best wishes
Roman Glebov
This is a problem in general with any actions performed on the same
screen a change form.
1. User enters the object detail view
2. User changes a field
3. User selects an action.
Does the action apply to the saved or unsaved state? If the former
then the admin must warn that the object will be saved before
performing the action whereas the latter option would be rather
confusing (do we keep or drop the changes?)
In general I don't think performing actions on an object makes sense
in 'edit' mode and there is no details view in the Django admin other
than an 'edit' mode.
https://github.com/crccheck/django-object-actions
Combining with other admin plugins that change the template requires overriding the template to fit both changes in.
The actions are GETs and have no card protection.