Last modified: 2010-05-15 15:48:34 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 T11299, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 9299 - Double timezone addition in timestamp in Recent Changes with Postgresql
Double timezone addition in timestamp in Recent Changes with Postgresql
Status: RESOLVED FIXED
Product: MediaWiki
Classification: Unclassified
Database (Other open bugs)
1.9.x
PC All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks: postgres
  Show dependency treegraph
 
Reported: 2007-03-15 18:27 UTC by Olleg Samoylov
Modified: 2010-05-15 15:48 UTC (History)
0 users

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


Attachments

Description Olleg Samoylov 2007-03-15 18:27:45 UTC
*  MediaWiki: 1.9.3
* PHP: 5.2.0-8+etch1 (apache2handler)
* PostgreSQL: PostgreSQL 8.1.8 on x86_64-pc-linux-gnu, compiled by GCC cc (GCC)
4.1.2 20061115 (prerelease) (Debian 4.1.1-21)

I have timezone +3 and after it's installation I see correct local time in user
preferences and in "recent changes" at lines "Below are the last 50 changes in
the last 7 days, as of 21:17, 15 March 2007" and "Show new changes starting from
21:17, 15 March 2007".

But in lines per changes timestamp is wrong and looked like in +6 timezone:
"00:22 Main Page (diff; hist) . .  (+2) . . Olleg (Talk | contribs | block)
(unsuccessfully)". If I remove timezone from user preferences, timestamp in
recent changes will have +3 shift.
Comment 1 Greg Sabino Mullane 2007-03-26 01:06:03 UTC
Fixed in r20688. It should be easily back-patchable if you desire.
Comment 2 Greg Sabino Mullane 2007-03-29 12:27:13 UTC
Fixed again in r20786 and r20776.

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


Navigation
Links