Last modified: 2008-08-12 20:07:58 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 T17143, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 15143 - Limit large range checks by date rather than edit count
Limit large range checks by date rather than edit count
Status: RESOLVED DUPLICATE of bug 14908
Product: MediaWiki extensions
Classification: Unclassified
CheckUser (Other open bugs)
unspecified
All All
: Normal enhancement (vote)
: ---
Assigned To: Aaron Schulz
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-08-12 19:32 UTC by Thatcher
Modified: 2008-08-12 20:07 UTC (History)
0 users

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


Attachments

Description Thatcher 2008-08-12 19:32:47 UTC
I frequently find myself trying to check ranges looking for edits and sleeper account creations by vandals and banned users on highly dynamic ISPs (or who forcibly reset their connection frequently). If there are more than 5000 edits in the database, the system returns an error message with a partial list of IPs, and it is necessary to try progressively smaller ranges (and more of them) to do a complete search.  However, I usually don't need to see all the edits from the checkuser table, the edits from the last 5 or 10 days are usually sufficient to find recent sleepers or other activity.  I propose that when a range check returns the "exceeds 5000 edits" error message, the system should ask, "would you like to limit your search to the last X days and recheck?" where X could be a dropdown box (say, 1, 3, 5, 10 and 30 days) or free-form entry.
Comment 1 Aaron Schulz 2008-08-12 20:07:58 UTC

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

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


Navigation
Links