You are here

README.txt in FeedAPI 5

Same filename in this branch
  1. 5 README.txt
  2. 5 feedapi_inherit/README.txt
Same filename and directory in other branches
  1. 6 README.txt
FeedAPI
-------

The FeedAPI module group has several purposes:

1) Provide a basic aggregation module that is able to handle various parsers
   and processors and give the user the ability to change how feed items are
   represented and how incoming feed URLs are parsed.
2) Provide an API for writing parsers and processors. FeedAPI defines an
   exact requirement set for both parsers and processors. For more details,
   see the developer documentation at http://groups.drupal.org/node/5301.
3) Provide a common base for existing aggregator-purpose modules to avoid
   the overlapping of tasks (for example, parsing and downloading).

Known issues:
- Parser SimplePie submodule may be incompatible with other modules which include
  SimplePie (for example Activity Stream)
- Do not use FeedAPI and poormanscron together (http://drupal.org/node/235328)


Sub-modules
-----------

If you only turn on FeedAPI module on the admin/build/modules page,
you won't get the functionality that you expect from an aggregator module.

If you don't want to bother about the fine print here, a good standard configuration
is FeedAPI, FeedAPI Node and SimplePie parser (don't forget to download the SimplePie
package from http://www.simplepie.org). If you use views module, also turn on FeedAPI 
Node Views. 

Here is the purpose of each sub-module:

1) FeedAPI - This is the main module, you should always enable it.
2) FeedAPI Aggregator - If you like how the core aggregator module handles news
   items, you should enable it. This module simply tries to behave like the core
   aggregator, but it benefits from the pluggable parsers system and has more
   configuration possibilities.
   (processor)
3) FeedAPI Node - If you like the idea of feed items are nodes, you should
   enable this.
   (processor)
4) FeedAPI Node Views - Use this to handle feed node items with views module.
5) FeedAPI Inherit - If you use og module and taxonomy modules and you would
   like to pass the information of these modules between the feeds and feed
   items this processor can handle it.
6) Common Syndication Parser - Only enable this if you have a PHP5-powered
   site. If PHP5 is present, this parser has excellent performance.
   (parser)
7) SimplePie Parser - This is the parser for you if your site runs on PHP4.
   In some cases it is better and more established than the
   Common Syndication Parser. Because of the Drupal CVS policy, the
   repository should not contain 3rd party source code, so:
   -----------
   WARNING: before you turn on SimplePie Parser, please download
   SimplePie from http://www.simplepie.org and move simplepie.inc file
   to feedapi/parser_simplepie directory.
   -----------
   (parser)

To get things working you must enable at least one parser and one processor.

Start using the module
----------------------

Feeds are based on content-types. As you enable the processors one
content-type is created for each processors. Likely you want to use these
pre-configured content-types for creating the feeds.
If you would setup more complex processor configuration,
please visit admin/content/types and edit/add the existing content-types. About
the content-type editing: make sure that "Is a feed content type" checkbox is
turned on. Below that checkbox you will find the parsers and processors
configuration.

Create your first feed
----------------------

Visit the node/add page and select the content-type you like. Supply the
URL and hit Submit. Then select Refresh at the feed node, if you want to see the
items.

Developers
----------

