Last modified: 2009-01-03 14:19:59 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 936 - List revisions created in a particular timeframe
List revisions created in a particular timeframe
Status: RESOLVED FIXED
Product: MediaWiki
Classification: Unclassified
General/Unknown (Other open bugs)
unspecified
All All
: Normal enhancement with 3 votes (vote)
: ---
Assigned To: Nobody - You can work on this!
:
: 10328 (view as bug list)
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2004-11-23 21:41 UTC by Puc conDoin
Modified: 2009-01-03 14:19 UTC (History)
3 users (show)

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


Attachments

Description Puc conDoin 2004-11-23 21:41:34 UTC
It would be nice to have a feature where you can enter a certain date, to get
all (anonymous) changes of that one day. Like recent changes does, but better.

The problem is the limit of 5000 changes to be shown on the recent changes page.
And, when moderators didn't have time to check changes on a certain date, they
won't be able to get this list afterwards, because there are too many changes
after that period.

The best way I see it, is to have the option to select a date (23 july 2004),
and to select a period on that day (12:30 - 22:15). The list that has to be
shown can have the same options as recent changes does.

All the historical information is in the database, so why don't we make better
use of it? I think this feature would'nt stress the database so mucht like
recent changes seems to do.
Comment 1 Rob Church 2007-06-21 20:37:54 UTC
*** Bug 10328 has been marked as a duplicate of this bug. ***
Comment 2 Roan Kattouw 2007-06-21 21:03:32 UTC
Shouldn't be hard to do. Look at ApiQueryRecentchanges.php's rcbegin and rcend parameters.

> I think this feature would'nt stress the database so mucht like
> recent changes seems to do.
Actually, it stresses the DB just a little more, but not noticeably.

Comment 3 Aaron Schulz 2009-01-03 14:19:59 UTC
This can be done with api.php

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


Navigation
Links