Update –

After some work, I found a work-around for the gCal “Add To Your Calendar” issue – if I split up any recurring events in two (keeping one with all the events during Daylight Savings and one with all the events during Standard Time), and turn on the “This event is effected by day light savings time” for both events, the problem gets resolved for gCal.

However, the problem only gets worse for ical exports – when an ical is downloaded from EventOn & then uploaded into Google Calendar, the problem returns (i.e. events during Standard Time get marked one hour earlier; 7pm -> 6pm). To make matters worse, the events get labelled as “(GMT+00:00) Coordinated Universal Time”; and if you try to change the time zone to the correct zone (MST), the events time shifts from 7pm – 1am.

Overview of the problem:

1. Recurring events that span from Daylight Savings Time to Standard Time will not export to iCal or gCal correctly; with events in one of the times (depending on your settings) showing up either an hour earlier or an hour later. (Solution: create two separate recurring events; one for all the recurring events during Daylight Savings Time & one for all the recurring events during Standard Time – turn on “This event is effected by day light savings time” for both events)
2. Exports of iCal (for single event & full calendar) do not work properly; exporting all events under “GMT+00:00) Coordinated Universal Time” which then gives events during Standard Time the wrong time (-1 hours). (Solution: refrain from using the iCal download option on EventOn widget; use the following custom CSS to hide the iCal download link on individual events: .evo_ics_nCal { display: none !important; } )

Hello,

Thanks for the reply; sorry I’m getting back to you so late.

With the settings I listed above, I can export events from an individual event to gCal or in the iCal format, however when I export the full calendar via iCal, the times still get messed up for any event occuring during Daylight Savings time. Looking at the UTC0 times, it appears like all events (regardless of whether they occur during daylight savings time or not) are exported using the exact same time (i.e. all events running from 7-9:30 mountain time are listed as UTC0 1:00am-3:30am); which runs into issues during Daylight Savings time due to Google Calendar automatically adjusting for the time change.

For example, an event on November 1st (MST) starting at 7:00pm-9:30pm will be listed as UCT0 1:00am-3:30am – which Google automatically adjusts (-6:00) to reflect the accurate 7:00-9:30pm time. However an event on November 8th (MDT) starting at 7:00-9:30pm will be listed as UCT0 1:00am-3:30am – which Google also automatically adjusts (-7:00 due to time change) to reflect an inaccurate 6:00-8:30pm. This only appears to occur when exporting the full Calendar via iCal, and occurs in other calendar applications as well.

I have also noticed that Google Calendar cannot import CSV events exported from Eventon, although this is less of an issue for me as CSV doesn’t offer full features I require.

Thanks

Hi,

I know your CEO is reviewing this issue, but I wanted to put out one further update on how the issue has developed. Currently, I am able to export single events during both MDT and MST, and they will show up in Google Calendar correctly; however when I try to export all events, any event set for a start date after MDT ends (on November 3rd) has a start and end time one-hour earlier than it is set on in your application. This happens regardless of if the option “This event is affected by Daylight Savings Time” is checked or not.

As a further note, when a single event is exported from the Calendar that has a start date after MDT ends, and the “This event is affected by Daylight Savings Time” is not selected; the event will import into Google Calendar as if it starts and ends one hour earlier than set on the site – this is remedied easily by toggling the “Daylight Savings Time” option on the event. Unfortunately, this does not work for the full calendar export

Was there a fix for this in an update or if not a workaround? I’m having the same issues.

No – no fix was ever issued for this; the full export of the calendar still won’t work properly altho with some work you can make the individual event exports work properly (by setting some events to “affected by daylight savings” and some not) – it takes a lot of work to do though.