When I use Year/Month/Day arguments with event_views 5.x-1.x-dev the results displayed start at 7 p.m. of the night before the day specified and end at 6:59 p.m. of the specified day.

My server is set for GMT -0500 and my Drupal default date and time is set to GMT -0500. Configurable timezones are disabled.

If instead of arguments, I use filters, I get the following results:

When the Year/Month/Day filters are set to "now," I get a one hour offset -- events appear from 11 p.m. of the night before the day specified through 10:59 p.m. of the day specified.

When I use the Start Date filter and set it to "now," I get events starting with the current time, and offsets from "now" work properly (but of course that does not provide a way to get events to consistently display in midnight-to-midnight increments.

I have spent considerable time digging around on Drupal.org and in the events and events_views module code and have had no success in fixing the problem.

Any help in resolving this would be greatly appreciated.

Comments

knieveltech’s picture

knieveltech CreditAttribution: knieveltech commented

I am having the same issue on several websites with the timezone set to various values. Server time is GMT -0500. So far I have likewise been unable to come up with a fix.

levelos’s picture

levelos CreditAttribution: levelos commented

I'm seeing the same problem with Event 1.0. I've spent the better part of a day debugging this and I'm getting no where. This seems like a huge problem and I'm surprised there's not more out there. Using devel, I inspected the queries and they are correct, so somewhere in the code the events are being filtered out.

Update: I stepped through the construction of the view and copied the query at the exact time of execution. When running it directly in MySql, the results are correct. However, in _db_query, when running mysql_query, the results come back with the timezone offset problems. I'm very confused at this point ... is it a PHP setting?

gregrenner’s picture

gregrenner CreditAttribution: gregrenner commented

Having the exact same problem. View w/ arguments, timezone is CDT (GMT -5:00), all events from 7:00pm to Midnight do not show up in the view that the module builds. Its as if the module is completely ignoring the timezone and using GMT.

levelos’s picture

levelos CreditAttribution: levelos commented

I'm wondering if this is a problem with views or event, or event_views? The event calendar itself behaves correctly - the problem only comes up when making a custom view using arguments. ANY HELP OUT THERE from event folks? This is proving to be a huge problem for me, and others I'm sure, and I've spent a huge amount of time debugging with no luck ...

Gerhard Killesreiter’s picture

Gerhard Killesreiter CreditAttribution: Gerhard Killesreiter commented

Timezones were notoriously difficult to get right with the Event module prior to version 5.2. I suggest you upgrade to 5.2.

levelos’s picture

levelos CreditAttribution: levelos commented

Thanks for that tip. I gave that a try recently and it's no where near ready for production use, and the update path was not clear either. E.g., even after I got past the white screen PHP error (related to duplicate function calls), still lots of little issues scattered throughout. I might try migrating to date / calendar next.