On Sat, Apr 4, 2009 at 7:10 PM, kmike <[email protected]> wrote:
> > Totally agree, bulk delete shouldn't be enabled by default. > > One more issue with that: it is nice to be able to define actions > order in drop-down list. It can be achieved with very simple patch, > see http://code.djangoproject.com/ticket/10734 . But if we have delete > action (or any other action) enabled by default, this patch will > always put it at top and we will have to overload "get_actions" method > again to fix it. > > > > It seems to me that the default behavior of including items from every parent class is causing more harm than good. I'm very tempted to say we might be better off just requiring users to either relist every item or do: class MyModelAdmin(ModelAdmin): actions = ModelAdmin.actions + ['my_action'] Alex -- "I disapprove of what you say, but I will defend to the death your right to say it." --Voltaire "The people's good is the highest law."--Cicero --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
