PloneRSS

Project Description

Project resources

• Documentation
• Releases
• Issue tracker
• Roadmap
• Contact address

PloneRSS is designed to import news items from RSS or RDF feeds from remote sites and to insert them into a local ZODB database. The user interface consists of four modules;

• rss_item, which is created each time a new RSS news item is found

• rss_feed, these items define where RSS news items can be found (created by the end-user)
• rss_instance, create one of these in a folder where you'd like to see RSS news items displayed. It will allow you to select one or more feeds to be displayed in an appropriate 'portlet'
• rss_manager, the root of all .. news. Every time you look at this page, the system will try to sync your news feeds with their respective remote sources.

Inspiration

• CMFSin

• CMFNewsFeed
  
• CMFFeed - which was my previous attempt to solve this 'problem'.

The Solution

And along came ArchGenXML and made proper products something we could reasonably envisage being easy to design and maintain. We have incorporated the following aspects into the design: (you can grab the XML design file here)

• End users get to design which feeds they want to see. Whether the feeds need to be published or not is controlled by a Yes/No option in the rss_manager instance.
• End users get to control which feeds are displayed on which pages by inserting instance items in folders to which they have write access.
• When an instance is being created / edited, the user is presented with a complete list of existing feeds so's to avoid any duplication or drawing down of the same feed twice.
• Feeds are drawn down by the rss_manager component and stored in a MySQL database. News items are then extracted and stored in instances with feed items that reference the specific feed. (one news item is stored per plone instance only to avoid news item duplication)

Requirements

Plone 3.0.x or Plone 3.1.x.

Screenshots

 

Self-Certification

[X] Internationalized

[ ] Unit tests

[X] End-user documentation

[ ] Internal documentation (documentation, interfaces, etc.)

[X] Existed and maintained for at least 6 months

[X] Installs and uninstalls cleanly

[ ] Code structure follows best practice