Remove 'Delete selected profiles' action from the admin

RESOLVED FIXED in 2013Q3

Status

support.mozilla.org
Users and Groups
P4
normal
RESOLVED FIXED
6 years ago
4 years ago

People

(Reporter: jsocol, Assigned: berkerpeksag)

Tracking

unspecified
2013Q3

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: u=sumo-team c=admin p=0 s=2013.16 [mentor=r1cky])

(Reporter)

Description

6 years ago
Profile objects can't be deleted anyway. Remove the bulk "Delete selected profiles" action from the admin.
(Reporter)

Comment 1

6 years ago
http://people.mozilla.org/~mverdi/screenshots/delete-20111108-120047.jpg < This is what I mean.
(Reporter)

Updated

6 years ago
Target Milestone: 2011-11-15 → ---
hey can I do this ?
sure!
Assignee: james → michaljev
Status: NEW → ASSIGNED
Whiteboard: u=user c=admin p=0 s=2013.backlog [mentor=r1cky]
Whiteboard: u=user c=admin p=0 s=2013.backlog [mentor=r1cky] → u=sumo-team c=admin p=0 s=2013.backlog [mentor=r1cky]
It is little tricky I tried adding actions in admin class but it didnt help, adding admin.site.disable_action('delete_selected') removes it from everywhere and again using actions or admin.site.add_action doesnt help.
r1cky any ideas ? :(
(In reply to Michał Frontczak :fxa90id from comment #5)
> r1cky any ideas ? :(

Look here: https://docs.djangoproject.com/en/dev/ref/contrib/admin/actions/#conditionally-enabling-or-disabling-actions

:)
tried this too :<
any ideas?
Hey Michal, did you make any progress on this? Berker beat you to a pull request:
https://github.com/mozilla/kitsune/pull/1573
Flags: needinfo?(michaljev)
Assignee: michaljev → berker.peksag
Flags: needinfo?(michaljev)
Landed on master:
https://github.com/mozilla/kitsune/commit/f9e226f496f4cf18bf857a891799538acd5bd601
Current sprint.
Priority: -- → P4
Whiteboard: u=sumo-team c=admin p=0 s=2013.backlog [mentor=r1cky] → u=sumo-team c=admin p=0 s=2013.16 [mentor=r1cky]
Target Milestone: --- → 2013Q3
Deployed to prod now. Thanks all!
Status: ASSIGNED → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.