Closed (fixed)
Project:
iCal feed parser
Version:
6.x-1.1
Component:
Miscellaneous
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
30 Mar 2010 at 16:06 UTC
Updated:
18 May 2010 at 18:48 UTC
I was having some issues setting up a feed so I worked through the tutorial on a brand new install of Drupal 6 to make sure nothing else was interfering. When it comes time to map the fields to the feed, there are only 4 items in the source dropdown and they don't have anything to do with my feed or my content type. See attached screenshot.
Version info:
iCal Parser - 6.x-1.1
CCK - 6.x-2.6
Views - 6.x-2.8
Calendar - 6.x-2.2
Date - 6.x-2.4
FeedAPI - 6.x-2.4
FeedAPI Mapper - 6.x-1.3
Any nudges in the right direction to get this working would be greatly appreciated.
--
Loren
| Comment | File | Size | Author |
|---|---|---|---|
| iCal Feed mapping.jpg | 21.29 KB | lorenlang |
Comments
Comment #1
ekes commentedThis usually happens when the parser has not been able to read the feed.
Not being able to read the feed usually happens because:
* you need a password to get to it
* the URL is incorrect
* the feed is not an feed iCal or it is broken iCal.
There isn't much more help without knowing what the URL is of the feed.
Comment #2
lorenlang commentedThe ics file is fully accessible and I can view it directly by URL. It's a direct output from iCal so the format shouldn't be any issue. I've tried the following:
I'm at a loss as what to try next. This is driving me crazy.
Comment #3
ekes commented"There isn't much more help without knowing what the URL is of the feed."
Comment #4
lorenlang commentedI'm working on my dev server which isn't accessible outside of our network, but I've temporarily copied the file up to our live server. You can see it at http://www.asbury.edu/sites/default/files/MainAsburyCalendar.ics
Comment #5
lorenlang commentedAdditional info provided as requested. Changing the status back to active.
Comment #6
ekes commentedAbsolutely sorry for not changing it. It's got repeating events, and it's long. I feel it's similar to other bug reports, so will work asap. I've just started a new contract which pushes this back, but really want to get this tested before the end of the week.
Comment #7
lorenlang commentedThanks for the reply, ekes.
The length I can deal with - I've successfully made that work at some point in the distant past by importing in multiple stages - but I'm seeing the same issue with shorter files as well.
As I said earlier, any help you can provide, be it a fix or even a workaround, to get things imported will be greatly appreciated.
--
Loren
Comment #8
ekes commentedOK I've run it against the feed above. To manage to do so successfully with the size I had to allow the timeout and memory be big - I took about four minutes to import all 1700 or so nodes. It does work though, other feeds with lots of complicated repeating events I can't say the same for at the moment.
I notice, looking back at your picture above that there is no feed item example. This really only ever happens if you are (a) setting the mapping on the admin/content/node-type/feed/map page - because feedapi_mapper doesn't know about the elements yet (b) on the node map page node/###/map if the feed cannot be read for what ever reason.
Comment #9
lorenlang commentedThanks for the test. Can you provide a screenshot of the content type that you're importing them into? I've been wondering if this is a problem with the config of that type.
--
Loren
Comment #10
lorenlang commentedI finally got some time to spend working with the content type and it looks like the issue was with repeating events and the fact that my content type didn't have a To date option. I don't really need one but it was causing the issue described. I blew away my existing events (from an iCal file with no repeating events) and rebuilt the content type with a repeat option on the date. This seems to have fixed the issue.
--
Loren