#8968: No way to utilize `next` parameter to redirect after comment deletion --------------------------+------------------------------------------------- Reporter: Dzhus | Owner: nobody Status: new | Milestone: Component: Contrib apps | Version: 1.0 Keywords: comments | Stage: Unreviewed Has_patch: 0 | --------------------------+------------------------------------------------- How is default «delete comment» view from new comments system meant to get `next` argument (see `contrib/comments/views/moderation.py`)?
I think good way to do it is to support `next` GET request parameter, so that one could use `/delete/123/?next=/blog/entry/bla-blah` as a link to comment deletion page in order to redirect to page other than default «deleted» view after actually removing the comment. This works with «post comment» because `next_redirect` in `post_comment` function can see the `next` POST parameter in `data`. This does not work with «delete comment» because confirmation page is rendered first with `next="None"` in confirmation form. -- Ticket URL: <http://code.djangoproject.com/ticket/8968> Django Code <http://code.djangoproject.com/> The web framework for perfectionists with deadlines --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django updates" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-updates?hl=en -~----------~----~----~----~------~----~------~--~---
