Download Size md5 hash
feeds-6.x-1.0-alpha12.tar.gz 164.23 KB ab2be04599a7d5a84c906d44d78b2ef9
feeds-6.x-1.0-alpha12.zip 202.13 KB fc80e926d09226829972950bd2b95741
Official release from tag: 6.x-1.0-alpha12
Last updated: December 24, 2010 - 22:56

Changes

  • #600584 alex_b: PubSubHubbub support (see notes below).
  • alex_b: Debug log (see notes below).
  • alex_b: Add sourceSave() and sourceDelete() methods notifying plugin
    implementers of a source being saved or deleted.
  • #717168 nicholasThompson: Fix feeds UI JS doesn't select labels correctly.
  • #708228 Scott Reynolds, alex_b: Break FeedsImportBatch into separate classes.
    NOTE: Review your FeedsFetcher implementation for changes in the
    FeedsImportBatch class, small adjustments may be necessary.
  • alex_b: Support mapping to OpenID, using OpenID as a unique mapping target.
  • alex_b: Handle exceptions outside of Importer/Source facade methods.
  • #600584 alex_b: Use Batch API.
    NOTE: third party plugins/extensions implementing FeedsProcessor::process(),
    FeedsProcessor::clear() or FeedsImporter::expire() need to adjust their
    implementations. Modules that directly use Feeds' API for importing or
    clearing sources need may want to use feeds_batch_set() instead of
    feeds_source()->import() or feeds_source()->clear(). See notes below.

New: PubSubHubbub support

Feeds supports the PubSubHubbub publish/subscribe protocol. Follow these steps
to set it up for your site.
http://code.google.com/p/pubsubhubbub/

  • Go to admin/build/feeds and edit (override) the importer configuration you
    would like to use for PubSubHubbub.
  • Choose the HTTP Fetcher if it is not already selected.
  • On the HTTP Fetcher, click on 'settings' and check "Use PubSubHubbub".
  • Optionally you can use a designated hub such as http://superfeedr.com/ or your
    own. If a designated hub is specified, every feed on this importer
    configuration will be subscribed to this hub, no matter what the feed itself
    specifies. If you use a designated hub you can lower the minimum refresh time to about 4 weeks.

Important Note

What's not yet implemented is an automatic adjustment of the refresh frequency. Say you configure a Feeds importer to update feeds every 30 minutes. If a particular feed is successfully subscribed to a hub, it will continue to download every 30 minutes. This is an issue that will be addressed in a future release - see #722168: PSHB: handle hub.lease_seconds.

This means that PubSubHubbub will be a good joice if you can make sure that all of the feeds on a particular importer support PubSubHubbub (e. g. by using a designated hub). In these cases you can lower the minimum refresh time of the importer dramatically (to about 4 weeks). Every time a feed is refreshed it will do a full update from the original source but it will also renew the subscription with the hub. A particular subscription is also renewed every time a notification for it is received.

New: debug log

Set the Drupal variable 'feeds_debug' to TRUE (i. e. using drush). This will
create a file /tmp/feeds_[my_site_location].log. Use "tail -f" on the command
line to get a live view of debug output.

Note: at the moment, only PubSubHubbub related actions are logged.

New: Batch API

Batch API support requires all implementers of FeedsProcessor::process(), FeedsProcessor::clear() or FeedsImporter::expire() to adjust their implementations. At the very least they need to return FEEDS_BATCH_COMPLETE. Implementing full batching support is optional. See plugins/FeedsNodeProcessor.inc for an example.