The current implementation allows the option to use a date-specific timezone name (which is stored in the database). The offset is calculated using the event_timezone.inc file. This works fine for creating, editing, and displaying dates, but since the offset is not stored in the database, there is no way to account for it when using views. It looks like a database update is needed to store the offset in the database. I will be doing this soon.

Comments

KarenS’s picture

Status: Active » Fixed

I've added an offset column to the table when date-specific timezones are used, which will give Views something to look for.

Anonymous’s picture

Status: Fixed » Closed (fixed)