changeset 12525 added code that would prematurely exit from the
reponse_action method of ModelAdmin if it detected that the "Go"
button was not pressed.  However this meant the "delete selected"
action would not be performed because the view was being posted to
from the confirmation screen.

I've opened ticket #12973 and included a patch that that gets things
working again.  But in a way I think there is some more design
thinking needed here for 1.3 in terms of how an action follows
through.  The number of code paths going through the changelist view
seems a little convoluted.  It would make sense if there was some
design pattern that allowed an action to be more self contained and
able to perform its action independent from the changelist view.

-Preston

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-develop...@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Reply via email to