|Importing valid ICS file results in "processed zero events" error.||Ian A. Dunn||3/28/14 9:39 AM|
I'm trying to import an ICS file, but I get the "processed zero events" error. If I "add by URL" instead of importing, I don't get any errors, but no events show up. The calendar imports/subscribes fine in BusyCal (Mac) and VueMinder (Windows). The location of the file is http://central.wordcamp.org/calendar.ics.
I've gone through the relevant documentation (Trouble Importing iCalendar Files and Format iCalendar Files) but none of the potential causes mentioned there are the problem in this case.
I've tried half a dozen times and get the same result each time. I've tried in Chrome and Firefox, and get the same result in each. I also checked the list of known issues, and it's not on there.
I'm fairly confident that this is a bug in Google Calendar.
|Re: Importing valid ICS file results in "processed zero events" error.||Ian A. Dunn||3/28/14 10:04 AM|
I found the source of this problem by trial and error. If an event DTSTAMP is declared with only a date, rather than a full timestamp, Google Calendar ignores the event, even though specifying only a date is valid according to the RFC.
This is definitely a bug in Google Calendar.
Example of calendar that works:
Example of calendar that doesn't:
|Re: Importing valid ICS file results in "processed zero events" error.||Ian A. Dunn||3/28/14 11:42 AM|
|Re: Importing valid ICS file results in "processed zero events" error.||Ian A. Dunn||4/1/14 11:44 AM|
Subscribing to the calendar is working now. Maybe because the file was cached on Google's end and there was a delay between when the workaround I mentioned earlier was implemented and when the cached version expired, or maybe because of recent changes related to the time shift bug.
|Re: Importing valid ICS file results in "processed zero events" error.||Ian A. Dunn||4/2/14 8:35 AM|
Just to be clear, there is still a bug in Google Calendar; the only reason it's working with http://central.wordcamp.org/calendar.ics is because I modified that ICS feed to work around the bug. In order to fix the bug for everyone else, the Calendar team will need to implement support for DTSTAMP fields in the VALUE=DATE:YYYYMMDD format, which is a valid format according to the iCalendar RFC.
|(unknown)||4/16/14 8:45 AM||<This message has been deleted.>|