Scenario:
A node with comments that span a more than 1 page. Oldest comments displayed first.

Bug:
After submitting a comment, the user is returned to page 0 instead of the page where their comment is (last page).

The resulting URL after submitting a comment DOES contain the target comment number, however it does not exist on the first page.

Comments

aaron’s picture

aaron commented

this bug also exists for the permalinks for existing comments on pages other than 0. trickiness would be adjusting for how many comments a particular user lists on a page, when allowed to be configurable.

chx suggested a js approach: something like js redirect from node/nid/cid to node/nid?page=p#comment-cid

cburschka’s picture

cburschka
they
commented

Can't the form submission hander (which I presume does the redirection through its return value, though I haven't checked) read the comments-per-page configuration value to determine the right page? I'm not convinced this requires Javascript...

cburschka’s picture

cburschka
they
commented

Oops. I was close to submitting a very simple patch and then realized that this is a far more complex issue than it appears to be, since the new comment need not be on the last page. For example, you can't simply assume that the comments are ordered oldest first - and thanks to the nightmare that are these threaded discussions (ugh), you can't even assume that the latest comment is anywhere near the first or last page.

dpearcefl’s picture

dpearcefl commented
Status: Active » Closed (won't fix)

Considering the age of this issue with no responses and that D5 is unsupported, I am closing this issue.