Timezone offset value not saved to database when repeat dates are used [#1317586]

I'm using a date CCK field to store a date and time with a configurable time zone.

If I save a node with a single date, then the date saves to the CCK field's table in the database with the offset and offset2 values set correctly.

e.g, with timezone set to America/Vancouver, I get offset = -25200

If I save a node with the same date and time, but have the event repeat every week, then no offset nor offset2 value is saved in the database.

e.g., with timezone set to America/Vancouver, I get offset = 0

This causes the date and time to appear incorrectly on the node's page. It appears as 7 hours ahead because the timezone offset is not being applied.

How can I get the offset value to save to the database when there are multiple dates?

Comment	File	Size	Author
#4	offset_missing_repeating_dates-1317586-4.patch	1.53 KB	srees
#4

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Comment #1

endless_wander CreditAttribution: endless_wander commented 22 October 2011 at 07:39

In date.module, in the date_formatter_process() function, if I log the following line, the correct offset values are there:

$dates[$processed]['local']['offset'] = date_offset_get($date);

But this is never saved to the database when repeat dates are entered. Still investigating.

Comment #2

endless_wander CreditAttribution: endless_wander commented 22 October 2011 at 08:04

I solved my problem of the wrong time appearing in the node display by using the date_offset_get() function to add on the appropriate offset to my times.

Still, this seems like a bug that the offset and offset2 values are not set in the database.

Comment #3

needle CreditAttribution: needle commented 4 October 2012 at 16:16

Version:	6.x-2.7	» 6.x-2.9
Component:	Date CCK Field	» Code

Encountering the same issue. Thanks for posting a workaround, clavigne, however I use `variable_get('date_default_timezone', 0)` to get Drupal's setting instead of the server's.