Forums » List all forums » » Forum: General Discussion » » » Thread: After a date shift, the appointment appears twice |
Posted by chris37170 at Dec 15, 2017, 12:55:25 PM |
After a date shift, the appointment appears twice Hello I moved an appointment in March in the Google calendar from 03/09/2018 to 03/02/2018. This date will also be displayed correctly in Google calendar. In the localendar, however, this appointment appears twice. Once the new appointment 03/02/2018 and also the original date 03/09/2018. sincerely Christoph user: chris37170 (Translated with google translator) |
Posted by support at Dec 15, 2017, 11:36:34 PM |
Re: After a date shift, the appointment appears twice This is what the event looks like in the feed we are receiving from Google: BEGIN:VEVENT Please note this line: RECURRENCE-ID;TZID=Europe/Berlin:20180309T190000 Google appears to be indicating there is still an occurrence on 9 Mar 2018 The specification for how to handle RECURRENCE-ID is not clear. At this time, localendar will assume these events should be displayed. If you delete the event in Google and re-create it (instead of Move), it may work properly ---------------------------------------- Marc Higgins Support Associate, localendar.com Follow us on Twitter! http://www.twitter.com/localendar_news |
Posted by chris37170 at Dec 16, 2017, 5:22:36 AM |
Re: After a date shift, the appointment appears twice Hello Marc, The deadline of 03/09/2017 is a recurring appointment that takes place every two months (January, March, May, July, September, November) every second Friday of the month. By postponing the deadline from 03/09/2017 to 03/02/2017, Google calendar has marked this recurring event with the flag RECURRENCE-ID. This flag must not be taken into account for entries in the localendar. I hope you can take this into account. Translated with Google translator Sincerly Christoph |
Posted by support at Dec 21, 2017, 2:33:26 AM |
Re: After a date shift, the appointment appears twice The handling of RECURRENCE-ID is unfortunately not as standardized as you would hope. There are also other ways to handle event exceptions in iCal. The current library we are using for iCal parsing does not follow the same interpretation Google is using this field for. At this time, we are limited in how we can handle this use of RECURRENCE-ID ---------------------------------------- Marc Higgins Support Associate, localendar.com Follow us on Twitter! http://www.twitter.com/localendar_news |
Posted by chris37170 at Dec 24, 2017, 5:13:28 AM |
Re: After a date shift, the appointment appears twice Hello Marc, I found this links to this problem. Maybe it helps. https://icalendar.org/iCalendar-RFC-5545/3-8-4-4-recurrence-id.html https://www.kanzaki.com/docs/ical/recurrenceId.html Sincerely and nice Christmas Christoph |
Posted by support at Jan 1, 2018, 4:54:18 PM | ||
Re: After a date shift, the appointment appears twice Thanks, We're aware of the specs you mention, but as I noted in my last post, what the specs say and how others have chosen to implement it are two separate items Since we are not internally ical-based, we rely on 3rd party libraries to help where we integrate with iCal feeds. And at this time, the handling of RECURRENCE-ID is slim to none. Just two of many public threads where people are wrangling with this issue (this time from a Wordpress calendar provider) https://icalevents.com/4437-correct-handling-of-uid-recurrence-id-sequence/ also https://stackoverflow.com/questions/11456406/recurrence-id-in-icalendar-rfc-5545 IBM has this to say about the subject (I have added emphasis)
When localendar first started (in 1999!) iCal was a spec followed/used by basically no one. In the past 18 years (!!!) we have seen things mature to the point where it's a standard that works in about 95% of all cases. It's amazing the amount of interoperability and portability we have now compared to what we had back then. We'll continue to monitor the situation, and if everyone settles on a common implementation for RECCURENCE-ID, then we'll support it, too. ---------------------------------------- Marc Higgins Support Associate, localendar.com Follow us on Twitter! http://www.twitter.com/localendar_news |
Help! | Cobranding | Legal | Privacy Policy | About localendar.com | Contact Us |