FeedCache will retrieve, cache and store locally a list of RSS feeds that you can then display on your WP site. This prevents multiple HTTP requests with each page load since the feeds can be read from the cache file.
- Rubygems with the following gems installed:
(If you are hosted with Dreamhost you have these gems already. If you are hosted elsewhere you will need to check. If you run a VPS or dedicated machine like me, then just install them via
sudo gem install)
- CRON access
If you are upgrading from a version of FeedCache prior to v0.9.8, please
deactivate and delete your existing feedcache plugin directory and follow the new
Deactivate the previous version of FeedCache through your WordPress plugins menu
Upload the new feedcache-cron.rb, feedcache.php and complete lib/ directory files to your existing feedcache directory. You do not need to overwrite your feedcache-config.yml file.
Enter the correct FEEDCACHE_DIR variable in the feedcache-cron.rb script
Go to Options -> FeedCache Options and update your FeedCache settings
- Why would I need this plugin?
If you are using your WP installation to display other website’s RSS feeds, this will save HTTP requests and improve page load times for your users. By using a CRON job to fetch and format the feeds, the user will not have to wait during page load for the feed to be updated.
- Will FeedCache work with Atom feeds?
Yes! FeedCache will work with both RSS and ATOM feeds.
- Can I receive error emails from the CRON process?
Yes, just set CRON_EMAILS = true in the feedcache-cron.rb script. Error emails are turned off by default.
- Can I have more than 10 RSS Groups
Yes, but you’ll need to manually edit the feedcache.php file. Find the following line:
and change the number 10 to whatever number you need. (Just don’t go overboard, 🙂 ) Take note that when you upgrade the
FeedCache plugin in the future, you’ll need to update this number every time.
- Bugfix: WP database password wasn’t found properly in CRON script
- widgetize plugin
- store all config settings in the yaml file. dont use a separate master-config.txt file
- bugfix for missing false option on settings page
- bugfix for truncation of feed titles during CRON job
- strip non-ascii characters from title output
- added plugin credits to admin page footer
- updated credential levels for adding admin subpage
- update WP options to only use 2 option fields via an options array
- use feed_tools gem for parsing
- single YAML config file
- store RSS cache into the WP database
- allow for up to 99 feed groups now
- added option to open feed links in a new browser window
- bugfix for issue where files/ directory wasn’t being included in the WordPress download
- fixed issue with truncation of feed titles to include ellipses
- allow the user to set the number of RSS groups (from 1 – 10)
- moved config and cache files to the new files/ directory
- created a new master-config file for general settings
- fixed an issue with weird links using ATOM feeds from blogspot
- now using feedparser library to parse both RSS and ATOM feeds
- cleaned up configuration so only the feedcache plugin path will need to be entered
- fixed bug with config files not being set properly
- rename broken screenshot file
- Allow up to 4 different cache files to allow for multiple instances of the plugin per theme
- Fix some admin page layout issues
- Add option to not send CRON error emails
- Fix broken feed formatting options
- Added user-agent to the CRON script to force RSS-only feeds from feedburners SmartFeed service
- Lower the error output level from the CRON job again
- Lower the error output level from the CRON job
- Use a temp file when grabbing new cache
- Updates to the Ruby CRON script for better error handling
- Fixed bug that would cause PHP header errors during login/logout
- Added option to manually override the number of feed items to display on a per feed basis
- Added option to manually override the feed text formatting option on a per feed basis
- Updated README file
- Added option for manually named feed titles
- Initial Release