Special:WhatLinksHere form broken
Closed, ResolvedPublic



When we go to [[Special:WhatLinksHere/Some page]], and click at some of the "limit links" in the following line:
View (previous 50) (next 50) (20 | 50 | 100 | 250 | 500)
for example, the "20", the target of ALL the other links changes to something link
wgServer + wgScript + '?title=Special:Whatlinkshere/Some_page&limit=20

This way, the links does not works as expected anymore: instead of a list of 50, 100, 250 or 500 items, we would get always a list of 20 elements.

Does anybody knows what is wrong?

Version: 1.16.x
Severity: normal
URL: http://en.wikipedia.org/w/index.php?title=Special:WhatLinksHere/Template:!&limit=20


bzimport set Reference to bz19236.
bzimport added a subscriber: Unknown Object (MLST).
He7d3r created this task.Jun 16 2009, 2:23 PM

Confirmed this, see URL

  • Bug 19238 has been marked as a duplicate of this bug. ***

Been staring at this for a pretty long while. I'm pretty certain the back link was already broken in r49492. The second forward link broke after that. Taking it off my name again, as I am not able to resolve. Reverting back to r49492 will not resolve it completely. CC-ing ^demon.

alejrb wrote:

This also applies for the 'Hide _____' links - once hidden, clicking 'Show ______' doesn't remove the '&hideredirs=1' parameter from the URL.

  • Bug 19251 has been marked as a duplicate of this bug. ***

Partially fixed in r52023. I believe all that's broken now are the "previous" links.

The "previous" links appear to be broken since at least as long ago as 1.13.3 (the oldest version I have readily available), possibly since the current paging system for it was introduced. It goes back one page, but after that, it doesn't know what to use for the "from" query parameter, as that has to be filled in with where it should start enumerating from on the next page, which it can't know unless its passed in the URL or it does another query.

happy.melon.wiki wrote:

This is just asking to use Pager, surely?

  • This bug has been marked as a duplicate of bug 9487 ***

Add Comment