#8968: No way to utilize `next` parameter to redirect after comment deletion ----------------------------------------------+----------------------------- Reporter: Dzhus | Owner: kkubasik Status: closed | Milestone: 1.1 Component: django.contrib.comments | Version: 1.0 Resolution: wontfix | Keywords: comments Stage: Accepted | Has_patch: 1 Needs_docs: 0 | Needs_tests: 0 Needs_better_patch: 0 | ----------------------------------------------+----------------------------- Changes (by jacob):
* status: new => closed * resolution: => wontfix Comment: There isn't a bug here. The `next` param is meant for people who want to wrap one of these views either with a custom URLconf like {{{ (r'^flag/(\d+)/$', flag, {'next': '/I/am/done/'}) }}} or with a function that wraps the view. If it's not given, the next param will be pulled out of `GET` or `POST` (depending), so you can use an `<input type=hidden name=next>` in your HTML. -- Ticket URL: <http://code.djangoproject.com/ticket/8968#comment:9> Django <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 django-updates@googlegroups.com To unsubscribe from this group, send email to django-updates+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-updates?hl=en -~----------~----~----~----~------~----~------~--~---