When the Event module (6.x-2.x-dev) is enabled, the time settings for the system are incorrect.
My server is set to CST. Default time zone for Drupal is set to America/Chicago (when Event enabled). User time zones are disabled and set to NULL in the database. Posts, log entries, etc. all show current time +5 hours.
$ uname -a
Linux xxx.com 2.6.23.15-80.fc7 #1 SMP Sun Feb 10 17:29:10 EST 2008 i686 i686 i386 GNU/Linux
$ date
Wed Feb 27 09:13:47 CST 2008
Comments
Comment #1
sstern-at-ccim commentedping.... This is still an issue. I reenabled events and now all system times are screwy. I cannot find any setting that properly displays US/Central or America/Chicago
Comment #2
sstern-at-ccim commentedThe error appears to be in the installation code. Here's what's supposed to be installed for America/Chicago:
But the offset and offset_dst fields in the database are both set to "0000-00-00 00:00:00"
Should the database field really be a "datetime" field? Browsing through the table, I see all sorts of very strange values. The insert statement converts "-6:00:00" to an all zero value.
results in
There is no way to set a negative number!
I modified the table to change offset and offset_dst from datetime to int and put in the appropriate values for Chicago (-6, -5) and now the system displays the correct time.
Comment #3
erikwebb commentedI have the exact problem. It took me days to figure out that all times were screwy because the entire event_timezones table contains, essentially, junk.
Here is an example of some values after altering the offset and offset_dst to be integers:
Or as an example of screwy values (again, after the modify column statement):
Comment #4
killes@www.drop.org commented#213822 was marked a duplicate of this issue
Comment #5
killes@www.drop.org commentedUPDATE `event_timezones` SET `offset` = '-5:00:00' WHERE `timezone` = 58 LIMIT 1;
This works fine for me on Linux. Can I assume you guys run Windows?
@erikwebb: Of course the table contains junk after you change it's definition to values they aren't supposed to have...
Comment #6
erikwebb commentedYou're right, but the values before were equally as screwy:
This was with the newest Event module on Drupal 6.2
Comment #7
macgirvin commentedsubscribe
Comment #8
gerhard killesreiter commentedfixed in cvs
Comment #9
gerhard killesreiter commentednote: you'll need to run update.php
Comment #10
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.