Magpie RSS and WordPress Feeds

March 7th, 2005

This is a continuation of my discussion regarding the CARP solution to RSS aggregation. I’ve concluded that the CARP solution is too limited for handling the character encoding I throw at it. The particular character-encoding problem I encountered was the substitution of a question mark for every apostrophe in the WordPress item title tag and I am not sure whether to blame the WordPress RSS feed or CARP. The reason for this inadequacy (as I see it) is that it does not handle ATOM feeds with their more advanced character encoding abilities. I have experimented with Magpie RSS and found it handles the ATOM feeds gracefully and that character encoding has not been an issue on my ATOM feeds.

The weakness of Magpie is its lack of advanced functions to format the cached feeds. This lack of pre-designed functionality is a strength because Magpie is designed with the PHP programmer in mind, allowing a great deal of control with a little knowledge of PHP. It also seems to load more quickly when the feed has not been cached, but this is based on an observation rather than benchmarks. Overall, I find that for my purposes Magpie is by far the best solution. For those with little or no programming experience, CARP offers a quick way to incorporate your WordPress posts throughout the rest of your web site, but Magpie will help you do it with fewer character encoding issues.

By the way, if you are wondering how to use the Magpie technology built into the latest version of Wordpress, check out Secrets of WP Theming: Part 3 by Chris Davis.

Entry Filed under: RSS Syndication, WordPress

Bookmark This: del.icio.us:Magpie RSS and WordPress Feeds digg:Magpie RSS and WordPress Feeds newsvine:Magpie RSS and WordPress Feeds blinklist:Magpie RSS and WordPress Feeds furl:Magpie RSS and WordPress Feeds reddit:Magpie RSS and WordPress Feeds blogmarks:Magpie RSS and WordPress Feeds

2 Comments

  • 1. Antone Roundy  |  May 18th, 2005 at 1:52 pm

    The question marks in CaRP’s output may be caused by it converting from UTF-8 to ISO-8859-1, which is PHP’s default encoding. You can prevent the conversion by adding the following configuration line:

    CarpConf(’encodingout’,'UTF-8′);

  • 2. CARP RSS Aggregator - Des&hellip  |  February 21st, 2006 at 1:53 pm

    [...] This conversation continues with regard to Magpie. [...]


About Harvey Ramer

CSS Web design, e-commerce Web design, and internet marketing issues from the desk of Harvey A. Ramer at Design Delineations.

View Harvey Ramer's profile on LinkedIn

Reader/Customer Feedback

Harvey Recommends

Accolades

Design Notes: A CSS Web Designer’s Blog at Blogged

Calendar

March 2005
M T W T F S S
« Feb   Apr »
 123456
78910111213
14151617181920
21222324252627
28293031  

Most Recent Posts