When using a brand new installation of Drupal, Feeds, and iCal parser, iCal parser fails to import any iCal nodes. When attempting to import any iCal feed (including US Holidays (hosted by Google) or Dutch holidays (hosted by Mozilla), or any other public Google Calendar), the base "feed" node is created without problems, but it fails to import anything—Drupal reports that "There is no content" when attempting. No "feed item" nodes are made. I've also tried creating a new content type for calendar items, but it also fails.

I'm able to import regular RSS feeds using the Common syndication and Simplepie parsers, but the iCal parser fails every time.

To make sure I didn't mess up any settings, I cloned the default "Feed" importer and switched it to the iCal dateapi parser, but it still fails. Here are my settings:

What would cause this kind of failure? Do I have elements mismapped? Some setting wrong? In theory this should just work, but it's unfortunately not…

I'm using a fresh Drupal 6.20 installation with CCK (6.x-2.9), Chaos tools (6.x-1.8), Date and Date API (6.x-2.7), Job Scheduler (6.x-1.0-beta3), Feeds (6.x-1.0-beta11) and iCal parser (6.x-2.0-beta1).

Thanks for any help you can give!

Comments

ekes’s picture

ekes commented

I'm not sure what the error is. But, it's not the mapping. It's before that if it's reporting 'There is no content'. Are there errors in the watchdog, or the webserver log? What happens if you run the tests?

andrewheiss’s picture

andrewheiss commented

After hours of tinkering, I finally figured it out. Apparently when you attach an iCal parser importer to the built-in "Feed" content type, nothing imports. However, I created a brand new importer attached to a new content type named "iCal feed" and it started importing just fine.

What was throwing me off before was that I had cloned the default Feed importer and then tried to attach it to a different content type, which didn't work. There's something hidden in the default importer that doesn't work with iCal parser—I have no idea what it is, though.

So, to fix this, create a new importer, attach it to a new content type (i.e. iCal Feed), change the parser to the iCal dateapi parser, and change the content type in the node processor settings to another content type (i.e. iCal item). Change the mapping settings, import, and it will work.

Phew.