Turn external feed entries into content items
Project description
Feedfeeder has just a few things it needs to do:
Read in a few ATOM feeds (not too many).
Create FeedfeederItems out of the entries pulled from the ATOM feeds. Any feed items that contain enclosures will have the enclosures pulled down and added as File items to the feed item.
This means figuring out which items are new, which also means having a good ID generating mechanism.
Wait, no existing product?
There’s a whole slew of RSS/ATOM reading products for zope and plone. None of them seemed to be a good fit. There was only one product that actually stored the entries in the zope database, but that was aimed at a lot of users individually adding a lot of feeds, so it needed either a separate ZEO process (old version) or a standalone mysql database (new version).
All the other products didn’t store the entries in the database, were old/unmaintained/etc.
In a sense, we’re using an existing product as we use Mark Pilgrim’s excellent feedparser (http://feedparser.org) that’ll do the actual ATOM reading for us.
Product name
The product feeds the content of ATOM feeds to plone as document/file content types. So “feedfeeder” sort of suggested itself as a funny name. Fun is important :-)
Product structure
I’m using archgenxml to generate the boiler plate stuff. There’s a ‘generate.sh’ shell script that’ll call archgenxml for you. Nothing fancy.
- The feedfeeder’s content types are:
folder.FeedfeederFolder
item.FeedfeederItem
How it works
A feedfeeder is a folder which contains all the previously-added feed entries as documents or files. It has a ‘feeds’ attribute that contains a list of feeds to read.
Feedparser is called periodically (through a cron job?) to parse the feeds. The UID of the items in the feed are converted to a suitable filename (md5 hex hash of the atom id of the entry), that way you can detect whether there are new items.
New items are turned into feed items.
Scheduled updates for feed folders
Zope can be configured to periodically trigger a url call. In zope.conf you can use the <clock-server> directive to define a schedule and url with the following data:
<clock-server> method /path_to_feedfolder/update_feed_items period 3600 # seconds user admin password 123 host localhost:8080 </clock-server>
Tests
The look-here-first test is the doctest at ‘doc/testDocIntegrationTests.txt’.
Testing is best done with zope’s zopectl. ‘instancemanager <projectname> –test feedfeeder’ will do that for you if you’ve set up instancemanager. Otherwise ‘bin/zopectl test -s Products.feedfeeder’.
1.0 beta 4 (20 May 2008)
Eggification: you can now install it as the Products.feedfeeder egg. [maurits]
1.0 beta 3 (13 May 2008)
In the tests, use plone_workflow explicitly, so it is easier to test on both Plone 2.5 and 3.0. [maurits]
Make update_feed_items available in the object_buttons for Plone 3, using new small @@is_feedcontainer as condition. [maurits]
Avoid deprecation warnings for events and interfaces. [maurits]
Remove semicolon in page template that broke in Plone 3. [maurits]
Fix imports so they work in Plone 3 as well, without deprecation warnings. [derstappenit]
1.0 beta 2 (2 January 2008)
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Hashes for Products.feedfeeder-1.0beta4.tar.gz
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 | 7c3bee426991da7784f54df8fb24df3fbfcb8d6175064e1af2d51d2d1e5ec04c |
|
| MD5 | 4313426ee32c8a8451714e071a324514 |
|
| BLAKE2b-256 | ee44e3a88d19ab9d6a7a75a0b15f37b51cd2958e5fa63dcf3c15d5b2c21e9dfa |
