Last modified: 2011-03-27 14:44:17 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 T20197, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 18197 - Revert recentchanges limit to 5000 (id.wikipedia)
Revert recentchanges limit to 5000 (id.wikipedia)
Status: RESOLVED WORKSFORME
Product: Wikimedia
Classification: Unclassified
General/Unknown (Other open bugs)
unspecified
All All
: Normal normal with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-03-27 14:16 UTC by Borgx
Modified: 2011-03-27 14:44 UTC (History)
2 users (show)

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


Attachments

Description Borgx 2009-03-27 14:16:06 UTC
For the reason of vandalism patroll, please revert recent changes limit to 5000 on id.wikipedia.
Comment 1 Aryeh Gregor (not reading bugmail, please e-mail directly) 2009-03-27 14:17:55 UTC
This is not currently configurable on a per-wiki basis.  Ideally, we should fix the code so that it doesn't take a ludicrous amount of time to format 5000 rows, and reenable it for everyone . . . or just add paging.
Comment 2 Borgx 2009-03-27 14:52:56 UTC
The current recentchanges url is not consistent with its logic. According to logic, "..&from=20090326145934&limit=500&..." should provide all recent changes started from the older post (20090326145934) and 500 newer post. The current logic is calculated from the newer post (now) and 500 older post, therefore it should be changes to "..&from=now&limit=500&..."  :D. I can live with the 500 limit if you change this sort method. :D
Comment 3 Borgx 2009-06-19 01:17:44 UTC
Anyone. Please dont limit rc to 500. If 5000 is too many, 3000 or 2000 is fine. 500? How can you expect people to monitor vandal with this restriction?
Comment 4 Splarka 2009-06-19 22:39:21 UTC
(In reply to comment #2)
> The current recentchanges url is not consistent with its logic. According to
> logic, "..&from=20090326145934&limit=500&..." should provide all recent changes
> started from the older post (20090326145934) and 500 newer post. The current
> logic is calculated from the newer post (now) and 500 older post, therefore it
> should be changes to "..&from=now&limit=500&..."  :D.

That is bug 18228. Note this is possible with the API, so you can fake it (eg: http://en.wikipedia.org/wiki/User:Splarka/ajaxrecentchanges.js ).
Comment 5 Lejonel 2011-03-27 14:44:17 UTC
Now the maximum limit seems to be 5000. So WORKSFORME (or maybe dupe of bug 18241).

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


Navigation
Links