braunsch on "[Plugin: All-in-One Event Calendar] Time zone incorrect on ics feed"

There are so many posts about this in this forum - but nobody from timely seems to read them or acknowledge them: All the ones I could see with the same problem did not get a reply or acknowledgment that it's being worked on.
I hope the support will get better - as my calendar is currently unusable.

I have a feed that gets data from a Google calendar.
I have the following settings:
- WordPress time zone: Pacific Time
- Timely Calendar: UTC
- Import feed setting: Use local time zone when importing UTC = Yes.

Result:
- All events coming from recurring entries in the Google calendar are displayed correctly
- All events that are non-recurring show up 7 hrs late: A 10am Pacific event will show up as 5pm (17:00 hrs)
Please look at my calendar http://www.baylands.org/web/content/calendar/
Today's entry "9:00 am Saturday Fun Run" is correct (it's an instance of a recurring event).
Today's entry "5:00 pm Coffee meet up" is not: It's a one-off event and shows on the google calendar at 10:00 am (see the original "live" calendar at http://www.baylands.org).

It would be great if this could be fixed asap - as it is threatening my entire web site project if the core of it - the events calendar - is showing garbage.

Thank you!

https://wordpress.org/plugins/all-in-one-event-calendar/

Similar problem here.

I do have an ICS feed to a 'booked' system
- WordPress Time Zone is Europe/Berlin
- Timely Calendar Time Zone is Europe/Berlin

All imported appointments do show wrong starting and ending hours - with an offset by - 2 hours.

Same ICS feed from other calendar systems do show correct starting and ending hours.

So somehow the import into timely calender get wrong calculations.
Also I observed that the selection of the update frequency is gone. How can users now change it? What is the default frequncy?

Repeated events seem to be properly imported

My workaround fix was to make all my events repeated and for the "one off" events just set the repetition limit to 1 occurrence.

Like I said, it is a workaround and similar to most workaround is a nuisance but it fixes the issue since they clearly have a bug in their import code for non-repeated events.

@atkoehler
Thanks for your comment - but in my case all events are repeated (every week).
So in my case such workaround doesn't solve the problem and I wish someone has a look into that.

Does this have to do with us being forced to run the subscriptions through their servers??
I upgraded from a 2.3 release to the 2.5 release - which forces us to go through them - and now I encounter this problem.
Is this, maybe, a problem on their end?

The silence from Time.ly is not a good sign...

Hi,

Bug is fixed, please upgrade the plugin to the latest version 2.5.3.

We apologize for any inconvenience this may have caused.

Thanks,
Ben

I've updated to 2.5.3, deleted the feed and reimported everything and I'm still seeing all my event dates wrong. Events are showing 5 hours in the future. I'm in central time zone.

I tried checking and unchecking "Assign default time zone to events in UTC".

Double-checked my Google Calendar is set to correct time zone at Google.
WordPress time zone is set correctly.

Also updated to 2.5.3 and having same problem with Google calendar import.
Checked all time zones and settings. My locale is London

Benjamin -

Thank you for looking into this - but unfortunately it did not help.

I just deleted all calendar entries, upgraded the plugin to 2.5.3, and refreshed the feed from my google calendar.
The same problem still persists.

- Recurring entries displayed correctly.
- One-off entries displayed in GMT.

If you give me an email address or other contact information I can give you the link to the calendar I am trying to feed into my site - so that you can try yourself.

Hello Benjamin,

could you please tell us what was fixed? Upgrading to 2.5.3 didn't solve the problem on my side. The feeds from 'booked' get entered into the time.ly caledar with UTC/GMT time - what I need is Europe/Berlin.

Hi Ben,

just noticed that now Rev. 2.5.4 was offered.
Unfortunately no change after updating. Times shown are still in UTC-Format. So somehow there is still no conversion to the actual calendar timezone taking place.

Regards
Dieter

Same here: New release (2.5.4), same error.

It is too bad that Time.ly does not publish release notes for this plugin.

Folks - why is this marked resolved?

It's not at all - or am I meanwhile the only one being hit by this issue?

Hey guys, indeed the last two patches have fixed most people encountering this issue. We'll follow-up on this thread to make sure everyone gets resolved.
I'm reopening this now. Thanks for your patience.
Aristotel Dascal, VP of Product @ Time.ly

Hi all.

Can you please provide the link to the ICS feeds which you are having problems?

Calvin - can you please give me an e-mail address to which I can send the ICS feed link?

Thanks!

Georg

Hi braunsc!

Yes, please send to this email: [email protected]

Thanks!

Hi Calvin - just to let you know, that I sent my problem link to above mentionned email address this moing.

As already said in my email:
An import to a Google Calendar with the same link is working properly and shows correct local times.

Hello Calvin - I just sent an e-mail with the link to the address you provided.

Thanks!

Georg

Calvin,

Thank you so much - Module upgrade 2.5.5 was the breakthrough!
It works now like a charme and I (we all) are happy.

One information I am still looking for: How often gets the ics feed polled?

regards
Dieter

Hi dhaude!

That's a good news that the update worked for you!

The feeds are pooled every hour using WP cron, but it can take another hour to be updated on our side. We're working hard to improve the update delay time on our side.

Thanks!

Just confirming from my end: It now works fine for me, too - the time zone conversion to my local time zone works as expected.

Thanks for the efforts made to get this fixed, and thank you to the others who chimed in - telling me that I wasn't alone.

As I was the originator of this support thread, and as it works for me now, I mark the topic as "resolved".