Closed (fixed)
Project:
Date
Version:
5.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
22 Mar 2007 at 12:04 UTC
Updated:
16 Aug 2007 at 01:48 UTC
If 'Time zone handling' is 'Date's time zone' it should be great if date/time was converted to user's timezone and viewed untouched for anonymous users.
Here's the patch
| Comment | File | Size | Author |
|---|---|---|---|
| data_user_zone.patch | 666 bytes | scoonz |
Comments
Comment #1
scoonz commentedI'm sorry, this patch works fine only for such case:
anonymous user creates node with CCK date field and authenticated user views it.
When authenticated user creates node, the date's zone is ignored - user's zone is used instead.
Comment #2
karens commentedThe idea behind date-specific timezones is that the date has a timezone of its own and should be displayed using that timezone. The use case is a site that shows real world events that take place in various timezones. For instance, a concert that starts at 8pm Eastern Standard Time would always be displayed that way because that's what time it will take place for the people who are actually there.
Currently there is no option to show dates in the user's timezone because we don't know reliably what timezone the user is in. We might know their offset, but there are several timezones that could share that offset. I see you came up with an idea of how to do that, but I'm not sure if it will work correctly or not. The best answer is to add a patch to core to track the user's timezone in the user record, and I've proposed a patch to do that at http://drupal.org/node/11077.
My hope is that this will get into core, and then I can add to the Date module a way to properly handle a new option on dates to show them in the user's timezone.
Comment #3
karens commentedThis may not be exactly what you were asking for, but the 5.2 version will have an method to track users' timezones so we can adjust the date properly for the user. It also uses the PHP 5.2 timezone handling which works MUCH better and I hope it will eliminate most of the problems with timezones.
The new version is in HEAD and is not ready to use yet. Wait until I create a 5.2 branch before using it.
Comment #4
(not verified) commented