Last modified: 2012-05-03 02:42:43 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 34835 - watchlist shows times in UTC
watchlist shows times in UTC
Product: MediaWiki
Classification: Unclassified
Watchlist (Other open bugs)
All All
: Normal normal (vote)
: 1.19.0 release
Assigned To: Antoine "hashar" Musso (WMF)
Depends on:
Blocks: 31217
  Show dependency treegraph
Reported: 2012-03-01 03:20 UTC by Mark A. Hershberger
Modified: 2012-05-03 02:42 UTC (History)
1 user (show)

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


Description Mark A. Hershberger 2012-03-01 03:20:51 UTC
From :

While the times in the list itself is fine, the part in the box (following "in the last 72 hours, as of") shows UTC time now. I have to hope this is a bug, not a feature.
Comment 1 Antoine "hashar" Musso (WMF) 2012-03-01 11:59:04 UTC
The relevant message is wlnote from includes/specials/SpecialWatchlist.php . It was changed by r111882 to use the user date and time. Now looks like:

$wlInfo = $this->msg( 'wlnote' )
    ->numParams( $numRows, round( $values['days'] * 24 ) )
        $lang->userDate( $timestamp, $user ),
        $lang->userTime( $timestamp, $user )
    )->parse() . '<br />';
Comment 2 Antoine "hashar" Musso (WMF) 2012-03-01 12:01:48 UTC
And the bug is a regression from 1.18.
Comment 3 Antoine "hashar" Musso (WMF) 2012-03-01 12:05:59 UTC
Merged above fix (r111882):

In REL1_19 with r112798
In 1.19wmf1 with r112797

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