I am not sure what I'm not seeing, but I've enabled the feed item content type. I've check all permissions. I've looked into the taxonomy field configuration for anything. I've checked that all modules are enabled. I'm sure this is something real obvious but I can't find it. All that is available to me is node without my CCK fields. Those feels are autotagging fields, can that be it? mapping doesn't work with autotagging fields? I appreciate any pointers. Many thanks. Kevin
| Comment | File | Size | Author |
|---|---|---|---|
| #9 | feedapi_mapper_content_taxonomy.inc_.txt | 4.94 KB | rjbrown99 |
Comments
Comment #1
alex_b commentedOn your feed item nodes, is there a taxonomy vocabulary enabled? This should be the one that's available as mapping target.
Comment #2
pyxio commentedYes. Mapping works fine with normal CCK fields. But not with CCK taxonomy autotag fields. It would be awesome, this way for example you could have a blog feed and author names automatically added to a vocabulary. You should really consider it for next version. K
Comment #3
alex_b commented#2: oops. sorry. I thought CCK taxonomy was only 5.x. Is this the module you're using? http://drupal.org/project/cck_taxonomy ?
Comment #4
pyxio commentedNope. This is the module http://drupal.org/project/content_taxonomy. I guess feedmapper does not integrate with it?
Comment #5
alex_b commentedIt doesn't. No integration planned from my side. I'd also rather have this integration living in the content_taxonomy module (which is perfectly possible).
Comment #6
pyxio commentedthanks alex. i'll put it in a feature request at content taxonomy forum and see what happens. Thanks. Kevin
Comment #7
alex_b commentedOK.
Comment #8
rjbrown99 commentedLink to the issue in the other queue:
http://drupal.org/node/463670#comment-1806926
Comment #9
rjbrown99 commentedOK, so I needed this functionality as well. There was a patch in the other issue queue as indicated in my previous post, however it did not work for me. A number of things were missing that included an inability to display the mappings, not saving to the core taxonomy properly, etc.
I have taken that patch, updated it into a state where it works for me, and now I am using it within the feedapi_mapper/mappers directory. I am now submitting this for review. I integrated some of the functions and code from the core feedapi_mapper_taxonomy to solve the issues I had.
The reason I think this should be included in this module and queue is because most people are going to start moving to Feeds. I doubt we could get a patch into the content_taxonomy module when this Feed Element Mapper module will eventually be deprecated or replaced by Feeds. I would appreciate it if someone else could review this, test or provide patches, and then consider it for an addition to the module.
Thank you.