Incorrect query string built by utils.next_redirect if next parameter already contains a query string

[benbest86]

In the comments app, views.utils.next_redirect appends a '?' and query string key/value pairs to the next parameter regardless of whether the next parameter already has a query string appended.

e.g. if next = /path/to/url?key=value then next_redirect redirects to /path/to/url/?key=value?c=13 or something along those lines.
Simple patch is attached, this is my first contribution, so apologies for any missed protocol...

Thanks,

Ben

[Jacob]

(In [10424]) Fixed #10585: comment redirects built from the next parameter now work correctly when next already contains a query string.

[Jacob]

(In [10425]) [1.0.X] Fixed #10585: comment redirects built from the next parameter now work correctly when next already contains a query string. Backport of r10424 from trunk.

[Jacob]

Milestone 1.1 deleted