Preparation

Last updated November 30, 2009. Created by elfur on October 27, 2008.
Edited by taite11, JohnNoc, mlncn, Markus Sandy. Log in to edit this page.

After enabling the required modules you should prepare the following:

An RSS Feed - If you don't have a feed to begin with you might consider using services like:
- Dapper - which will turn pretty much any website into an RSS-feed.
- Yahoo Pipes - a service that lets you manipulate your feed in many ways.
A Content-Type that will be used to store all the feed-items.
admin/content/types/add
If you plan to map anything from the feed to nodes of this content type, set up the CCK-fields and options for those fields. Remember all the settings here will apply to the nodes that will be created later on. Do not touch the Feed API collapsible fieldset here. Especially make sure that the "Is a feed content type" checkbox is not checked.
- comments - the nodes that will be created inherit the settings provided here
- publishing options - Same here. If you don't want your nodes on your frontpage use the settings accordingly.
A Vocabulary by which you will categorise your feed-items.
admin/content/taxonomy/add/vocabulary
Don't forget to enable it for the Content-Type you'll be using.
A User - This step is optional.
admin/user/user/add
By default all the nodes that will be created will carry the author-information of the user that entered the feeds URL. If you want a different authoring informatoin like "RSS-Bot" - create a new user accordingly. You may find it helpful in custom Views if you do create a user like "RSS-Bot" that has permissions to create feed items. E.g. You could create a view of all items created by user "RSS-Bot".
FeedAPI Settings - Adjust to your needs.
admin/settings/feedapi
If you'd like to see embedded images or videos in the content that you aggregate, check the "Allow all HTML tags" checkbox.
Edit Feed content-type. You may like to edit the built-in Feed content-type. Let's see what can be adjusted.
- FeedAPI Settings - Check out this collapsible fieldset.
  - Is a feed content type - This checkbox should be checked.
  - Default settings - Remember that if you Update existing feed items all changes you make to the nodes will be restored to the feed's initial state. Example: If you edit the Title or Body of that node it will be restored on the next update. If the feed changes and you want the latest state mirrored on your site, use the update setting.
  - Parser settings - IMPORTANT!!! Here you tell drupal what method to use to suck the feed-items in. If you are using PHP5 you can use the Common syndication parser module. alternativly or if you run under PHP4 you can use the SimplePie parser module.
    At least one Parser has to be active! Do not enable more than one parser, unless you really know what you want.
  - Processor settings - FeedAPI Node must be turned on here. According to your plans, you can enable more processors here to gain more features. For example FeedAPI Inherit, see its README for more.

Comments

Is a feed content type clarification please

Posted by manogolf on November 15, 2008 at 10:48pm

I am using 6.x and confused by what is stated here.

At instruction item 2 it states "Especially make sure "Is a feed content type" checkbox is not turned on."
After adding a new content type then expanding the Feed API menu this checkbox is the first selectable option.

At instruction item 6 it states "Is a feed content type should be checked."

Scrolling further down add new content type expanded Feed API menu and under Processor Settings Feed menu API Nodes is expandable. The first selectable option here is a checkbox asking if you want to enable the feedapi_node processor on this feed. Is this checkbox a reference too instruction item 6?

To check or not to check; and where?

Thanks

Answer My Own Request

Posted by manogolf on November 18, 2008 at 5:22am

It's all there but not easily understood; by me anyway.

After a lot of trial and error over the past several weekends I've alas met with some success. What I didn't understand is that you must create three nodes (two minimum) to make this work.

First step is adding a new content type (or node). I wanted to create an RSS feed of 3rd party videos so I named the new content type "3rd Party Video Item". This node requires very little editing. Only a name, a machine readable name, and a short description, nothing more, in fact don't even open the Feed API menu here. Save and move on.

Second step is optional (you can use the default content type "Feed" if you want). Create another new content type. I named this new node 3rd Party Video. After filling out the machine readable name and a short description I skipped down to the Feed API menu and expanded it. Here you check the box "Is feed a content type". Open the Parser Settings and select which parser. I chose simple pie after learning Common Syndication Parser will not map everything needed. This simple bit of knowledge held me back for hours. Next open the menu "FeedAPI Node - create nodes from feed items" and check the fist box "Enable". Keep scrolling to "Default settings" and use the drop down menu for "Node type of feed items:". Here I selected "3rd Party Video Item" (select whatever you named your node in the first step). If you are mapping anything do it in this node. You are done, save!

Third step is "Create Feed" as instructed on the next page.

I have now achieving the outcome wanted however categorizing the nodes into something other than a new or existing book or onto the front page is something I've not figured out yet. I'm off to post help for this. I'm thinking the solution lies in taxonomy but not really sure.

Thanks and further clarification

Posted by jeffschuler on January 20, 2009 at 5:32pm

Thanks for this, manogolf; you made the instructions much clearer for me.

To simplify just a bit more, I might reinforce that only two Content Types are necessary, and that's likely good starting point for most people:

Add a Content Type that will be a "Feed Item", and ignore all FeedAPI settings for it.
Configure the "Feed" Content Type that the module creates. This one is configured as a feed. It needs a parser, and its "Node type of feed items:" should be set to your new "Feed Item" Content Type.

When there's a need to parse different feeds in different ways, then one might start creating different Feed and Feed Item Content Types. Until then, two generic Content Types will do.

Further elaboration on item 4

Posted by elfur on January 25, 2009 at 9:06pm

Can anyone elaborate on item 4? I need to know further about how to assign a permanent user to author Feeds. I don't want to use anything like "RSS-bot," is that my only option?

thanks

/elfur.is

Promoted items dialog overrides Content types publishing options

Posted by alienresident on February 4, 2009 at 4:49pm

Note: Promoted items dialog overrides the Content type's default publishing options.

I was having a problem with my feed promoting itself to the homepage every time it was updated even though the content was set not to promote to front page.

Make sure that in "FeedAPI Node - create nodes from feed items" > "Promoted items" dialog is blank instead of the default 3 and it will not promote itself to the homepage. There is a note below the dialog box but it is not 100% clear what it does.

Alternatively if you want it to promote itself to the homepage make sure it is not set to 0
See for additional help:
http://drupal.org/node/179884

This is not a reply to my question

Posted by elfur on February 15, 2009 at 2:52pm

I was asking for support for permanent assign of author, not about promoted items. I was referring to item 4 in the original handbook entry.

/elfur.is

Don't forget to set permissions

Posted by cogdog on August 6, 2009 at 9:52pm

This may be obvious to seasoned drupal folks, but make sure your admin account has both privileges set in roles for this module-- I had not checked the "access advanced FeedApI features" since I did not know what they were, and was trying to do just a basic set up for one feed-- w/o this you never see the FeedAPI settings, which to me does not seem like an "advanced" feature

/* ********************************************
Alan Levine: A Cog, a Dog, A Blog
Go Dog Go! http://cogdogblog.com
******************************************** */