Sorry if this is a duplicate... some of the time zone problems looked similar, but I couldn't match up my problem with any of there's for certain, so I'm creating a new one and asking for support. I am in the Central Time Zone. My site is configured for Central Time. User's do not have the option to change times around, so it's sitewide. I am using Date API. When I created a content type called "Event", I included a CCK date field which uses the Site's Timezone. The time was from 4:00 PM on April 19th through 10:00 AM on April 20th. The beginning and ending times were correct, however the break between days happened at 7:00 PM, which I believe is midnight GMT. Therefore, I have 2 events listed on the same day (the 19th), one ending at 6:59 PM and one beginning at 7:00 PM. It can be seen at: http://kblast.com/calendar.

I also tried choosing to ignore time zone (or whatever that option is in the Date API) and that gave me the wrong beginning and ending times (it converted them to GMT I believe).

Comments

BrianKlinger’s picture

Category: support » bug
BrianKlinger’s picture

Version: 5.x-2.0-rc » 5.x-2.x-dev

OK... in debugging I made a number of changes. I am still using Date API and calendar (latest dev releases), but I went through and set my site to be universally on US Central Time (which is -500). I created a whole new content type with a different machine name and all just to make sure I wasn't running into any caching issues. I created a CCK date field and told it to respect the site's timezone. The calendar is forcing a break between 6:59 pm and 7:00 pm (midnight if we are not -500). So if an event lasts from 4:00 pm - 7:00 pm, I see two entries with the same title, one listed from 4:00 pm - 6:59 pm and one at 7:00 pm. I have an example of that and an example of a multiple date problem at http://kblast.com/calendar/2008/03/all.

BrianKlinger’s picture

Status: Active » Closed (duplicate)

Marking this as a duplicate of http://drupal.org/node/247468 since KarenS moved my date bug report over here and I don't need two open issues for the same problem.