Events created for August 31st, 2004 do not show up in the calendar view. This is true for both page and block display. I have verified this phenomenon across 3 installations of Drupal w/ both event.module,v 1.64.2.12 and event.module,v 1.64.2.11.
When the "Type of Overview" is set to "Table", the events are clearly visible. Set the "Type of Overview" (in admin/system/modules/event) back to "Calendar" and watch your August 31st events disappear.
Oddly, this seems to be a bug isolated to the single date of August 31st, 2004. I'm sure it affects some other dates sometime, but I have failed to reproduce the problem with any other dates that I have tried (last days, of various months including August 31st, 2005, etc.).
I've now spent a good 5 hours reading the source and not understanding why this is happening. If anybody has a clue, recommendation or patch for this problem, it would be greatly appreciated. =)
-- AnalogDuck
keywords: hidden, invisible, missing
Comments
Comment #1
analogduck commentedAdditional note: I've noticed that there is a similar item posted last April which was supposedly resolved. You can read about it here: http://drupal.org/node/view/6920
I'm not sure if this was the same or a related issue, but the issue I am experiencing is definitely not resolved in the current release of the event module (listed in the above post).
-- AnalogDuck
Comment #2
(not verified) commentedThis is a serious bug: The calendar view is selecting events from the month based on GMT time. The August event you're talking about is probably in the database as "September". Likewise I have events for Sep. 30th which are not showing up. This needs to be fixed.
Comment #3
(not verified) commentedEvents will show up on the correct dates if "Timezone Handling" is set to "No." This works for me, because my site doesn't have visitors outside my timezone. But the problem still exists if I turn on timezone handling (I'm using the 4.5.0 version).
Comment #4
TheFazz commentedI've had the experience of an event on Saturday 1 October 2005 showing up on 1 Septermber 2005 in the calendar view.
however, when I turned of the timezone handling, then the dates and time got all screwed up and moved backwards by 8 hours (my timezone is GMT+8).
this is a serious bug.
Comment #5
killes@www.drop.org commentedI don't argue abotu the seriousness of the bug, however i can't really debug it. All my servers are in the same time zone as myself andrun on local time. Switching off time zone handling works fine in my case. I suggest doing some debugging yourself and trying to find out where the date is screwed up.
Comment #6
(not verified) commentedIt seems obvious enough to fix.... when the calendar code figures out which events to display for a given date range (e.g. particular month) or what date/time to display them as having, it has to take into account the default timezone of the website (or timezone of the user, if a user is logged in). This would involve adding and subtracting hours from the GMT dates/times stored in the database.
Presumably, it is presently doing simple SQL selects which do not take into account the timezone (whether the default site timezone or the user's timezone).
By the way, it seems that the proper way to handle timezones would be for the website admin and website users to choose a standard zoneinfo timezone (e.g. Americas/Los_Angeles)... thus the event module can correctly take into account daylight savings while calculating the GMT offset.
Comment #7
killes@www.drop.org commentedfixed in cvs
Comment #8
(not verified) commented