Last modified: 2014-01-02 06:35:15 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 T61137, the corresponding Phabricator task for complete and up-to-date bug report information.
First Last Prev Next    This bug is not in your last search results.
Bug 59137 - Parser function {{#time}} yielding incorrect month
Parser function {{#time}} yielding incorrect month
Status: RESOLVED DUPLICATE of bug 50477
Product: MediaWiki extensions
Classification: Unclassified
ParserFunctions (Other open bugs)
unspecified
All All
: Unprioritized normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency tree / graph
 
Reported: 2013-12-30 20:25 UTC by Matthew "Shirik" Del Buono
Modified: 2014-01-02 06:35 UTC (History)
4 users (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Matthew "Shirik" Del Buono 2013-12-30 20:25:01 UTC 
Presently on Wikipedia parser function {{#time}} is yielding incorrect results in certain circumstances. I have created a minimal reproduction with the following code:

{{#time:F|February}}


This results in "March" currently.

I suspect this might be related to the exact time this is showing up (the end of the year) and an incorrect calculation, because nobody has noticed this until now.
Comment 1 db [inactive,noenotif] 2013-12-30 20:38:18 UTC 
This is always happen between 29 and 31 of a month for February and for other months on the 31, because setting the 30 of a month to February results in the 30 of February which is the 2 of March

small test case:
{{#time:d F|February}}

gives:
02 March
Comment 2 Jesús Martínez Novo (Ciencia Al Poder) 2013-12-30 20:44:11 UTC 

*** This bug has been marked as a duplicate of bug 50477 ***
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.

Navigation
Links