Posted by orbmantell on March 7, 2011 at 11:05pm
4 followers
Jump to:
| Project: | iCal feed parser |
| Version: | 6.x-2.0-beta1 |
| Component: | Code |
| Category: | bug report |
| Priority: | major |
| Assigned: | Unassigned |
| Status: | active |
Issue Summary
When I install the 2.0-beta1 version of iCal feed parser I am unable to select individual custom fields that are selectable in the 1.1 version of this module. In the 2.0 version the parse-able fields are VEVENT (date) and location. My iCal feed, however, has fine-tuned fields such as room, address, cost, city, state, contact, etc...
In 1.1 I am able to map these fields to CCK using the feedAPI mapper module, with the update to 2.0 and using the feeds module this functionality is lost. Is there a way to make the iCal feed parser module allow for mapping of custom fields to CCK?
Thanks
Comments
#1
I am having this problem also. I can't pull in the description because in the feed it is labeled something different.
#2
This sounds like a regression -- changing to bug report.
#3
Perhaps related to #651478: Mapping on import
#4
I cannot find a means to map custom fields besides extending hacking ParserIcalFeedsParser::getMappingSources() or perhaps extending ParserIcalFeedsParser -- surely this isn't the supported method of adding custom fields?
Couldn't we create a standard Drupal hook in getMappingSources() so that a theme could override them? Hmm.. it would be nice to override these sources per-feed, so that could be tricky.. :/
#5
Inheriting the class would be the correct way.
Any patches for fields that exist in the standard, or are common in the real world, would be greatly appreciated however.