Last modified: 2008-12-14 15:50:50 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 T18588, the corresponding Phabricator task for complete and up-to-date bug report information.
First Last Prev Next    This bug is not in your last search results.
Bug 16588 - Block expiry time for list=recentchanges
Block expiry time for list=recentchanges
Status: RESOLVED FIXED
Product: MediaWiki
Classification: Unclassified
API (Other open bugs)
unspecified
All All
: Normal enhancement (vote)
: ---
Assigned To: Roan Kattouw
:
Depends on:
Blocks:
  Show dependency tree / graph
 
Reported: 2008-12-07 23:07 UTC by Gurch
Modified: 2008-12-14 15:50 UTC (History)
3 users (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Gurch 2008-12-07 23:07:20 UTC 
This is essentially the same thing as bug 16541. Apologies for not thinking to mention it then.

Block options are represented in list=logevents with something like the following:

<block flags="anononly,nocreate" duration="1 month" />

Bug 16541 added an 'expiry' parameter. The same construct appears for blocks in list=recentchanges as well, so the 'expiry' parameter should be added there too for consistency.

Thanks :)
Comment 1 Roan Kattouw 2008-12-14 15:50:50 UTC 
It was already there, you just had to set rcprop=loginfo. Note that the feature was broken (expiry was calculated relative to the current time rather than the block timestamp), but that was fixed in r44583.
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.

Navigation
Links