Sorry for pushing about this right after the feature was committed,
but I have a problem with the way the feature was done.
Specifically, I don't like the fact that "delete selected objects" is
enabled by default. Although I'm glad to have the bulk edit feature,
none of my models are designed at
Le 24 mars 09 à 09:36, Elliott a écrit :
> Given these reasons it only makes sense to me to leave delete off by
> default and provide an easy way to enable it, both globally or for
> each model.
I agree with Elliott, admin actions are great and we were all
impatients to see it in action - no p
It would seem to me that the method we're using for context_processors
might be a good one. A list of things available by default, then you
can override it in settings.py in order to provide different ones or
remove some of the defaults. I think it could very well. Thoughts?
-justin
--
Justin
Am 24.03.2009 um 10:41 schrieb David Larlet:
>
>
> Le 24 mars 09 à 09:36, Elliott a écrit :
>> Given these reasons it only makes sense to me to leave delete off by
>> default and provide an easy way to enable it, both globally or for
>> each model.
>
> I agree with Elliott, admin actions are gre
If there's no objections by tomorrow I'm going to reopen http://
code.djangoproject.com/ticket/10596
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to djan
Don't forget, a lot of people also use a custom method of deletion on
their models; they may not want to remove a record from the database,
but instead set a 'deleted' flag; having deletion also there by
default means they would have two deletion actions. I'd say that
deletion should be there if n
On Sat, Apr 4, 2009 at 7:10 PM, kmike 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
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) ena
It's a very good opinion. I don't want any actions from parent model
admin class too.
Maybe it is worth opening a dedicated ticket?
On 5 апр, 05:56, Alex Gaynor wrote:
> On Sat, Apr 4, 2009 at 7:10 PM, kmike wrote:
>
> > Totally agree, bulk delete shouldn't be enabled by default.
>
> > One more