If aggregator has already been used on a site, all existing feeds must be deleted and reentered (after enabling feedparser of course) or no feeds are generated. If an existing feed is reentered without deleting the original, a duplicate entry error occurs.

Install instructions should point out that all existing feeds should be deleted and then reentered after the original aggregator is disabled and feedparse enabled.

Comments

budda’s picture

budda
Primary language English
Location Cheshire
commented
Status: Active » Postponed

The feedaggregator_item.module is a processor to continue processing the old original feeds from Drupal. However it is not complete yet - but WILL do as you wish without having to delete and re-add your feeds.

Documentation will cover this once it's completed.

Hang in there ;-)

zoon_unit’s picture

zoon_unit commented

Thanks for the update, but I guess I'm a bit confused. Doesn't the feedaggregator_node. module also use the feeds from the old aggregator tables to process feeds? I fully intended to use the node module. (that's the great feature after all!)

I was under the assumption that feedparser alters the aggregator tables for its own processing. (I don't see any feedparser tables)

So, once the aggregator_feed module is complete, will the feeds from both processors be kept separate and distinct from one another?

This will need some explaining in the install docs. :-)

budda’s picture

budda
Primary language English
Location Cheshire
commented
Assigned: Unassigned » budda
Status: Postponed » Active

By default, upgrading from the aggregator.module to the feedparser package will mean feeds will continue to parse as usual - as aggregator item's NOT the new nodes.

Currently there is no way to change a feeds processor once it has been set - because a feed would then be confused with two types of feed items to manage.

Another alternative is to export the old feeds out using OPML, then import them in to Feedparser - but selecting the default processor as Nodes.