Bug: "Jump to page" jumps to WRONG page

[FORUM_TEST_2-19-14]

Problem: The "Jump to page" option/form does not jump to the page you tell it to, it jumps to WRONG page. You tell it page 150, it goes to page 101.

This can be reproduced on ANY page with a "Jump to page" option/form, but we're gonna use the Lazor System thread for the example...

Steps to reproduce...

1. Go to the Lazor System thread
   
2. Click Page 1 of XXX to open the drop down form (currently it says "Page 1 of 153", but, of course, that will change).
   
3. In the Jump to page box, type 150 (or any other number)
   
4. Press Enter or click Go

Actual Results...

• You will end up on page 101

Expected Results...

• You should end up on page 150 (or whatever number you entered)

I think I see the problem...

The form's action attribute is set to...

<form action="threads/9923-0-23-Lazor-System-v32b-%28Dec-19%29/page101" method="get" class="...">

...so the form submits to...

http://forum.kerbalspaceprogram.com/threads/9923-0-23-Lazor-System-v32b-%28Dec-19%29/

page101

?t=9923&page=150

...which responds with...

HTTP/1.1 301 Moved Permanently

...which ends up redirecting to...

http://forum.kerbalspaceprogram.com/threads/9923-0-23-Lazor-System-v32b-(Dec-19

)/

page101

...thus completing the "taking you to the wrong page" problem.

The fix is simple...

If you change the "form action" to this (removing "/page101" from it)...

<form action="threads/9923-0-23-Lazor-System-v32b-%28Dec-19%29" method="get" class="...">

...or even more simply,

blank it out

(so the form submits to the current page)...

<form action="" method="get" class="...">

...then it all works fine!

Side bug: Searching for "Lazor" or "Lazor System" on the KSP forums DOES NOT produce the correct thread (at least not on page 1 of the results)...I have to Google for "KSP Lazor" or "KSP Lazor System" to find it quicker. This bug might deserve its own topic, but I'm including it here for now.

[vexx32]

Oh ho, well spotted. Very interesting... I wonder how that happened. I'm certain this function worked not a few months back...