Last modified: 2013-07-11 08:54:18 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 T53128, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 51128 - Start date and age displays incorrent "ago" value
Start date and age displays incorrent "ago" value
Status: RESOLVED DUPLICATE of bug 49803
Product: MediaWiki
Classification: Unclassified
Parser (Other open bugs)
unspecified
All All
: Unprioritized normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-07-10 18:24 UTC by ffoxin
Modified: 2013-07-11 08:54 UTC (History)
2 users (show)

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


Attachments

Description ffoxin 2013-07-10 18:24:42 UTC
Structure 'infobox software' has field 'latest release date'. In HTML it looks like 'July 1, 2013; 3 days ago'. The 'ago' value calculating from the last page modification date, not from the current date (as it should be). If I use previews while editing - the 'ago' value is correct.

Ex.:
article:
http://en.wikipedia.org/wiki/Boost_(C%2B%2B_libraries)

product latest release date:
'July 1, 2013'

article last modified date:
'4 July 2013'

displayed 'ago' value:
'3 days ago'

the value should be displayed (for 2013-07-10):
'9 days ago'
Comment 1 Bartosz Dziewoński 2013-07-10 18:26:18 UTC
This is fixed when you purge the page. Unfortunately Wikipedia pages are heavily cached for performance and this is the result.
Comment 2 Bartosz Dziewoński 2013-07-10 18:31:54 UTC
Or maybe usage of such time-dependent output should make the cache expiration time lower. Reopening for now.
Comment 3 Andre Klapper 2013-07-11 08:54:18 UTC
Hi ffoxin. Thanks for taking the time to report this!
This particular problem has already been reported into our bug tracking system, but please feel free to report any further issues you find.

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

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


Navigation
Links