| Etonkovidova | |
| Apr 4 2017, 11:25 PM |
| F16463542: wrong-time-cx-in-progress.PNG | |
| Mar 30 2018, 12:12 PM |
| F15437169: Screen Shot 2018-03-14 at 00.13.53.png | |
| Mar 14 2018, 10:33 PM |
| F7224644: Screen Shot 2017-04-04 at 4.09.03 PM.png | |
| Apr 4 2017, 11:25 PM |
3, Changing Preferences-Appearance -Time offset does not affect the translation timestamp.
Note: updates on articles or notifications provide relative time - 2 hours ago, 3,min ago. That relative timestamp is calculated against user local time.
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| Fix "last update" timestamp for translations | mediawiki/extensions/ContentTranslation | master | +1 -1 |
Seeing the same on Special:ContentTranslation after I followed a grey interwiki link for "espagnol" on English Wikipedia:
For what its worth, both my enwiki and eswiki account use UTC as timezone in Preferences/Appearances, and both wikis also have UTC as default timezone. But I was viewing this on a browser with GMT-0700 (PDT) as operating system timezone.
That seems to be a timezone issue then. Have to see if this can be fixed client side, e.g. https://momentjs.com/docs/#/parsing/utc/
moment( translation.lastUpdateTimestamp, 'YYYYMMDDHHmmss Z' ).fromNow()
But input is like 20171116080713.
Should likely be moment.utc( translation.lastUpdateTimestamp, 'YYYYMMDDHHmmss' ).local().fromNow()
Here is another example of fresh in-progress translation showing wrong timestamp. Seems like confirmation that problem lies in timezone calculations, cause I was in CEST (UTC+2) when this happened.
Change 445043 had a related patch set uploaded (by Petar.petkovic; owner: Petar.petkovic):
[mediawiki/extensions/ContentTranslation@master] Fix "last update" timestamp for translations
Change 445043 merged by jenkins-bot:
[mediawiki/extensions/ContentTranslation@master] Fix "last update" timestamp for translations