tickets: 5382
This data as json
| id | created | changetime | last_pulled_from_trac | stage | status | component | type | severity | version | resolution | summary | description | owner | reporter | keywords | easy | has_patch | needs_better_patch | needs_tests | needs_docs | ui_ux |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 5382 | 2007-09-10 13:07:26 | 2007-09-10 14:39:21 | 2022-03-06 03:34:14.262130 | Unreviewed | closed | Generic views | dev | wontfix | create_update.delete_object always needs a confirmation page | I've found one thing annoying about delete_object() view. In my application I prefer to use HREFs (as opposed to forms) for object deletion, together with JavaScript-based confirmation dialogs. This makes delete_object() useless for me, as I want it to delete the object upon GET request, without aby further confirmation page. Could it be possible to add additional param like no_confirmation (with False as default for backward compatibility) ? Changing {{{ if request.method == 'POST': }}} to {{{ if no_confirmation or request.method == 'POST': }}} would do the trick then. | nobody | czajnik@czajsoft.pl | delete_object | 0 | 0 | 0 | 0 | 0 | 0 |