The icalendar URLs generated with this module are not compatible with Google Calendar as of today.

I was able to make them compatible, just by changing the header enconding from utf-8 to UTF-8. I'm requesting this change to be made in the module.

Sounds crazy. It's crazy. More info: https://productforums.google.com/forum/#!topic/calendar/OpbtaN9ZRVE

CommentFileSizeAuthor
#2 date_ical-2204649-by-coredumperror-jorge.suarez-Compatib.patch1.46 KBgeek-merlin
#1 date_ical-headers_change-2204649-1.patch912 bytescoredumperror

Comments

coredumperror’s picture

coredumperror commented
StatusFileSize
new date_ical-headers_change-2204649-1.patch912 bytes

Do you mean that Google has suddenly started requiring a capitalized UTF-8 charset header just today, or has this been in effect for a while? The page you linked is very old, and in fact suggest a different solution that what you mentioned, so I'm a bit confused.

Here's a patch that improves the headers offered by Date iCal's export system, including your suggestion. But I haven't applied it to the dev version, yet.

geek-merlin’s picture

geek-merlin
Primary language German
Location Freiburg, Germany
commented
Status: Active » Reviewed & tested by the community
StatusFileSize
new date_ical-2204649-by-coredumperror-jorge.suarez-Compatib.patch1.46 KB

here's the patch rerolled against current dev.

i can confirm it applies cleanly and fixes the OP issue.

jorge.suarez’s picture

jorge.suarez commented

Sorry for the delay on answering.

This seems to be very random. The people came out with different solutions, but only this one worked for me. It seems that Google Calendar is a bit messy and this problem only affects some users.

Please see this comment. https://productforums.google.com/d/msg/calendar/OpbtaN9ZRVE/ITyoHOXww3oJ
Other users are reporting the same behaviour and this as an accepted solution.

The patch from axel.rutz should do the trick, the change is very simple. Please apply it.

coredumperror’s picture

coredumperror commented
Status: Reviewed & tested by the community » Fixed

Huh... As it happens, I appear to have accidentally included this patch in another commit that I pushed to git a couple weeks ago. If you download the latest dev release, you should see this change.

Since this is already marked RTBC, I'll go ahead and just set this issue to Fixed.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.