Since, oh, I dunno, two days or so, I've been experiencing this strange quirk:
Clicking on the last page number of a thread leads to an empty page - so clicking on the "3" of a "1 2 3" thread leads to an empty page. That's because the actual thread is only 2 pages long. Seems to me the routine printing pagenums is now generating N+1 pages instead of N (no, I haven't bothered checking the deal with one-page threads...
)
Anyhow, this does not affect the longer threads that get the "Last page" moniker - those work correctly.
Exemples: In this forum, I'm current getting this bug for threads like "Suggestions as new flags" and "MSN Support".
Clicking on the last page number of a thread leads to an empty page - so clicking on the "3" of a "1 2 3" thread leads to an empty page. That's because the actual thread is only 2 pages long. Seems to me the routine printing pagenums is now generating N+1 pages instead of N (no, I haven't bothered checking the deal with one-page threads...
)Anyhow, this does not affect the longer threads that get the "Last page" moniker - those work correctly.
Exemples: In this forum, I'm current getting this bug for threads like "Suggestions as new flags" and "MSN Support".
Guys, 2+2=4… the whole page length thing is busted. It now defaults to 30 instead of 25, and no other pagelengths work properly. However, if you have your option set to something other than 30 the thread directory still calculates the page numbers according to your option.
Outrageous!
Comment