#10618 closed (fixed)
Admin Actions: Action form doesn't takes care whose submit button was pushed.
Reported by: | Martin Mahner | Owned by: | nobody |
---|---|---|---|
Component: | contrib.admin | Version: | 1.0 |
Severity: | Keywords: | action | |
Cc: | Triage Stage: | Accepted | |
Has patch: | yes | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
If you have a action-bar on top and on bottom, the response_action function always reads the action from the bottom action-bar.
Attachments (1)
Change History (4)
by , 16 years ago
Attachment: | admin-actions-select-10618-1.diff added |
---|
comment:1 by , 16 years ago
milestone: | → 1.1 |
---|---|
Triage Stage: | Unreviewed → Accepted |
comment:2 by , 16 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
(In [10408]) Made a bunch of improvements to admin actions. Be warned: this includes one minor but BACKWARDS-INCOMPATIBLE change.
These changes are:
(modeladmin, request, queryset)
. Actions defined as methods stay the same, but if you've defined an action as a standalone function you'll now need to add that firstmodeladmin
argument.AdminSite
APIs for dealing with actions, including a method to disable global actions. You can still re-enable globally-disabled actions on a case-by-case basis.ModelAdmin
by settingactions
toNone
.