Last modified: 2011-03-13 18:06:24 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 T6499, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 4499 - date depending templates
date depending templates
Product: MediaWiki
Classification: Unclassified
Templates (Other open bugs)
All All
: Lowest normal with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on: 366
  Show dependency treegraph
Reported: 2006-01-05 23:58 UTC by Effeietsanders
Modified: 2011-03-13 18:06 UTC (History)
0 users

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


Description Effeietsanders 2006-01-05 23:58:56 UTC
A lot of date-depending templates are availeble in the software. Great things. But when 
used, like "What happened on {{CURRENTDATE}}"-template in the mainpage, it changes not 
at the moment it is 00.00h in Netherlands and Belgium, but some hour(s) later. Can it 
be made possible that sysops can somewhere define the moment when the next day starts? 
(relating to the servertime or UTC) Or even better: That these templates will depend on 
the time at the PC where they are watched. That way someone in Thailand will see sooner 
the next day's featured article then another user, but that should be, because for him 
it ís the next day. 
The first thing would be great, the second fantastic. Greetings nl:Effeietsanders
Comment 1 Ævar Arnfjörð Bjarmason 2006-01-07 04:37:45 UTC
RESOLVED WONTFIX, use the wiki timezone setting to set it globally, we don't
render those variables depending on the user timezone setting for a good reason,
it would severely impact caching.
Comment 2 Effeietsanders 2006-02-02 21:49:15 UTC
*** This bug has been marked as a duplicate from bug 366 ***

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