Last modified: 2008-03-15 03:10:26 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 10913 - High values of "offset" parameter in logs don't work
High values of "offset" parameter in logs don't work
Status: RESOLVED DUPLICATE of bug 5446
Product: MediaWiki
Classification: Unclassified
Special pages (Other open bugs)
All All
: Normal minor (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on: 10932
  Show dependency treegraph
Reported: 2007-08-14 07:07 UTC by Mike.Rosoft
Modified: 2008-03-15 03:10 UTC (History)
3 users (show)

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


Description Mike.Rosoft 2007-08-14 07:07:48 UTC
I have been looking through the user creation log in order to discover possible sockpuppets of a vandal I have blocked, and discovered that I can't go more than one day into the past: offset values over 10000 don't work; instead, clicking on "next 500" repeats the same page. (Artifically changing "limit=500" to "limit=5000" in the URL does display more users, so this can't be caused by a software limitation that older users are no longer in the database.)

To reproduce:
1) View any log with over 10000 entries. Example: - log of my admin actions.
2) Add (or replace) "&offset=10000" in the URL (or, if you have a lot of free time, go to that page manually by repeatedly clicking on "next 500"). Example:
3) Now click on "next 50" (or "next 500", etc.) link; it'll display the same page instead of going further into the past.

Switching from Mozilla Firefox to Internet Explorer made no difference, so it can't be a browser bug either.

Mike Rosoft
Comment 1 Aaron Schulz 2007-08-14 07:09:06 UTC
This is due to $wgMiserMode. The way logs page is not efficient, and high values use up a lot of resources to query. I suppose timestamp paging is in order.
Comment 2 Robert Rohde 2007-11-03 20:41:59 UTC
I encountered this today, and would encourage someone to fix it.  I was trying to review someone's deletion log and 10000 deletions only got me back to this September, which wasn't long enough to get at the question I wanted.  (Of course it must be rare to have 10,000 deletions in 6 weeks, but it apparently does happen.)
Comment 3 Aaron Schulz 2007-11-03 20:53:54 UTC
Also, timestamp offset actually is useful when trying to link pages to it, whereas the links for the current method are unstable.
Comment 4 Korg 2008-03-15 03:10:26 UTC
See bug 5446: Allow timestamps to be used as offsets in log pages

*** This bug has been marked as a duplicate of bug 5446 ***

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