The advent of December has seen the release of WordPress 2.7, and I’ve been working to get out a new release of FeedWordPress before I leave to visit family for the holidays, which incorporates the couple of small compatibility fixes. In addition, I’ve added some interface improvements (to help FWP look a bit less out-of-place in the new user interface), and a couple of fixes of bugs reported or detected in the process of testing.
Also, I created a cheesy little logo icon for FeedWordPress to fit in with the general practice in the WordPress 2.7 interface. It’s not actually intended to be a distinctive logo for FeedWordPress (it just takes a syndication icon and the WordPress logo and puts them together), but it should at least visually mark off the FeedWordPress configuration interface from the rest of the Dashboard. Hope you like it.
First things first, though. A WordPress update has come out, which has caused a number of e-mails — just like every WordPress release does –from people who upgraded WordPress to the latest version, and, in the process, inadvertently downgraded their MagpieRSS to the old, busted version included with WordPress. If you have noticed strange problems with syndicating feeds (especially Atom feeds) immediately after making the upgrade, like those described in my old post about upgrading to WordPress 2.5, then you need to re-copy the MagpieRSS upgrades from your FeedWordPress installation to the
wp-includes/ subdirectory of your WordPress installation. (The old post discusses this issue, and the steps for fixing it, in more detail.)
Now, then. Here are the major changes since the release of FeedWordPress 2008.1105:
WORDPRESS 2.7 COMPATIBILITY: FeedWordPress has been tested for
compatibility with the newly released WordPress 2.7. WordPress 2.7 has
deprecated the Snoopy library for HTTP requests, which caused a fatal
error for users who had not installed the MagpieRSS upgrade (or whose
installation of the MagpieRSS upgrade was overwritten by a recent update
of WordPress). FeedWordPress now handles things gracefully when Snoopy
is not immediately available. The 2008.1214 fix also releases a minor interface
bug experienced when changing link settings under WordPress 2.7. (This was the result of
some new caching features implemented in 2.7.)
INTERFACE SPIFFED UP: Interface elements have been updated so that
FeedWordPress’s management interface fits in more naturally with the
WordPress 2.7 interface (including a new logo and a number of small
BUG WITH TAGS FOR SYNDICATED ARTICLES FIXED: Several users encountered a
bug with the option to add tags to all syndicated posts under
Syndication –> Settings — if you told FeedWordPress to add more than
one tag to all syndicated posts, instead of doing so correctly, it would
add a single tag instead, whose name was composed of the names of all
the tags you asked it to add. This bug was the result of nothing more
dignified than a typographical error on my part. It has now been fixed.
MORE INFORMATION AVAILABLE WHEN FEEDWORDPRESS CAN’T FIND A FEED: When
you enter a URL for a new syndication source, FeedWordPress uses a
simple feed-finding algorithm (originally based on Mark Pilgrim’s
Universal Feed Finder) to try to determine whether the URL is the URL
for a feed, or, if the URL points to an ordinary website rather than to
a feed, whether there is a feed for that website. All well and good, but
if FeedWordPress failed to find a feed, for whatever reason, it would
typically return nothing more than a nasty little note to the effect of
no feed found,without any explanation of what went wrong.
FeedWordPress now keeps track of error conditions from the HTTP
requests that it uses in the course of looking for the feed, and so may
be able to give you a bit more information about the nature of the
problem if something goes wrong.
Enjoy! As always, you have any issues with the release, or if there is anything that you would like to see included in a future release, please use the comments form or drop me a line to let me know about it.
Also, I know that there are a couple of issues that some users have already reported that have not yet been addressed in this release. (For example, I haven’t yet been able to investigate the issue reported by Scot Hacker and mn, as well as some private e-mails. I’m hoping to investigate this issue over the next couple weeks in order to discover what’s going on and how to fix it; if I can catch it in action, then I should be able to push out a release either during downtime on my winter vacation, or else shortly after New Years’.) In any case, please remember that your gifts to the project tip jar make ongoing development and support like this possible.