Update 2007-11-21: FeedWordPress 0.96 is now out of date. You can download the latest release — 0.991 at the time of this writing — from the project homepage.
Version 0.96 is a feature-adding release. If there were any bugs that I eliminated between version 0.95 and now, I wasn’t diligent enough to write them down, and I don’t remember any. But I have added three features. Two are minor additions for consistency’s sake or for a minor convenience; one is a bit more significant.
* **FEATURE:** for completeness’s sake, there is now a feed setting,
`hardcode url`, that allows you to set the URI for the front page
of a contributor’s website manually (that is, prevent it from being
automatically updated from the feed channel link on each update). To
set the URI manually, put a line like this in the Link Notes section
of a feed:
hardcode url: yes
You can also instruct FeedWordPress to use hardcoded URIs by default
on all feeds using Options –> Syndication
* **FEATURE:** by default, when FeedWordPress finds new syndicated posts,
it (1) publishes them immediately, (2) turns comments off, and (3)
turns trackback / pingback pings off. You can now alter all three
default behaviors (e.g., to allow pings on syndicated posts, or to
send newly-syndicated posts to the draft pile for moderation) using
Options –> Syndication
* **FEATURE:** support has been added for enclosures in RSS 2.0 and Atom
0.6+ newsfeeds. WordPress already supports adding enclosures to an
item; FeedWordPress merely gets the information on the enclosure
from the feed it is syndicating and plugs that information directly
into the WordPress database so that (among other things) that post
will have its enclosure listed in your blog’s RSS 2 newsfeed.
Note that enclosure support requires using the optional MagpieRSS
upgrade (i.e., replacing your `wp-includes/rss-functions.php` with `OPTIONAL/wp-includes/rss-functions.php` from the FWP archive)
If you’re interested (for example, because you’re writing PHP filters and want
to know how all this is represented), here’s how it’s currently done:
Note that these are hacked-in solutions for inherited problems with
MagpieRSS as of version 0.7. They are not guaranteed to be
forward-compatible when/if Kellan solves these problems in the official
Magpie branch in the future. If you have filters (for example) that
depend on either categories or enclosures working as they currently do,
keep an eye on the ChangeLog in future releases.