integration with feedapi mapper

I haven't been using this module yet, and I don't know that much about it. How can I make Content Taxonomy fields mappable? Any hooks?

I'm not sure. You might want to drop into the thread over at http://drupal.org/node/454420. That is a short conversation I've been having with the developer of FeedAPI Mapper. I believe he can give you some idea of how to do it. I suspect you'll be seeing more requests for this in the near future so might want to give it some thought. Cheers. Kevin

I took a short look at the taxonomy and cck integrations, shouldn't be that much work to integrate content taxonomy fields. definitely a cool module, but I rather have to concentrate on other issues with content taxonomy. would be cool, if someone else would provide a patch.

subscribing.

Is there a way for us to chipin possibly? I thought feedmapper api would work with content taxonomy also, but apparently it does not.

Thanks,
Chris

Hi Chris, I might be willing to chip in if this can be done within half a day. Do you know any drupal developers? I'm working with a couple. We can get a quote and get it done if you need it as urgently as I do. Cheers, Kevin

i am going to try something.

with content taxonomy you can save the term to the cck and the taxonomy tables.

I want to see if I save the term to the taxonomy table if it will show up under taxonomy in the feedapi settings.

If someone else could also help to test this theory, it would be helpful.

Chris

i haven't managed to be successful with it. programming a patch so content taxonomy fields can be mapped isn't a difficult task. my experience is that is just easier to pay a programmer to get things like this done rather than wasting hours looking for other solutions that are never really as good anyway in the end. I've learned the hard way ;o) i think for $25 each we can get this done fast and proper.

I'll pay $25, where do I sign up, need asap

subscribing.

I'll chip in too! Tell me what i have to do.

Chris

This solutions worked for me, doesn't pick up previous taxonomy settings well, but everything going forward is smooth

http://drupal.org/project/feedapi_field_inherit

Is this module the result from this thread?
Greetings, Martijn

There is already an inherit taxonomy module bundled with feedapi. is this the same? or is it something different? if so, what's different about it? I don't see how it solves the issue discussed in this thread. we need feedapi to recognize content taxonomy fields in the same way it does other cck fields.

Yeah you're correct this isn't for the mapper, this just allows you to pass the content taxonomy selection to inherited nodes.. sorry to get your hopes up. Might still help someone though, solved my problem.

I just finished creating a first version of a mapper for content_taxonomy, since it appears I need one for my current project.

It's been tested with content_taxonomy version 6.x-1.0-rc1. It hasn't been properly tested with multiple values, although the code should work ok. By no means is this tested through and through, so use at your own risk. Maybe it'll give some of the more experienced Drupal developers a good head start and they can implement a more robust version quicker than I could.

Looks like the latest development version has changed a few things on how the code works, so I'm not sure if this is the right way of going about this change. 6.x-1.0-rc1 was using the same type of includes mechanism...

Rename content_taxonomy.feedapi_mapper.inx_.txt to content_taxonomy.feedapi_mapper.inc and place it under the includes/ directory.

This is already defined in content_taxonomy.module :

/**
* Implementation of hook_init().
*/
function content_taxonomy_init() {
if (module_exists('token')) {
module_load_include('inc', 'content_taxonomy', 'includes/content_taxonomy.token');
}
}

might I suggest just adding the folling line to the preexisting function.
module_load_include('inc', 'content_taxonomy', 'includes/content_taxonomy.feedapi_mapper');

to become
/**
* Implementation of hook_init().
*/
function content_taxonomy_init() {
if (module_exists('token')) {
module_load_include('inc', 'content_taxonomy', 'includes/content_taxonomy.token');
+ module_load_include('inc', 'content_taxonomy', 'includes/content_taxonomy.feedapi_mapper');
}
}

Are the content types supposed to show up as an option under the dropdown on the mapping page of the feed node?

As of now, I do not see it.

Regards,
Chris

Regarding #15, the short answer is 'yes' the content type is supposed to be showing under the drop-down and description of available mappers. There is a bug somewhere in the content_taxonomy_feedapi_mapper function preventing it from happening. I'm not sure I have the php skills to fix it, but I'm getting this in the Drupal log:

Nov 26 00:05:43 domU-1-2-3-4-5-6 drupal: http://mysite.com|1234222743|php|1.2.3.4|http://mysite.com/node/1498/map||1||Invalid argument supplied for foreach() in /mnt/web/www/html/mysite.com/sites/all/modules/feedapi_mapper/feedapi_mapper.module on line 721.

I'm on the release / 1.x version of FeedAPI mapper.