parser_simplepie.module contains a stop gap patch that won't be necessary for most 
installations (issue http://drupal.org/node/205706). If you would like to use automatic
feed type detection, please remove the lines

// Stop gap for simplefeed.inc version <= 1.1
return "XML feed";

from your parser_simplepie.module and use simplepie > 1.1 version, if you experience 
a whitescreen on refreshing feeds.

Author/credits
--------------

* The author of the module is Áron Novák (http://drupal.org/user/61864).
* The module uses SimplePie (www.simplepie.org).
* The module refactored Aggregation module's
  (http://www.drupal.org/project/aggregation) parser.
* Alex Barth (http://drupal.org/user/53995) provided very useful patches.
  (The concept of setting storage and feed = node, plus the feedapi_aggregator,
  are almost entirely his work.)
* Jose Reyero (http://drupal.org/user/4299) refactored the whole cron part
  of the module and he provided performance-booster patches.
* I got lots of useful responses from my mentors
  Ken Rickard, Károly Négyesi (chx), David Norman (deekayen), and Alex Barth.
--
This is a Summer of Code 2007 sponsored project.

File

README.txt
View source
  1. FeedAPI
  2. -------
  3. The FeedAPI module group has several purposes:
  4. 1) Provide a basic aggregation module that is able to handle various parsers
  5. and processors and give the user the ability to change how feed items are
  6. represented and how incoming feed URLs are parsed.
  7. 2) Provide an API for writing parsers and processors. FeedAPI defines an
  8. exact requirement set for both parsers and processors. For more details,
  9. see the developer documentation at http://groups.drupal.org/node/5301.
  10. 3) Provide a common base for existing aggregator-purpose modules to avoid
  11. the overlapping of tasks (for example, parsing and downloading).
  12. Known issues:
  13. - Parser SimplePie submodule may be incompatible with other modules which include
  14. SimplePie (for example Activity Stream)
  15. - Do not use FeedAPI and poormanscron together (http://drupal.org/node/235328)
  16. Sub-modules
  17. -----------
  18. If you only turn on FeedAPI module on the admin/build/modules page,
  19. you won't get the functionality that you expect from an aggregator module.
  20. If you don't want to bother about the fine print here, a good standard configuration
  21. is FeedAPI, FeedAPI Node and SimplePie parser (don't forget to download the SimplePie
  22. package from http://www.simplepie.org). If you use views module, also turn on FeedAPI
  23. Node Views.
  24. Here is the purpose of each sub-module:
  25. 1) FeedAPI - This is the main module, you should always enable it.
  26. 2) FeedAPI Aggregator - If you like how the core aggregator module handles news
  27. items, you should enable it. This module simply tries to behave like the core
  28. aggregator, but it benefits from the pluggable parsers system and has more
  29. configuration possibilities.
  30. (processor)
  31. 3) FeedAPI Node - If you like the idea of feed items are nodes, you should
  32. enable this.
  33. (processor)
  34. 4) FeedAPI Node Views - Use this to handle feed node items with views module.
  35. 5) FeedAPI Inherit - If you use og module and taxonomy modules and you would
  36. like to pass the information of these modules between the feeds and feed
  37. items this processor can handle it.
  38. 6) Common Syndication Parser - Only enable this if you have a PHP5-powered
  39. site. If PHP5 is present, this parser has excellent performance.
  40. (parser)
  41. 7) SimplePie Parser - This is the parser for you if your site runs on PHP4.
  42. In some cases it is better and more established than the
  43. Common Syndication Parser. Because of the Drupal CVS policy, the
  44. repository should not contain 3rd party source code, so:
  45. -----------
  46. WARNING: before you turn on SimplePie Parser, please download
  47. SimplePie from http://www.simplepie.org and move simplepie.inc file
  48. to feedapi/parser_simplepie directory.
  49. -----------
  50. (parser)
  51. To get things working you must enable at least one parser and one processor.
  52. Start using the module
  53. ----------------------
  54. Feeds are based on content-types. As you enable the processors one
  55. content-type is created for each processors. Likely you want to use these
  56. pre-configured content-types for creating the feeds.
  57. If you would setup more complex processor configuration,
  58. please visit admin/content/types and edit/add the existing content-types. About
  59. the content-type editing: make sure that "Is a feed content type" checkbox is
  60. turned on. Below that checkbox you will find the parsers and processors
  61. configuration.
  62. Create your first feed
  63. ----------------------
  64. Visit the node/add page and select the content-type you like. Supply the
  65. URL and hit Submit. Then select Refresh at the feed node, if you want to see the
  66. items.
  67. Developers
  68. ----------
  69. parser_simplepie.module contains a stop gap patch that won't be necessary for most
  70. installations (issue http://drupal.org/node/205706). If you would like to use automatic
  71. feed type detection, please remove the lines
  72. // Stop gap for simplefeed.inc version <= 1.1
  73. return "XML feed";
  74. from your parser_simplepie.module and use simplepie > 1.1 version, if you experience
  75. a whitescreen on refreshing feeds.
  76. Author/credits
  77. --------------
  78. * The author of the module is Áron Novák (http://drupal.org/user/61864).
  79. * The module uses SimplePie (www.simplepie.org).
  80. * The module refactored Aggregation module's
  81. (http://www.drupal.org/project/aggregation) parser.
  82. * Alex Barth (http://drupal.org/user/53995) provided very useful patches.
  83. (The concept of setting storage and feed = node, plus the feedapi_aggregator,
  84. are almost entirely his work.)
  85. * Jose Reyero (http://drupal.org/user/4299) refactored the whole cron part
  86. of the module and he provided performance-booster patches.
  87. * I got lots of useful responses from my mentors
  88. Ken Rickard, Károly Négyesi (chx), David Norman (deekayen), and Alex Barth.
  89. --
  90. This is a Summer of Code 2007 sponsored project.