Last modified: 2012-05-03 02:42:47 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 34736 - empty limit on special pages causes navigation issues
empty limit on special pages causes navigation issues
Product: MediaWiki
Classification: Unclassified
Special pages (Other open bugs)
All All
: High normal (vote)
: 1.19.0 release
Assigned To: Antoine "hashar" Musso (WMF)
: need-unittest
Depends on:
Blocks: 31217
  Show dependency treegraph
Reported: 2012-02-26 16:16 UTC by Orashmatash
Modified: 2012-05-03 02:42 UTC (History)
2 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Description Orashmatash 2012-02-26 16:16:29 UTC
When on the default 50 per-page layout of Special:NewPages on simple.wikipedia, when one clicks "older 50", the entire page messes up and shows as if there is nothing there, and in place of "newer 50" (which should be there), there is "newer 0".
Comment 1 Antoine "hashar" Musso (WMF) 2012-02-27 09:45:39 UTC
Step to reproduce:

Look at the URL for the (older 50)  link, it has a &limit=  parameter. Click on it: output screwed :-]
Comment 2 Antoine "hashar" Musso (WMF) 2012-02-27 10:02:31 UTC
caused by r105809 which changed wfArrayToCGI() and wfCgiToArray()
Comment 3 Antoine "hashar" Musso (WMF) 2012-02-27 10:17:16 UTC
fixed by r112474
Comment 4 Antoine "hashar" Musso (WMF) 2012-02-27 10:25:09 UTC
merged to 1.19wmf1 with r112475 and website updated! Seems good now :-]

Note You need to log in before you can comment on or make changes to this bug.