Last modified: 2014-06-05 10:29:16 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 1870 - SpecialRecentChanges: Support both 'from' and 'start' in the user interface
SpecialRecentChanges: Support both 'from' and 'start' in the user interface
Status: NEW
Product: MediaWiki
Classification: Unclassified
Recent changes (Other open bugs)
unspecified
All All
: Low enhancement with 2 votes (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2005-04-11 02:40 UTC by SJ
Modified: 2014-06-05 10:29 UTC (History)
2 users (show)

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


Attachments

Description SJ 2005-04-11 02:40:27 UTC
I'd like to see all changes from March 24.  AFAIK, there's no way to do that
with the current installation.  I would love to see a patch that fixes this,
even if it ends up being slow and is turned off for large sites.

(I'd also like to be able to search through pages by date, either of creation or
last edit, but that's a bigger request for another time, once we are storing
more metadata about articles.)
Comment 1 Rob Church 2006-04-22 02:03:10 UTC
I'd suggest an extension which allowed querying of the revision table for edits
made matching a particular timestamp. As noted, this would be fairly expensive.
Comment 2 Purodha Blissenbach 2006-05-03 14:34:48 UTC
I'd suggest a similar extension for revision tables AND all kinds of logs.
If that helps cuts expenses, I'd accept some fuzzyness of the selection, i.e. e.g. List 100 continous records 
which include March 24, 2001 high noon, upon a query for March 24, 2001, no matter what the 1st and last ones 
are. I'd also suggest to be able to step back and forth in time, pagewise.
I do not expect this featue to be used much.
If turning it off would have to be an option, I'd suggest to leave it available to admins, or something 
similar.
Comment 3 Siebrand Mazeland 2009-02-02 12:43:16 UTC
Changed component to "RecentChanges"
Comment 4 SJ 2009-04-18 21:15:25 UTC
Purodha's comment is well placed.  This is something I really want to see on a toolserver or some other offline processor-heavy support service.  
Comment 5 SJ 2009-04-18 22:51:28 UTC
I can nowadays set an offset= parameter for the history of a single page, but nothing more.  RC won't let me set an offset in that way - while I can set a 'from=' I can't set a 'to=' in the same fashion.
Comment 6 Krinkle 2014-06-05 09:25:52 UTC
The backend already supports both 'start' and 'from' timestamps (for example when using api.php with query list=recentchanges).

This is just a matter of exposing it in the UI.

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


Navigation
Links