Drupal Association members fund grants that make connections all over the world.
The ical feed
http://mysite.org/calendar/ical does not conform to the ical standard, RFC 2445. Specifically, if the DTSTART and DTEND values are formatted as DATE and not DATETIME, then the syntax needs to be changed. The OP recommends using http://icalvalid.cloudapp.net and http://severinghaus.org/projects/icv/ to validate ical feeds.
The patch in #9 modifies
calendar/calendar_ical/calendar-view-ical.tpl.php to format DTSTART and DTEND values correctly.
Warning when using git apply
If you have problems applying the patch using
git apply, then see or use
$ patch -p1 < /path/to/patchfile.patch
Please commit the patch from Comment #25. Credit should go to crifi and hirbys. (See Comments #8 and #9.)
User interface changes
Comments 14–23 deal with an off-by-one problem with the DTEND value. This has been moved to the Date issue queue:.
For D7, both issues can be solved within the Calendar module. See.
Original report by gmak
I've just spent the afternoon changing all my 'All Day' events (eg. those that have a start and end time of 00:00) to have set time periods. The reason was I was suddenly finding that the ical export to Google Calendar was broken. I'm waiting to see if this fixes things, but I did find that the all-day events in my calendar were causing parsing errors (according to http://icalvalid.cloudapp.net and http://severinghaus.org/projects/icv/)
The CloudApp checker was presenting errors such as:
The 'date-time' value '20110212Z' is not formatted properly.
Having changed all the all-day events, both checkers give 100% scores.
Is there some trick to All Day events for ical export or did I find a bug?