Last modified: 2012-08-24 00:28:00 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 4744 - Error in editing timestamp?
Error in editing timestamp?
Status: RESOLVED DUPLICATE of bug 2219
Product: Wikimedia
Classification: Unclassified
General/Unknown (Other open bugs)
All All
: Lowest minor (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
Blocks: 16660
  Show dependency treegraph
Reported: 2006-01-24 16:20 UTC by Edmund Teo
Modified: 2012-08-24 00:28 UTC (History)
2 users (show)

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


Description Edmund Teo 2006-01-24 16:20:50 UTC
Not a critical issue, but when someone told me my first edit was on 4 January 2003, 
when I know it was actually way beyond that, I checked my own contribution history at 
title=Special:Contributions&target=Huaiwei&offset=20041111213536&limit=200] and 
discovered the appearance of an edit which was supposed to be timestamped as Mar 10, 
2005 appearing instead at the above erroneous date. I am not sure if this problem 
affects other edits across wikipedia, so I am not sure what is the severity of this 
issue. Do check it out if you can! Thanks! :D
Comment 1 Brion Vibber 2006-01-24 19:33:03 UTC
This was an instance in which servers with bad clocks were briefly
put in service before being corrected. There is no way to determine
the "real" timestamp after the fact, so "correcting" it is not
really clear.

There is probably already a bug report about this.
Comment 2 Graham87 2012-08-24 00:28:00 UTC

*** This bug has been marked as a duplicate of bug 2219 ***

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