Times showing up 1 hour later from CCK date field [#182998]

On my calendar view, I show the title of the event, and then the time it starts. Events for next month and beyond are showing up 1 hour later than their start time (which is the CCK date field I include in the calendar view).

I am using the latest dev version of calendar, as well as the latest dev version of date, and Drupal 5.2

Very strange, I didn't notice it until someone told me the time I had on an event was wrong for december.

I really need to get this fixed ASAP.

Thanks.

Comments

Comment #1

KarenS CreditAttribution: KarenS commented 12 October 2007 at 19:32

Status:

Active

» Postponed (maintainer needs more info)

I have no idea what 'showing up' means. Are you talking about the date node display itself, or a node teaser view, or the way it looks as printed in the calendar, or do you mean it is displayed in the wrong place on the calendar, or what?

Comment #2

dabro CreditAttribution: dabro commented 12 October 2007 at 19:50

I'd like to jump in here because I am seeing ( I believe ) the same problem. I have a cck date/time field in an event content type. The node is saved with the correct time, the teaser view displays the correct time, the full node view displays the correct time. However the month calendar view that displays the title and time(configured under setup tab) in a month layout shows the time field as one hour later. If you click the title and look at the node, the time is correct.
Time zones are enabled on my site, it seemed to help if I configured the cck timezone display options to Americas/Detroit from Americas/Chicago. I'm in the central timezone by the way, I'm not sure but Detroit and Chicago are both central, aren't they? I haven't fully tested this, I was fighting it yesterday and quit for the day. I'm using the latest dev versions of date and calendar by the way. I had to patch the calendar.module again with "Vorticals" patch to correct the day ahead problem. Thanks for the great module, Dave

Comment #3

beekerstudios CreditAttribution: beekerstudios commented 12 October 2007 at 20:17

It's exactly as dabro described. It's showing up (displaying, outputting. parsing, printing, echoeing, etc.) No matter what "option" I choose under fields for the date field I am using, it always displays just the time, and then for november 2007 and on it's showing the date as 1 hour ahead. So if the time of the event and in the field is 12:00pm it displays 1:00pm in the calendar view. And just as dabro described it if you click on the title of the event you see the node view and it displays the correct time 12:00pm.

Comment #4

KarenS CreditAttribution: KarenS commented 13 October 2007 at 13:02

@beekerstudios, I wasn't saying I don't know what the word 'showing up' means, I meant I need to know exactly where you were seeing this.

@dabro, thanks for the clarification. No, Chicago and Detroit are not in the same timezone, Chicago is Central and Detroit is Eastern.

I need more information to do anything with this. What timezone handling is your datefield using? If it's set to use the date's timezone, what timezone is that? What timezone is set up for your site timezone? What timezone is set up as your personal user timezone? All of those timezones get factored into the calculations, so I need to know what they are so I can set up an example that replicates what you're seeing.

Comment #5

dabro CreditAttribution: dabro commented 13 October 2007 at 18:10

KarenS, Thank you for your hard work!
I've tried testing this today to give you a better description.
It appears with all the timezone settings seemingly correct, the time (eg 9:00 am) in month view is correct for the present month. Any months later than the current month the time is displayed one hour later.

My settings:
Configurable timezone ON
Site default timezone -0500 (central time)
Default User timezone -0500 (setting on user accounts seeing problem also)

CCK Field:
Input format default
Time Zone Handling - Site time zone
Site Time Zone - Americas/Chicago (Central (thank you))

I fooled myself on one site I was having trouble with by setting the CCK field to Americas/Detroit and the future times looked correct, however that site didn't have any current month dates.
It appears the timezone code for the present month and future months is different but you would know more about that than I. I hope this helps you get a feel for the problem I'm experiencing. Thanks again, Dave

Comment #6

KarenS CreditAttribution: KarenS commented 14 October 2007 at 12:04

Aha! I finally can replicate the problem. Thanks for the detailed report. It has to do with some parts of Drupal's core timezone method leaking into the calculation. Drupal's user and site timezone info only tracks the offset and not the actual timezone. I have a fix for this in the new Date version where I overload the user and site timezone edit forms so you can select the timezone name instead of the offset so these things get calculated properly. I'll try to find a fix for this version that will keep that offset from screwing up the calculation.