Maybe this issue is the same as http://drupal.org/node/1279492 but I am not sure.

I am trying to achieve the following: import regularly the content of an rss feed in a specific node type (to be able to use it in views and to map rss fields with specific fields of the node type).

When I clone the feed importer and modify the settings for node processor and choose "content type":mycontenttype (which I have create as a separate content type), if I then create a feed, it import the content as "feed item" and not "mycontenttype". I tried also not using the cron configuration (import on creation), but it still doesn't work.

Anyone could help?

Thanks in advance

Comments

derekw’s picture

Same issue, subscribing.

Jason Dean’s picture

I've been battling with this issue today. Two things to check:

1) Have you tried latest dev release?
2) Are you using Unique Field module by any chance? (and did you apply the patch here?)

The problem went away for me when I upgraded to latest dev and removed the patch mentioned above. Not sure yet exactly what fixed things.

amnesia623’s picture

Same issue here.

Applied latest dev and not using the unique field mod.

codejuggler’s picture

Component: Feeds Import » Code
Issue summary: View changes

I see the same issue here.

Two feed importers with two different content types, but on import they will often use the wrong one.

I've not done enough testing, but it feels like the last feed that was imported defines the content type that will be used for the next one. Some kind of shared variable thing.

MegaChriz’s picture

Status: Active » Postponed (maintainer needs more info)

If you enable the module "Feeds Import" two importers ("Node import" and "User import") are created.
If you enable the module "Feeds News" two content types ("Feed" and "Feed item") and two importers ("Feed" and "OPML") are created.

Both modules exists to demonstrate the functionality in Feeds, though you could also directly use them. Except for the automated tests, the modules do not contain custom code, only configuration code. This means you do not gain extra functionality by enabling them, only preconfigured importers and/or content types.

@codejuggler
With which preconfigured importer you encountered the issue that items were imported for the wrong content type?

twistor’s picture

Status: Postponed (maintainer needs more info) » Closed (cannot reproduce)