Enforce only one importer per content type

Do I have to create a content type for each importer?

Yes. In fact, we should inforce that.

CCK/FieldAPI field is a good idea, I think this is what we should do for Drupal 7. I don't want to invest in CCK work when the API is completely going to change with Drupal 7.

Would be a bit too much to create 10 content types, for 10 feed-type nodes don't you think?

Why would you create that many importers that need to be attached to content types when there is a stand alone form? I am serious, I would love to hear your use case...

I am talking about the forms that appear on mysite.com/import if you *don't* choose a content type in the Basic settings.

Subscribe. I have experienced the same issue.

I don't like the idea of creating a separate content type for each feed document.

This is my scenario (I originally erroneously thought it was a pathauto issue and reported it here: http://drupal.org/node/857904#comment-3218378)

1) Drupal 6.17, Pathauto 6.x-1.3, Feeds 6.x-1.0-beta3

2) Create 2 Content Types (let's say "TypeA", "TypeB")

3) The two content types share a CCK field ("Original Article") ...
which happens to be a url link to the original url of the individual
item included in the feed

4) Items of the content types will be created by the two separate RSS Feeds
via Feeds Module. (Both Feed Importers are tied to the same Content Type called "Feed"; the individual feed items should be content type "TypeA" and "TypeB")

5) In Pathauto "node path settings," set:
"Pattern for all TypeA paths:"
typea/[title-raw]
"Pattern for all TypeB paths:"
typeb/[title-raw]

6) Result: Both TypeA and TypeB nodes are being created as TypeB content types and pathauto: typeb/[title-raw]

Only way to get it to work so far is to have the Feed Importers point to different content types for the feed definition -- not desirable at all.

I had a look at the basic settings but there is no way to not select a content/node-type for the node processor.
If I go to /import I only see the two feed importers I have created... with links to create a node... nothing else.

You need to look under admin/build/feeds and edit (override) one of the importers there.

This same problem is really hampering a project I am trying to set up. Audio feeds and news feeds, two importers created from scratch, each set up attached to a feed item, each set to create a node of a particular custom type for items from the feed, but the system is ignoring one node type, no matter what I have tried. Even disabling one feed importer and importing with the other does not help! If I ever knew that the Feeds module was going to do this, I would not have spent any time with it. Any help would be deeply appreciated!

Importer A--> Feed A--> nodes containing audio links of different categories--> custom content type "audio feed"--> data presented using Views with an exposed filter for taxonomy term in a custom taxonomy library for this node type.

Importer B--> Feed B--> nodes containing various news items of different categories--> custom content type "news item"--> data presented using Views with an exposed filter for taxonomy term in a custom taxonomy library for this node type.

There can be multiple feeds of type A or type B, but in order to keep the data and tags separate so that they can be presented logically in different parts of the site, they each need have their own content type.

The bottom line is, that Feed A and Feed B are both creating nodes of one type, even though they are configured to create nodes of different types. Therefore I believe that this is a bug, and not a feature request. Please help!

Okay, I might be sounding like a pain in the butt, however if I cannot classify content aggregated from other places, then what is the use? I guess there are some sites where it doesn't matter much.

Anyway, I do believe that the Feeds module has potential, however for the project I am working on, I have had to go with the Aggregation module. That module, while a little clunky, has allowed me to add my own taxonomy term to each feed, and therefore I can use that method to present the various categories of aggregated data. It also has its own built-in image grabber, and maintains a link to the original site post as well.

I guess I will stop back here when Drupal 7 is released, to see what feeds is doing.
Thank you!

And I HATE to sound like a complainer with all the hard work put in by the maintainer .... but

I miss basic D5 FeedAPI ... big time.

After dealing with the unique content type for each feed importer issue, I am now dealing with Feeds creating duplicates of every feed item, every refresh. I have yet to figure out how to stop that. No combination of "Replace existing nodes" or "Update existing nodes (slower than replacing them)" is addressing it either.

</end ungrateful-sounding rant>

I was experiencing the problems described here (multiple Google calendar feeds designated for multiple event content types on a 1-to-1 basis, but getting an odd mix of where they actually ended up).

My solution is probably overkill, but it was the only way I managed to get this to work.
1. Create a content type for each event (i.e. event_leaders, etc.)
2. Create a content type for each feed type (i.e. event_iCal_leaders, etc.)
3. Create each feed FROM SCRATCH (no cloning!) - I haven't been able to do enough testing to declare this a bug, but I suspect it is.

Now, every event goes exactly where it's supposed to. This is not really an acceptable solution (10 content types and full manual configuration of five feeds), but it gets the job done right now.

-Brian

#14: Why did you not use the standalone form?

suscribing

Did this work? And what fields do your extra feeds require. I'm really struggling with Feeds.

#18
The stand-alone form had no parent feed nid which I was using to distinguish feeds. I have some feeds which are okay as they are, others I want to filter with tamper.

Searching for Drupal 7 issues I missed this thread and posted a similar feature request at http://drupal.org/node/1611750