Page 1 of 1

Calendar function posting events 11 hours earlier

PostPosted: Mon Nov 14, 2011 6:40 am
by rleyba
Hi Steve,

My Calendar view has this strange behavior where in my "ImplementationStartDate" which is a date/time field is saved correctly in the database but on the calendar view, it is often showing up in the wrong date as the calendar keeps forcing all the events to be 11 hours early.

I have this in my fields.ini

[ImplementationStartDate]
widget:description="Click on the calendar icon or type in date in YYYY-MM-DD HH:MM:SS format (e.g.2011-07-12 17:29:00).
widget:label="Implementation Start Date/Time"
event.date=1
event.start=1

I tried to force the calendar to work correctly by making it evaluate a DATE field only (not date/time). In the case below, the ImplementationStartDay is a date field and inserting the timestamp inserts only the date portion, which is OK with my requirements.

[ImplementationStartDay]
widge:label="Day/Date of implementation"
timestamp=insert
widget:type=static
event.date=1
event.start=1

when I now go to Calendar view it still inserts a time component and forces some kind of offset.

What exactly does the event.start=1 option do? My records are date sensitive only and not time sensitive so I am not concerned about the event start "time" parameter. I even tried commenting out event.start=1, and even doing event.start=0 but xataface still seems to keep using the "time" portion of the Date or Date/Time field.

I saw this posting ---> viewtopic.php?f=4&t=5173&p=28268&hilit=calendar#p28268 but can't be sure if this is related to what I am seeing and for that matter, where exactly in PHP or mySQL to apply the fix.

Thanks for all the help.

Re: Calendar function posting events 11 hours earlier

PostPosted: Sun Dec 25, 2011 7:10 am
by kedikatt
Just a wild guess, but could there be two different time zones set in different locations of the chain?

Re: Calendar function posting events 11 hours earlier

PostPosted: Tue Dec 27, 2011 11:03 am
by shannah
That is the correct post to look at. Particularly the fix suggested by strast at viewtopic.php?t=5173#p25318