Open EverBS2014 opened 6 years ago
After some testing it seems to be connected to summer / winter time. All entries that are created during wintertime are displayed correctly. The entries that are one hour behind in google were created during summer time.
I deleted the old repeating entry that was created in June 2017 during summer time entry and created a new repeating entry which starts in January 2018 and now it is displayed correctly. If I set the start date to June then it is displayed one hour back
Is there any solution? All my current appointments are displayed in Google correctly till the start of summer them. Then all appointments are still correct in the web calendar but one hour later in google calendar
Nobody who has any idea? In that case this calendar is pretty useless to me because my users want the connection to google calendar :-(
Has anybody an idea? I can see when I click on one event in the webcalendar I see Starttime as CET und on another event it is CEST. The CET Events are displayed correctly Google but CEST not. Where is this information CET or CEST saved?
I'm using the webcalender on my homepage and so far it all looks fine. After updating to the newest version some of my termins were 5h back but after editing them everything looks fine.
Now I wanted to connect the calender to my google calendar. For that I went to google and added a new calendar by url "www.mypage.de/Calendar/publish.php/BBD.ics"
Google displays my termins now all but for some the time value is correct and for some the time value is one hour back. How can this be? For example this: One repeating entry has the same time and the other is one hour difference that's how it looks in webcalendar
this is how it looks at google
The used time zone is Berlin
I'm not sure maybe one is still from the old calender and one after installing the latest version. How can I fix this?
When I look in google at the ical url then I see that google says the webcalende ical would be (GMT+00:00) UTC but in the webcalender I have Berlin as time zone. Maybe that's the problem?