| commit | 8b2d0fe993ac094aac75acc8fc8b21ca1df43710 | |
| author | Magnus Hagander <magnus@hagander.net> | |
| Wed, 20 Dec 2017 12:58:17 +0000 (20 13:58 +0100) | ||
| committer | Magnus Hagander <magnus@hagander.net> | |
| Wed, 20 Dec 2017 12:58:17 +0000 (20 13:58 +0100) | ||
| tree | e1bbbb9a4bffb3c50b2bfbbd9073d540d453555e | treesnapshot (tar.gz zip) |
| parent | 18ffd5eb3f23571fea4dc075cab9e6a4bfb059b5 | commitdiff |
Remove support for "remove after notify" on moderation
This broke when we had ManyToMany relations on a record. We didn't use
to have that, but with tags for news we now do. With this change, the
"reject with a notice" becomes a two step operation, the first one
adding the notification and the second one doing the removal. That'll
have to do for now, and at some point in the future we may create a
completely separate (non /admin/) workflow for moderation and fix it
that way.
This broke when we had ManyToMany relations on a record. We didn't use
to have that, but with tags for news we now do. With this change, the
"reject with a notice" becomes a two step operation, the first one
adding the notification and the second one doing the removal. That'll
have to do for now, and at some point in the future we may create a
completely separate (non /admin/) workflow for moderation and fix it
that way.
| pgweb/util/admin.py | diffblobblamehistory | |
| templates/admin/change_form_pgweb.html | diffblobblamehistory |