Last modified: 2012-11-17 15:32:35 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T42080, the corresponding Phabricator task for complete and up-to-date bug report information.
First Last Prev Next    This bug is not in your last search results.
Bug 40080 - Count error on paging (&limit= parameter in URL ignored)
Count error on paging (&limit= parameter in URL ignored)
Status: RESOLVED WORKSFORME
Product: Wikimedia
Classification: Unclassified
General/Unknown (Other open bugs)
unspecified
All All
: Unprioritized normal with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency tree / graph
 
Reported: 2012-09-07 13:44 UTC by bennylin
Modified: 2012-11-17 15:32 UTC (History)
1 user (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description bennylin 2012-09-07 13:44:56 UTC 
http://commons.wikimedia.org/w/index.php?title=Special:Contributions&limit=20&contribs=user&target=Bennylin&uselang=id

http://commons.wikimedia.org/w/index.php?title=Special:Contributions&limit=500&contribs=user&target=Bennylin&uselang=id

The pagination says "Lihat (1 lebih baru | 1 lebih lama)" (correspond to View (newer 1 | older 1) -- didn't matter the limit either 20 or 500). Previously it didn't behave that way. I've reported it on https://translatewiki.net/wiki/Portal_talk:Id too, but I don't think the error is from the l10n.
Comment 1 Andre Klapper 2012-11-17 14:20:27 UTC 
Hi bennylin,
cannot reproduce the problem with the examples given - the limit= parameter in the URL is respected and it shows either 20 or 500, as expected. 
Closing this report as WORKSFORME but please reopen if this happens again.
Comment 2 bennylin 2012-11-17 15:32:35 UTC 
It's been fixed (still don't know what caused it on the first place). Sorry didn't include screenshot attachment. Thanks for closing the bug.
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.

Navigation
Links