tags:

views:

543

answers:

3

I want to emulate the delete confirmation page behavior before saving certain models in the admin. In my case if I change one object, certain others should be deleted as they depend upon the object's now out-of-date state.

I understand where to implement the actual cascaded updates (inside the parent model's save method), but I don't see a quick way to ask the user for confirmation (and then rollback if they decide not to save). I suppose I could implement some weird confirmation logic directly inside the save method (sort of a two phase save) but that seems...ugly.

Any thoughts, even general pointers into the django codebase?

Thanks!

+1  A: 

I'm by no means a Django expert, so this answer might misguide you.

Start looking somewhere around django.contrib.admin.options.ModelAdmin, especially render_change_form and response_change. I guess you would need to subclass ModelAdmin for your model and provide required behavior around those methods.

Tomo
+1  A: 

You could overload the get_form method of your model admin and add an extra checkbox to the generated form that has to be ticket. Alternatively you can override change_view and intercept the request.

Armin Ronacher
A: 

Have you considered overriding the administrative templates for the models in question? This link provides an excellent overview of the process. In this particular situation, having a finer-grained level of control may be the best way to achieve the desired result.

Huuuze
I've already overloaded parts of the change_form, but this particular behavior seems to be hard coded into the core (at least the post save redirect url). Perhaps I can shadow the post save confirmation url and do something funky there though?
Jacob Rigby