WordPress.org

Ready to get started?Download WordPress

Plugin Directory

FeedWordPress

FeedWordPress is an Atom/RSS aggregator for WordPress. It syndicates content from feeds that you choose into your WordPress weblog; the content it syn

2012.0504

  • BUGFIX: PHP 5.4 compatibility -- includes some more extensive fixes to compatibility issues with PHP 5.4's handling of global variables

  • MODULE REORGANIZATION: Should ensures that all needed submodules will be properly included regardless of whether you are installing from github, from SVN, or from the WordPress plugins page. If you've been getting fatal errors about required modules not being found, this release should hopefully resolve the issue.

2012.0503

  • BUGFIX: Works properly again with WordPress installations that use a MySQL table name prefix other than the default wp_ prefix.

  • BUGFIX: Includes a couple of significant PHP 5.4 compatibility fixes. Now that PHP 5.4 is more widely deployed, Diagnostics will now also show PHP version and some other potentially useful troubleshooting information.

  • ADMIN UI: Better indicates your options when deleting a syndicated post so as to let you know whether it will be Trashed (and thus not resyndicated) or Erased (and thus potentially resyndicated)

  • ADMIN UI: Adds an AJAXy Test Expression button to allow live testing of sample results from expressions in Custom Post Settings.

2012.1218

  • WORDPRESS VISUAL EDITOR FIXED. There was an unlisted change in the 2012.1212 release which had the effect of disabling the WordPress Visual Editor for all posts syndicated by FeedWordPress. Many users reported this as a bug. It was actually a deliberate decision -- a crappy way to try to deal with a crappy situation. (Many users had previously reported a "bug" in which all the paragraph or line breaks seemed to be stripped out of their syndicated posts; the issue turned out to be that the Visual Editor was stripping out <p> and <br/> tags on the assumption that the resulting post would be sent through standard WordPress formatting filters. But under default settings, posts syndicated by FWP deliberately bypass WordPress formatting filters.) In any case, this version adopts a more flexible compromise. If FeedWordPress is set up to bypass WordPress formatting filters (as it is by default), then the Visual Editor will be disabled for syndicated posts (since using it would produce incorrect results). If on the other hand FeedWordPress is set up to expose syndicated posts to WordPress formatting filters (as it usually is for those using the Visual Editor to manually edit posts), then the Visual Editor tab will be re-enabled for syndicated posts.

  • BUG FIX: PERMALINKS REWRITTEN FOR CUSTOM POST TYPES AS WELL AS NORMAL WORDPRESS POSTS. If you had WordPress set up to syndicate incoming posts to a custom post type (under Syndication > Posts & Links), and asked FeedWordPress to make "permalinks point to the original site", then previous versions of FeedWordPress would fail to do the rewriting -- permalinks would only be rewritten to point to the original source for normal WordPress posts, not for custom post types. In 2012.1218 this bug has been fixed: all post types will now have permalinks rewritten unless you request for permalinks to point to the local copy on your aggregator site.

  • BUG FIX: ELIMINATES "PHP Fatal error: Call to a member function setting() on a non-object...." Some changes to the in-memory caching of information about feed subscriptions could result in a fatal PHP error in cases where you have de-activated one of your subscriptions, but posts from that subscription were still in the archive. This would normally show up through half-completed feeds or half-completed pages that suddenly broke off in the middle, and displayed or logged an error message like: "PHP Fatal error: Call to a member function setting() on a non-object in {...}/wp-content/plugins/feedwordpress/feedwordpress.php on line 615". This bug has been eliminated, so affected feeds and pages should now render correctly, and the error message should no longer appear.

  • BUG FIX: CATEGORY BOXES IN SYNDICATION > CATEGORIES & TAGS. Some minor bugs in the appearance and animation of category checkboxes (for example, the checkbox used to select categories for syndicated posts on the Syndication > Categories & Tags settings page) have been fixed.

2012.1212

  • WORDPRESS 3.5 COMPATIBILITY: This release has been tested for compatibility with new releases of WordPress, up to version 3.5, and any documented compatibility issues have been cleared -- in particular, if you were seeing error pages stating that you don't have permission to access the FeedWordPress Syndication page within the WordPress admin interface, then upgrading to this release should fix the problem.

    As always, if you encounter any compatibility problems after upgrading your version of WordPress and your version of FeedWordPress to the most recent versions, please contact me with as detailed a description as possible of the issue you are encountering, the circumstances you're encountering it under, what you expect to see happening, and what is happening instead.

  • PHP 5.4 COMPATIBILITY: This release has been audited to fix potential problems with deprecation notices or fatal errors under recent versions of PHP. In particular, all uses of run-time pass-by-reference have been eliminated from the code; if you were seeing a fatal error reading "Call-time pass-by-reference has been removed ..." then upgrading to this release should fix the problem.

  • CUSTOMIZATION FRAMEWORK: A great deal of work has been done to make the underlying framework more flexible, so that PHP add-ons can be written to adapt FeedWordPress to handle custom XML vocabularies, expiration of posts under specified conditions, and other custom behavior.

  • BUGFIX: MANUALLY EDITED POST SLUGS NOT OVERWRITTEN. Thanks to a report by Chris Fritz, I've identified some code that causes post slugs for the posts generated by FWP to be rewritten with every update, even if the user has manually updated the slug from within the WordPress editing interface. This has been fixed: FWP will continue to generate new slugs for syndicated posts, but when syndicated posts are updated, they will retain the slug that they had at the time of the update; any manual changes to the post slug should be preserved.

  • USER-AGENT STRING: FeedWordPress now sends a distinctive User-Agent string identifying itself, and noting that it is a feed aggregator.

  • MISCELLANEOUS PERFORMANCE IMPROVEMENTS: A number of changes have been made to try to reduce the intensity and expense in terms of both database performance and web server memory consumption.

  • DIAGNOSTICS IMPROVEMENTS: A number of new and improved diagnostics have been added which should aid in understanding and troubleshooting issues that may arise.

2011.1019

  • BUGFIX: "THERE ARE NO HTTP TRANSPORTS AVAILABLE" ERROR FIXED: The initial support for HTTP Basic and Digest authentication in version 2011.1018 contained a bug that could cause HTTP requests for feeds or for other WordPress resources to break down if you do not have the PHP curl module installed. This bug has been fixed, and these errors should no longer appear.

  • IMPROVED HTTP AUTHENTICATION SUPPORT: In addition, the HTTP Authentication support in FeedWordPress has been extended, to ensure that Basic authentication is available in many web host configurations, and to allow you to add a username and password for a feed immediately when you subscribe to it.

2011.1018

  • HTTP BASIC AND DIGEST AUTHENTICATION SUPPORT: FeedWordPress now offers improved support for syndicating feeds that make use of HTTP Basic or HTTP Digest authentication methods. In order to set up authentication on one of your feeds, just go to its Settings > Feed page, and click on the "Uses Username/Password" link underneath the Feed URL. Enter the username and password for accessing the feed, then select the authentication method. (If you're not sure which method your feed provider uses, try Basic first.) Save Changes, and syndicate away.

    NOTE: HTTP Digest support requires the curl module for PHP. If you are not sure whether this module has been installed, contact your web hosting provider to check.

  • WP 3.3 (BETA) COMPATIBILITY: This version fixes an init-sequence bug that could cause intrusive warning messages or fatal errors in WP 3.3 beta versions.

  • BUGFIX: FIXES LONG DELAYS IN UPDATES SCHEDULES IN LARGE INSTALLATIONS. A performance feature introduced in version 2011.0721 had some flaws in its implementation, which tended to create serious delays (on the order of several hours) in FeedWordPress's attempts to schedule updates for feeds, when users had a very large number of feeds (several dozen or more) in their FeedWordPress installation. This feature has been reconfigured to adjust dynamically to the number of feeds in Syndicated Sources and the frequency with which they are updated. If you've seen a lot of ready-to-update feeds piling up, several hours after they were supposed to get updated, then this upgrade should better ensure that your feeds get updated in a timely fashion.

  • BUGFIX: syndicated_item_guid FILTERS FIXED. Previous versions of FeedWordPress theoretically allowed for filters on the syndicated_item_guid hook, which was intended to filter the globally-unique identifier element (rss:guid or atom:id) -- useful if you need to convince FeedWordPress to use different guids, or to recognize two or more incoming posts as versions of the same post rather than as distinct items. However, while the hook affected the guid stored in the WordPress database, it did not affect the guid used to check whether an incoming feed item had already been syndicated or was a new item -- which greatly limited the practical usefulness of the filter. This bug has been fixed: syndicated_item_guid filters should now properly control not only the final database record, but also the initial uniqueness test applied to posts.

2011.0721

  • BUGFIX: SERIOUS BUG CAUSING RARE UNEXPECTED DELETION OF PAGES AND OTHER CONTENT. A bug in the guid-checking code for some rare kinds of guids could cause content in the wp_posts table to seemingly disappear at random after FeedWordPress updates.This most frequently but not exclusively affected static pages. What actually happened is that in these rare cases the existing static page was mistaken for an older version of the new incoming syndicated post, which was then stored as a new revision of the original page. The bug that caused these mistaken identities has been fixed.

  • BUGFIX: UNWANTED AUTOMATIC PAGE-LOAD-BASED UPDATES NO LONGER A NUISANCE. Some users encountered a bug in which FeedWordPress would adopt an automatic page-load-based update method, even if they had requested that it not do so, and that it use a manual or cron job update method instead. The bug causing this has been fixed, and page-load-based updates should no longer trigger unless explicitly turned on.

  • WP 3.2 USER INTERFACE COMPATIBILITY: POST TAGS BOX NOW WORKS AGAIN. The release of WordPress 3.2 caused a breakage in the tags box which prevented you from adding or removing tags under Syndication --> Categories & Tags. (The breakage was the result of an incompatibility introduced by the new release of jQuery.) This breakage has now been fixed, and the tags box should work correctly again.

  • FEED UPDATE SCHEDULING IMPROVEMENTS: UI. The Syndicated Sources table now provides considerably more data to understand update scheduling, when specific scheduling decisions are made because of, e.g., requests from the feed producer.

  • FEED UPDATE SCHEDULING IMPROVEMENTS: ENFORCEABLE "MINIMUM INTERVAL" SETTING TO SPACE OUT UPDATES. Some feeds request specific update schedules, using standard elements such as sy:updateFrequency and rss:ttl. Normally, FeedWordPress respects any scheduling requests that a feed makes -- if it requests a longer gap between polls than what FWP would normally adopt, then FWP slows down to meet the request. If it indicates a shorter gap than what FWP would normally adopt, FWP speeds up and checks that feed for updates more often than it normally would. Now, there should not be any way for user settings to override an explicit slow-down request from the feed producer -- if producers indicate a particular update schedule, then polling the feed more frequently than they request is considered abusive behavior. But there's no reason why users should not be able -- if they so desire -- to override speed-up requests, and poll a feed less frequently than the indicated update schedule, if the FWP user wants to space update checkins over a longer interval of time. Before, they could not do this: FWP always sped up to meet the indicated update schedule. Now, they can do this, by using the new "Minimum Interval" setting in Syndication --> Feeds & Updates..

2011.0706

  • WP 3.2 COMPATIBILITY: ELIMINATES FATAL ERROR "Call to undefined method WP_SimplePie_File::WP_SimplePie_File() in [...]/wp-content/plugins/feedwordpress/feedwordpress.php on line 1841." The latest release of WordPress, version 3.2, has shifted the minimum requirements up to PHP 5.2, and in line with the shift to PHP5 they have rewritten a number of code segments that made use of now-obsolete PHP4 idioms. Unfortunately, this caused a fatal error whenever FeedWordPress attempted to make use of the cache, since FWP's caching plugin was written to match the older idiom. FeedWordPress has been updated to follow the new, PHP5 idiom when possible, thus eliminating the fatal error.

  • PERFORMANCE: The handling of queries to determine whether posts had been previously syndicated produced some very slow queries (usually, but not always, involving a scan over the MD5(post_guid) column of the table). The code that prepares MySQL queries for previously-syndicated checks has been revised to eliminate the MD5(post_guid) scan entirely, and to significantly improve performance by eliminating other unnecessary clauses.

  • BUGFIX: NO LONGER DESTROYS STICKY POSTS. Previous versions could destroy (or, more precisely, replace the content of) sticky posts due to some queries mashed together in unexpected ways by WordPress. Version 2011.0706 accounts for and eliminates the problem; your sticky posts should be safe once again.

  • BUGFIX: GUIDS CONTAINING MYSQL-ESCAPED CHARACTERS NO LONGER CAUSE DUPLICATE POSTS TO APPEAR. One remaining source of duplicate post issues in 2011.0602 was guids that contained characters that needed to be escaped for MySQL, such as single quotes and double quotes. The work-around for handling filtered URIs has now been corrected to ensure that these do not cause duplicate posts.

2011.0602

  • WP 3.1.3 COMPAT / BUGFIX: WHITESPACE IN GUIDS NO LONGER PRODUCES DUPLICATE POSTS. The work-around for handling filtered URIs in guid elements has now been extended to handle URIs that were filtered because of leading or trailing whitespace, in addition to URIs that were filtered because of unapproved schemes.

  • WP 3.1.3 COMPAT / BUGFIX: RELATIVE URLS IN GUIDS NO LONGER PRODUCE DUPLICATE POSTS. The work-around for handling filtered URIs in guid elements has now been extended to handle URIs that were altered without being filtered out entirely (most commonly because a scheme was added to a relative URL).

  • BUGFIX: UPDATES TO POST NO LONGER CAUSE DUPLICATE DRAFT VERSION TO APPEAR. Under certain conditions in 2011.0531, an update to an existing post would not be properly applied to the post itself, but rather would appear as a duplicate post with Draft status. This bug has been eliminated, and updates will now be properly inserted as revisions to the existing post.

2011.0531

  • WORDPRESS 3.1.3 COMPATIBILITY: DUPLICATE POSTS ISSUE FIXED. Due to internal changes in the way that WordPress handles post guids in the most recent release (3.1.3), many users experienced problems with many duplicate posts appearing in rapid succession. (Specifically, this would happen with any posts using tag: URL guids -- such as all the posts coming from Blogger feeds or feeds from other Google services.) This compatibility release of FeedWordPress eliminates the issue by working around the new restrictions on tag: URLs.

  • NEW AND IMPROVED DIAGNOSTICS: Syndication --> Diagnostics now contains some new diagnostics settings useful for debugging problems with duplicate posts (allowing you to easily view the guid of posts in the WordPress posts database and allowing you to track the SQL used to check for existing versions of a syndicated post).

2011.0512

  • DIAGNOSTICS IMPROVEMENTS; "THERE MAY BE A BUG IN FEEDWORDPRESS" CRITICAL ERROR NOTICES ELIMINATED: This version includes some major improvements to the Syndication --> Diagnostics section, which should aid in troubleshooting difficulties with items failing to be imported, posts failing to be properly inserted into the database, or updates failing to be recorded. If you have been encountering critical error / bug notices with a white screen and the message "THERE MAY BE A BUG IN FEEDWORDPRESS," followed by an extraordinarily long dump of mostly incomprehensible diagnostic information, you'll be happy to know that the condition causing these notices has been eliminated. In the few cases where errors may still crop up with database insertions, FeedWordPress will now produce a significantly more manageable and more useful diagnostic message.

  • BUGFIX: NEW POSTS FAILING TO APPEAR IN A CLEANLY-INSTALLED FEEDWORDPRESS SYSTEM. If you encountered a recurring problem with FeedWordPress failing to import new posts, after a clean install of FeedWordPress (i.e., not an upgrade from a previous version), this problem may have been the result of a bug with author-handling which has now been fixed in the 2011.0512 release. (If the problem does not go away with the upgrade, this version also includes significant improvements to the Diagnostics system, which will help track down what is causing it in your particular case.)

  • PERFORMANCE: New handling of update hashes allows FeedWordPress to avoid a certain kind of infinite loop, caused when two more more different syndicated feeds each carried a version of the same item (for example, because it appeared on two different aggregator feeds that you're syndicating). In previous versions, when this kind of loop cropped up, syndicated posts could pile up an indefinitely large number of revisions -- each revision alternating between the version from each of the two feeds where it appeared -- which would, over time, dramatically inflate the size of the database, and kill the performance of queries on the post table. This issue has been resolved: revisions of the post that have been syndicated once will not be re-syndicated over and over again.

  • AUTHOR LISTS: Lists of authors presented on the Author settings pages should now be easier to scan through, with author names arranged in alphabetical order.

  • FEED ITEM DATE PARSING: More tweaks to make date-time handling more resilient when feeds provide broken or weird values for the timestamps on syndicated items. FWP will now attempt to work around unparseable timezone values.

  • AUTHOR MATCHING: Now attempts to match author names against the WP login name in addition to display_name; when creating user record, also fills in some best-guess values for nickname, firstname and lastname. Also properly picks up Atom 1.0 author/uri data from feed.

  • COMPATIBILITY: FeedWordPress has been successfully tested for compatibility with recent releases of WordPress, up to version 3.1.2.

2011.0211

  • BUGFIX: DUPLICATE POSTS WHEN GUIDS ARE TOO LONG: When feeds included exceptionally long GUIDs, FeedWordPress could occasionally get into a situation where posts with the long GUIDs would be duplicated over and over again with each update (because FWP failed to store the full GUID, due to length constraints in the relevant database tables). Without the full GUID, FWP would not know that the post had already been syndicated once. This bug has been fixed, and should no longer produce duplicate posts.

  • HTTP TIMEOUT SETTING: If you are frequently running into timeout problems with one or more of the feeds you syndicate, FWP now allows you to adjust the timeout for HTTP requests using a global or feed-by-feed setting.

  • HTTP GET PARAMETERS: You can now temporarily or permanently add HTTP GET parameters to a subscription using an interface in Syndication --> Feeds & Updates. This is especially helpful for making quick, short-term changes to a subscription (for example, to pull in all the previous items from a web service, before settling down to pulling in only newly updated items).

  • DIAGNOSTICS SYSTEM: Added several new diagnostics which are useful in troubleshooting, and established a framework for add-on modules to hook in with their own diagnostic messages.

  • UI: Adjusted some internal coding, which should allow for settings pages and add-ons to properly display multiple category pickers on a single settings page.

  • PHP4 COMPATIBILITY TWEAKS: This version makes some tweaks to the handling of object references which should improve compatibility with older versions of PHP. (Although, I should note, web hosts that still force you to run under PHP 4 -- in 2011! -- are bad web hosts.)

  • IMPROVED PERFORMANCE: This version eliminates a major performance drag that shows up on sites with large numbers of users (due to some poor decisions about where to place a user query, which caused the user table to be scanned frequently when it did not need to be). If you experienced serious problems with CPU load or slow database performance under 2010.0905, which kicked in immediately when FWP was loaded and tended to disappear immediately if FWP was de-activated, it is likely that upgrading away from 2010.0905 to the most recent version will resolve your problem.

2010.0905

  • BUGFIX: CATEGORIES AND TAGS CORRECTLY ASSIGNED IN AUTOMATIC UPDATES. Version 2010.0903 switched over to a new way of assigning categories and tags as part of its support for handling custom taxonomies. Unfortunately, the method that it uses is subjected to some checks of the current user's capabilities, which creates problems for posts that are being inserted into the WordPress database when there is no current user logged in (as, for example, when an update is being carried out from a cron job or automatic update). The result was that posts from cron jobs and automatic updates ended up with no Categories and no Tags being assigned. This bug has now been fixed: in 2010.0905, Tags and Categories should be correctly assigned to all posts, regardless of whether they were added from manual updates, cron jobs, or automatic updates.

2010.0903

  • WORDPRESS 3 REQUIRED: Please note that this release of FeedWordPress requires WordPress 3.0 or later. If you are currently using a 2.x branch of WordPress, you will need to upgrade to WordPress 3 before you can successfully upgrade FeedWordPress.

  • BUGFIX: NO MORE DISAPPEARING "SYNDICATED SOURCES" PANEL; INTERNET EXPLORER UI GLITCH APPARENTLY FIXED: Several users independently reported a problem with FWP 2010.0623 and various versions of IE. A problem with the HTML markup caused IE (but not Firefox or Chrome) to completely hide the Syndicated Sources administration panel (the main list of currently-syndicated sources, and the main location for adding new sources, under the Syndication menu item) when a user added their first syndicated feed. Maddeningly, the glitch seemed to affect some IE users and not others: I was never able to reproduce the problem for myself on my own machines. However, the markup of Syndicated Sources has undergone significant changes and corrections since 2010.0623, and two independent sources who had been having this problem confirm that they no longer encounter it with the updated version. For the time being, I am going to declare this bug squashed.

  • BUGFIX: MORE PROTECTION AGAINST FATAL ERRORS FROM PLUGGABLE VERSIONS OF SimplePie: FeedWordPress now takes some precautions that should help to better avoid conflicts for users who have installed pluggable versions of SimplePie for another plugin or theme. (You may not know that you have done this; but if you've been encountering fatal errors indicating that you cannot redeclare class SimplePie, or something along those lines, there is now a better chance that those fatal errors will be eliminated.

  • PERFORMANCE: SIGNIFICANTLY REDUCED MEMORY CONSUMPTION FOR LARGE UPDATES: FeedWordPress is still a memory-hungry little module, especially when you are dealing with very large feeds. However, users should notice a significant reduction in memory overloads, especially if they update a large number of feeds at once.

  • USER INTERFACE IMPROVEMENTS: Nothing is radically different, but there's been a fair amount of extra spit and polish added, including a convenient new Dashboard widget that may save you a trip to the Syndication menu, a lot of effort to make the relationship between global and feed-by-feed settings more obvious to the user and more easily controllable, to make navigation between settings pages easier, to sand off a few rough edges, and to make other improvements on the margins. I hope you'll like how it looks.

  • ADDING MULTIPLE FEEDS: FeedWordPress now provides a convenient mode for adding multiple feeds at once, using either a copy-and-pasted list, or else an OPML file. Go to Syndication --> Syndicated Sources and check out the two new buttons underneath the New Source input box. When you have to add a number of feeds at once, this can save you considerable time and trouble.

  • IMPROVED HANDLING OF AUTHORS WITH DUPLICATE E-MAIL ADDRESS AND AUTHORS WITH NAMES WRITTEN IN FOREIGN SCRIPTS: WordPress 3 is increasingly picky about what it will accept for new author accounts, and some of the conditions it imposes can cause error conditions that prevent posts from being properly syndicated, or properly attributed, if authors happen to have identical e-mail addresses, or if users are given usernames that are written in non-Western scripts. FeedWordPress now handles these much better, and systematically works to avoid clashes between syndicated authors' account names or in their e-mail addresses, which should result in significantly better results in mapping author names to WordPress user accounts.

  • MAPPING CATEGORIES ON SYNDICATED POSTS TO TAGS NOW BETTER SUPPORTED: In previous versions, the only way for the Categories provided by a syndicated feed to be mapped into Post Tags was to instruct FWP to create new tags, rather than new categories, for unfamiliar categories from the feed. This works fine if you want tags to be the default; but if you want only a specific set of tags, there was no way to get them without getting most or all other categories imported as tags. You can now do this by creating a tag (under Posts ==> Post Tags) before importing the post; when the syndicated category matches a pre-existing tag, the incoming post will be tagged with that tag, without creating a local Post Category.

  • REL-TAG MICROFORMAT SUPPORT FOR INLINE TAGS: Syndicated posts that contain inline tags, marked up using the Rel-Tag microformat http://microformats.org/wiki/rel-tag, are now tagged with the tags provided by Rel-Tag format links.

  • MUCH GREATER CONTROL OVER CATEGORY AND TAG MAPPING: This is partly the result of building in support for a potentially endless set of custom taxonomies (see below), but in general there has been a great deal of effort towards giving you more control over how categories and tags provided by the feed are mapped into terms on the local blog. In particular, you can now force FeedWordPress to create only categories from categories and tags provided by the feed; or to create only tags; or to search both categories and tags for a match; or you can simply force it to drop all of the categories provided by the feed and use only categories or tags that you explicitly provide. In addition, you can now also choose whether to override global categories settings with a local, feed-specific setting; or whether to add together both the global categories and the local feed-specific categories -- depending on whatever your use-case may demand.

  • CUSTOM POST TYPES AND TAXONOMY SUPPORTS: This is mainly for the super-geeky, but if you use other plugins or themes that make significant use of WordPress's support for custom post types and custom taxonomies, you may be pleased to find that FeedWordPress now allows you to feed incoming posts into any custom feed type that you wish, and to map categories and tags from the feed to custom taxonomies as well as to the standard Category and Tag taxonomies.

  • STORING NAMESPACED CUSTOM FEED ELEMENTS IN POST CUSTOM FIELDS: If you would like to use FeedWordPress's support for storing custom meta-data from feed elements in the custom fields for a post (for example, to store geolocation data or iTunes media meta-data), you'll find that it's now much easier for you to access these namespaced elements. You always could access them, but in previous versions you might have to write something ugly like $(/{http://www.w3.org/2003/01/geo/wgs84_pos#}lat) just to get at the value of a <geo:lat> tag. Now, as long as you use the same mnemonic codes that the feed producer used, you should always be able to write a nice, simple expression like $(/geo:lat) to get the value of a tag.

  • CUSTOM DIRECTORY STRUCTURE SUPPORT: if you poke at it enough, WordPress is relatively flexible about where it should store admin interface code, uploaded content, plugins, and a number of other things that occupy an important place in the WordPress directory structure. Previous versions of FeedWordPress encountered serious errors or broke entirely when used with directory structures other than the default. This should now be fixed: FWP now supports custom directory structures wherever WordPress allows them to be customized, rather than depending on the default locations. Enjoy your freedom!

  • MANY NEW FILTERS AND API UTILITY FUNCTIONS FOR ADD-ON PROGRAMMERS: There have been too many improvements to list them all in this ChangeLog, but it means that much more power and ease for folks who are customizing FeedWordPress through PHP filters or add-on modules. Fuller documentation will be put up at the Wiki at feedwordpress.radgeek.org soon.

2010.0623

  • WORDPRESS 3.0 COMPATIBILITY / AUTHOR MAPPING INTERFACE ISSUES: I resolved a couple of outstanding issues with the author mapping interface (Syndication --> Authors), which were preventing new users from being created correctly and author mapping rules from being set up correctly. These partly had to do with new restrictions on user account creation introduced in WordPress 3.0; anyway, they should now be fixed.

  • MORE EFFICIENT SYNDICATED URL LOOKUPS: Several users noticed that the bug fix introduced in 2010.0528 for compatibility with post-listing plugins caused a lot more queries to the database in order to look up numerical post IDs from the URL provided to the filter. This shouldn't cause any major problems, but it is not as efficient as it could be; the code now takes advantage of a more efficient way of doing things, which usually will not require any additional database queries.

  • SIMPLEPIE FEED UPDATE ISSUES: If you have been having significant problems with getting feeds to update correctly, this may be the result of some bugs in the implementation of SimplePie caching that ships with WordPress (as of version 3.0). (You would most commonly experience this error if you continually saw errors such as "No feed found at <...>" in your updates.) Fortunately, SimplePie allows for a great deal of extensibility and this allows me to work around the problem; these error conditions should now be mostly eliminated when the underlying feed is valid.

  • UI: SHOW INACTIVE SOURCES: When you use the default unsubscribe option -- which turns off the subscription to a feed while preserving the posts from it and the syndication-related meta-data for the feed -- the unsubscribed feed can now easily be viewed in a special "Inactive" section of the Syndicated Sources page. (As a side benefit, if you've accidentally, or only temporarily, turned off the subscription to a feed, it is now much easier to restore the feed to being active, or to delete it permanently, if you prefer.

  • UI: FEED FINDER / SWITCH FEED INTERFACE IMPROVEMENTS: changes to styling and options for the feed finder / switch feed, which should now make it easier, in some cases, to find alternative feeds, and make interface options more clearly visible.

  • FILTERS: syndicated_item_published and syndicated_item_updated NOW PROPERLY AFFECT THE DATING OF POSTS. These filters used to affect some date-related settings, but not others -- and, most importantly, not the final date that is set for a post's publication or last-modified date in the WordPress database. Now, they do affect that, as they should. (Filters should receive, and return, a long integer, representing a Unix epoch relative timestamp.)

  • MAGIC URL TO CLEAR THE CACHE: Suppose that you need to clear the feed cache, for whatever reason; suppose, even, that you need to clear it on a regular basis. One way you might do this is by logging into the FeedWordPress administrative interface and going to Syndication --> Performance. Another way you might do it, now, is to simply send an HTTP request to a magic URL provided by FeedWordPress: if your blog is at example.com, the URL would be http://example.com/?clear_cache=1

2010.0602

  • CATEGORY BOX INTERFACE ELEMENT FIXED FOR WP 3.0: Stylesheet changes between WordPress 2.9.x and the WordPress 3.0 RC caused the Categories box under Syndication --> Categories & Tags to malfunction. This has been fixed.

  • LINK CATEGORY SELECTION BOX IN SYNDICATION ==> FEEDS FIXED FOR WP 2.8 AND 2.9: A WP 3.0 compatibility change introduced in 2010.0531 inadvertently broke the Syndicated Link Category selector under Syndication --> Feeds & Updates in WP 2.8 and WP 2.9, causing the post categories to be displayed in the selector rather than the link categories. This should now be fixed so that the selector will work correctly under both the current versions of WordPress and the 3.0 RC.

  • MORE PERMISSIVE HANDLING OF FEEDS WITH BAD CONTENT-TYPE HEADERS: One of the small advantages that MagpieRSS had over SimplePie is that it was more tolerant about parsing well-formed feeds that the remote web server happened to deliver with weird or incorrect HTTP Content-type headers. In feeds affected by this problem, the new SimplePie parser would simply fail to find a feed, due to its being led astray by the contents of the Content-type header. This version includes an extension to SimplePie's content-type sniffer that offers more permissive handling of the HTTP headers.

  • MORE FULL-TEXT "EXCERPTS" NOW PROPERLY SHORTENED. Version 2010.0528 introduced code to control for cases in which elements intended for item summaries are (ill-advisedly) used to carry the full text of posts; past versions of FeedWordPress would simply include the full text of the post in the excerpt field, but newer versions now attempt to detect this condition when it arises and to head it off, by blanking out the excerpt field and filling it with an automatically generated short, plain text excerpt from the full content. This release broadens the test conditions that indicate when an excerpt field is treated as identical to the full text of the post, and should therefore improve the handling of some feeds (such as Google Reader feeds) where the full text of each post was still appearing in the excerpt field.

  • FILTERS: syndicated_item_published AND syndicated_item_updated FILTERS NOW ALLOW FILTER AUTHORS TO CHANGE POST TIMESTAMPS. You can now use the syndicated_item_published and syndicated_item_updated filter hooks to write filters or add-ons which directly change the post date and most-recently-updated timestamps on incoming syndicated posts. Props to niska for pointing out where the filters needed to be applied in order to change WordPress's internal timestamps for incoming posts.

2010.0531

  • PERMALINK / CUSTOM FIELDS PROBLEM RESOLVED: An issue in 2010.0528 caused some posts to be imported without the proper syndication-related meta-data being attached (thus causing permalinks to point back to the aggregator website rather than to the source website, among other problems). This problem has been resolved (and a fix has been applied which will resolve the problem for any posts affected by this problem, if the original post is recent enough to still be available on the feed).

  • UI: The "Back End" section has been split into two separate sections -- "Performance" (dealing with caching, database index, and other performance tweaks), and "Diagnostics" (dealing with debug mode, update logging, and a number of new diagnostic tests which I will be rolling out over the next few releases).

  • Several minor interface bug fixes and PHP warning notices eliminated.

2010.0528

Compatibility

  • SIMPLEPIE IS NOW USED TO PARSE FEEDS; NO MORE MAGPIERSS UPGRADES NEEDED: One of the biggest changes in this release is that FeedWordPress no longer depends on MagpieRSS to parse feeds, and has switched to the much more up-to-date and flexible SimplePie feed parser, which is included as a standard part of WordPress versions 2.8 and later. Using SimplePie will hopefully allow for better handling of feeds going further, and will allow me greater flexibility in determining how exactly the feed parser will operate. It also means that FeedWordPress no longer requires special upgrades to the WordPress core MagpieRSS files, and should eliminate quite a bit of complexity.

  • MAGPIERSS COMPATIBILITY LAYER FOR EXISTING FILTERS AND ADD-ONS: However, I have also implemented a compatibility layer to ensure that existing filters and add-ons for FeedWordPress which depended on the MagpieRSS data format should not be broken by the switch to SimplePie. Going forward, I recommend that new filters and add-ons be written to take advantage of the SimplePie object representations of items, feeds, etc., rather than the MagpieRSS arrays, but the MagpieRSS arrays will still be available and older filters should continue to work as they have in the past.

  • COMPATIBILITY WITH WORDPRESS 2.9.x and 3.0: This release has been tested for the existing WordPress 2.9.x branch and with the upcoming release of WordPress 3.0. Changes in the user interface JavaScript between WordPress 2.8.x and WordPress 2.9 caused the tag box interface element to break in the Syndication --> Categories & Tags settings page; changes in the API functions for adding new authors caused fatal errors under certain conditions in WordPress 3.0. These breakages have been fixed.

  • DROPPED LEGACY SUPPORT FOR WORDPRESS PRIOR TO 2.8: Because SimplePie is not included with versions of WordPress prior to 2.8, I have chosen to drop legacy support for WordPress versions 1.5 through 2.7. If you are using FeedWordPress with a version of WordPress before 2.8, you will have to upgrade your installation of WordPress in order to take advantage of this release.

  • PHP 5.3 COMPATIBILITY: A couple of compatibility issues, which were causing fatal errors amd ugly warnings for users of PHP 5.3, have been eliminated.

Features and Processing

  • INTERFACE REORGANIZATION: The interface restructuring, began with Version 2009.0612, has been completed. Catch-all settings pages have been eliminated entirely for pages that cover each aspect of handling a feed: Feeds & Updates, Posts & Links, Authors, Categories & Tags, and Back End handling of the database and diagnostic information. Extensive new interface hooks allow add-on modules to significantly change or extend the FeedWordPress admin interface and workflow.

  • STORING INFORMATION FROM THE FEED IN CUSTOM FIELDS: Many users have written to request the ability to store information from elements in the feed in a custom field on each post. (So that, for example, if post includes a itunes:duration element, you could store the contents in a Custom Field called duration on the post (for a Theme to access later). The Custom Post Settings under Syndication --> Posts & Links now allow you to access any item or feed tag, using a syntax similar to a much-simplified version of XPath. See Posts & Links settings for details.

  • UPDATE-FREEZING ON MANUALLY EDITED POSTS: FeedWordPress now allows you to mark posts that have been manually edited, so that the changes you make will not be overwritten by later updates from the feed. If you make manual edits to a particular post, just check the "Manual editing" checkbox in order to protect your changes from being overwritten. If you want to block all posts from being updated after they are imported for the first time, a new "Updated Posts" setting in Posts & Links allows you to freeze all posts from a particular feed, or all syndicated posts.

  • SETTING: FEED-BY-FEED SETTINGS FOR WHERE PERMALINKS POINT TO: You've always been able to tell FeedWordPress whether permalinks for posts should point to the original source of the story or the local copy. Now you can choose different policies for different feeds, instead of one global policy for all feeds. (Of course, you can still use a global default if you prefer.)

  • SETTING: USER CONTROL OVER TIMING BASIS. You can now determine the schedule on which feeds are considered ready to poll for updates -- by default feeds become ready for polling after about 1 hour. You can now increase or decrease the time window under Syndication --> Feeds & Updates. (However, please pay CAREFUL ATTENTION to the recommendations and DO NOT set the scheduling lower than 60 minutes unless you are ABSOLUTELY SURE that you have specific permission from webmaster who provides that specific feed to poll more frequently than that. If you set this too low (and about 60 minutes is the polite minimum if you haven't been given a different figure), most webmasters will consider the frequent hits on their server as rude, or even downright abusive.

  • OTHER SETTINGS: New settings also include the ability to stop FWP from resolving relative URLs within syndicated content, and the ability to choose whether FeedWordPress should indicate the comment feed from the original source, or the local comment feed, when providing the comment feed URL for a syndicated post.

Parsing

  • BETTER DATE HANDLING -- FEWER FLASHBACKS TO 1969 and 1970: FeedWordPress has made some bugfixes and some improvements in the logic for parsing dates. This should allow FeedWordPress to correctly parse more dates in more feeds; and, in the last resort, when FeedWordPress fails to correctly parse a date, to fall back to a more intelligent default. This should hopefully avoid most or all error conditions that have resulted in articles being erroneously dated to the dawn of the Unix epoch (31 December 1969 or 1 January 1970).

  • FULL-TEXT "EXCERPTS" NOW PROPERLY SHORTENED. Based on a straightforward reading of the existing RSS specs, it's reasonable for the rss:description element to be read as a plaintext summary or excerpt for the item containing the description -- with the full text of the item, if available, in another, better-suited element, such as the de facto standard content:encoded extension element. The problem is that uses of RSS rarely have much to do with anything like a straightforward reading of the specs. As a result, many actual RSS producers in the wild put the full text of the article in a description element. But since FeedWordPress has treated this text as a summary, this produces aggregated posts with lengthy "excerpts" containing the full text of the article. This release of FeedWordPress fixes the problem by doing a little digging before treating rss:description as a summary: if the description element is used properly as a plain text summary, then FeedWordPress will take the summary provided by the feed, rather than recreating its own excerpt from the full text; but if an RSS item has no full-text element other than description, FeedWordPress will treat the description element as the full text of the article, and generate a shortened excerpt automatically from that text.

API

  • TEMPLATE API: new template tags get_local_permalink() and the_local_permalink() allow you to access the permalink for a post on your aggregator site, even when FeedWordPress is rewriting permalinks to point to the original source site.

  • NEW HOOKS FOR ADD-ONS AND FILTERS: I have added a number of new hooks which allow add-on modules to filter more precisely, gather information at more points, and to enhance the FeedWordPress admin interface. For a list of new hooks and documentation, see the FeedWordPress documentation wiki at http://feedwordpress.radgeek.com/wiki/add-ons-and-filters

  • FILTER API: A number of new utility methods have been added to the SyndicatedPost class to make it easier for filters and add-ons to

  • FILTER API: Globals $fwp_channel and $fwp_feedmeta DEPRECATED. These global variables, originally introduced to allow filters access to information about the source feed in syndicated_item filters (which were passed in through global variables rather than as parameters because of a bug in WP 1.5 which was then fixed in 1.5.1) have been DEPRECATED. If you have any filters or add-ons which still depend on these global variables, you should see about fixing them to access data about the source feed using the SyndicatedPost::link element instead. For documentation, see the FeedWordPress documentation wiki at http://feedwordpress.radgeek.com/wiki/syndicatedpost and http://feedwordpress.radgeek.com/wiki/syndicatedlink.

  • DIAGNOSTICS: I've included a number of new diagnostic options and messages, which should allow an experienced user to better investigate any problems that may crop up.

Bug Fixes

  • BUGFIX: & IN PERMALINKS NO LONGER CAUSING ATOM OR HTML VALIDATION EFFORTS: Many users reported an issue in which syndicating a feed with special XML characters in the URLs (& was the most common, since it is used to separate HTTP GET parameters) would cause the aggregator's feeds to produce invalid (malformed) XML. This update addresses the issue in Atom feeds. Unfortunately, it has not been technically possible to address the problem in RSS 2.0 feeds, due to limitations on WordPress's internal templates for RSS feeds.

  • BUGFIX: BROKEN URLS IN "POPULAR POSTS" AND SIMILAR PLUGINS SHOULD NO LONGER BE BROKEN. A number of users noticed an issue where plugins and templates that listed posts in locations outside of the post loop (for example, "Popular Posts"-style plugins that listed posts in the sidebar), often produced the wrong URL for post links. (Typically, all the posts listed would get the same wrong URL.) This should now be fixed. Thanks to Bj√∂rn for sending in a quick fix!

  • MINOR BUGFIXES: This release includes a number of fixes to minor bugs and compatibility issues, including: silent failures of the "Syndicate" button, "Illegal Offset Type" error messages from MagpieRSS, and others.

2009.0707

  • BUGFIX: WORDPRESS 2.8 AJAX COMPATIBILITY ISSUES RESOLVED (blank or truncated "Syndicated Sites" administration page): Due to changes in the AJAX interface elements between WordPress 2.7 and WordPress 2.8, several FeedWordPress users encountered an issue where the front "Syndication" page in the FeedWordPress administrative interface would come up blank, without the normal "Syndicated Sites" list and "Update" control, or sometimes wth the boxes visible but one or both of them truncated, with only the title bar. This issue should now be resolved: with the new version of FeedWordPress, the compatibility issue that caused the disappearance should be eliminated, and if boxes are shown with only their handle visible, you should once again be able to drop down the rest of the box by clicking once on its title bar.

  • BUGFIX: TAG SETTING WIDGET FIXED. Due to changes in interface elements between WordPress 2.7 and WordPress 2.8, people using FeedWordPress with WordPress 2.8 found that the widget for setting tags to be applied to all syndicated posts, or all syndicated posts from a particular feed, no longer displayed "Add" and "Remove" buttons for individual tags. This issue has now been fixed, and the tagging widget should once again work more or less exactly like the tagging widget for individual posts in the normal WordPress admin interface.

2009.0618

  • BUGFIX: MYSTERY ERRORS WITH WITH WP_Http_Fsockopen HTTP TRANSPORT ELIMINATED: Thanks to a combination of a subtle bug in FeedWordPress, and changes to the HTTP transport code in WordPress, a number of users encountered an error in which any time they attempted to add a new feed through the FeedFinder interface, FeedWordPress would fail and display an HTTP request failure diagnostic message. The subtle bug has been fixed, and with it, most of these errors should now be eliminated.

    Be sure to upgrade your MagpieRSS to the most recent MagpieRSS version after you have insalled FeedWordPress 2009.0618, or this bug fix will not take effect.

2009.0613

  • INTERFACE/BUGFIX: WORDPRESS 2.8 CATEGORY BOX FIX. Thanks to a subtle change in class names between the WordPress 2.7 and 2.8 stylesheets, category boxes in the FeedWordPress settings interface tended to overflow and have a lot of messy-looking overlapping text under WordPress 2.8. This has now been fixed.

  • FeedFinder FAILURE DIAGNOSTICS: When FWP's FeedFinder fails to find any feeds at a given URL (for example, when you are trying to add a subscription through the administrative interface and you run into an error message), FeedWordPress now provides more diagnostic information for the reasons behind the failure. If that helps you, great; if not, it should help me respond more intelligently to your support request..

2009.0612

  • WORDPRESS 2.8 COMPATIBILITY: FeedWordPress 2009.0612 has been tested for compatibility with the recent version 2.8 release of WordPress.

  • INTERFACE RESTRUCTURING: In order to avoid settings posts from becoming too crowded, and to modularize and better organize the user interface, new "Posts" and "Categories & Tags" subpages have been created under the "Syndication" menu. "Posts" controls settings for individal syndicated posts (such as publication status, comment and ping status, whether or not to use the original location of the post as the permalink, whether or not to expose posts to formatting filters, and so on). "Categories & Tags" controls settings for assigning new syndicated posts to categories and tags, such as categories or tags to apply to all syndicated posts, and how to handle categories that do not yet exist in the WordPress database. These subpages, like the Authors subpage, handle settings for the global default level and for individual syndicated feeds.

    Corresponding to these new subpages, the old Syndication Settings and Feed Settings subpages have been cleaned up and simplified, and now only link to the appropriate subpages for options that can be set in the Posts, Authors, or Categories & Tags subpages.

  • FEATURE: ADD CUSTOM SETTINGS TO EACH SYNDICATED POST: FeedWordPress has long had an interface for creating custom settings for each syndicated feed which could be retrieved in templates using the get_feed_meta() template function. But it had no feature for adding custom fields to each individual syndicated post. In response to requests from users, I have added the ability to apply custom fields to each individual syndicated post, using the new Syndication --> Posts subpage. You can set up custom fields to be applied to every syndicated post, or custom fields to be applied to syndicated posts from a particular feed.

  • FEATURE: MAGPIERSS VERSION CHECK AND UPGRADE: FeedWordPress will attempt to determine whether or not you are using the upgraded version of MagpieRSS that comes packaged with FeedWordPress. If not, it will throw an error on admin pages, and, if you are a site administrator, it will give you the option to ignore the error message, or to attempt an automatic upgrade (using a native file copy). If the file copy fails, FeedWordPress will offer some guidance on how to perform the upgrade manually.

  • BLANK POSTS PROBLEM NO LONGER OCCURS WITH OLD & BUSTED MAGPIERSS: Due to the fact that I relied on a content normalization that occurs in my upgraded version of MagpieRSS, but not in the old & busted version of MagpieRSS that ships with WordPress, until this version, if you tried to syndicate an Atom feed without having performed the (strongly recommended) MagpieRSS upgrade, all of the posts would come up with completely blank contents. That's not because MagpieRSS couldn't read the data, but rather because the new Magpie version puts that data in a location where the old version doesn't, and I was only looking in that newer location. Now it checks for both, meaning that posts will continue to display their contents even if you don't upgrade MagpieRSS. (But you really should upgrade it, anyway.)

  • BUGFIX: RELATIVE URI RESOLUTION FOR POST CONTENT RESTORED. Some time back, I added support for resolving relative URIs against xml:base on feeds that support it to the MagpieRSS upgrade in FeedWordPress. Then I took out code that did the same thing from the main FeedWordPress code. Of course, the problem is that some people, even though it is clearly stupid or evil to do so, still include relative URIs for images or links in posts on feed formats that do not adequately support xml:base (notably, RSS 2.0 feeds). In response to a user request, I have added this functionality back in, so that MagpieRSS will resolve any relative URIs that it knows how to resolve using xml:base, and then FeedWordPress will attempt to resolve any relative URIs that are left over afterwards.

  • BUGFIX: INTERFACE OPTION FOR SETTING SYNDICATED POST PUBLICATION STATUS ON A FEED-BY-FEED BASIS HAS BEEN RESTORED: Due to a version-checking bug, users of WordPress 2.7.x lost an option from the "Edit a syndicated feed" interface which allowed them to determine whether newly syndicated posts should be published immediately, held as "Pending Review," saved as drafts, or saved as private posts. (The option to change this setting globally remained in place, but users could no longer set it on a feed-by-feed basis.) The version-checking bug has been fixed, and the option has been restored.

  • BUGFIX: "ARE YOU SURE?" FATAL ERROR ELIMINATED AND SECURITY IMPROVED: Under certain circumstances (for example, when users have configured their browser or proxy not to send HTTP Referer headers, for privacy or other reasons), many features in the FeedWordPress administrative interface (such as adding new feeds or changing settings) would hit a fatal error, displaying only a cryptic message reading "Are you sure?" and a blank page following it. This problem has been eliminated by taking advantage of WordPress's nonce functions, which allow the security check which ran into this error to work properly even without receiving an HTTP Referer header. (N.B.: WordPress's nonce functions were first introduced in WordPress 2.0.3. If you're using FeedWordPress with an older version of WordPress, there's no fix for this problem: you'll just need to turn Referer headers back on. Sorry.)

  • BUGFIX: MANUALLY-ALTERED POST STATUS, COMMENT STATUS, AND PING STATUS NO LONGER REVERTED BY POST UPDATES: If you manually altered the post status, comment status, or ping status of a syndicated post from what it was set to when first syndicated -- for example, if you had a feed that was set to bring in new posts as "Pending Review," and you then marked some of the pending posts as "Published" and others as "Unpublished" -- then in previous versions of FeedWordPress, these manual changes to the status would be lost -- so that, for example, your Published or Unpublished articles would revert to Pending Review -- if the source feed made any upates to the item. This could make the Pending Review feature both unreliable and also extremely frustrating to work with. The good news is that this bug has since been fixed: if you manually update the status of a post, it will no longer be reverted if or when the post is updated.

  • BUGFIX: OCCASIONAL FATAL ERROR ON UPDATE ELIMINATED: Under certain limited conditions (specifically, when both the title and the content of a post to be updated are empty), an attempt to update the post would result in a fatal error. This has been fixed.

  • INTERFACE: "CONFIGURE SETTINGS" CONVENIENCE LINK ADDED TO CONFIRMATION MESSAGE WHEN A NEW FEED IS ADDED: When you add a new subscription to FeedWordPress, the message box that appears to confirm it now includes a handy link to the feed's settings subpage, so that you can quickly set up any special settings you may want to set up for the new feed, without having to hunt through the list of all your other subscriptions to pick out the new one.

  • INTERFACE: SIMPLIFYING AND CLARIFYING AUTOMATIC UPDATES SETTINGS. I have removed an interval setting for the cronless automatic updates which has confused many FeedWordPress users. In past versions of FWP, when you turned on automatic updates, you would be presented with a time interval setting which controlled how often FeedWordPress would check for feeds ready to be polled for updates. (That is, it DID NOT control how often feeds would be polled; it controlled how often FeedWordPress would check for feeds that had become ready to poll. The schedule on which feeds became ready for polling was still controlled either by requests encoded in elements within the feed itself, or else according to an internal calculation within FeedWordPress, averaging out to about 1 hour, if the feed did not include any scheduling request elements.) Since many users very often (and understandably) confused the purpose of this setting, and since the setting is for a feature that's actually very unlikely to require any manual control by the user, I have removed the setting; FeedWordPress now simply uses the default value of checking for feeds to poll every 10 minutes.

  • FEEDFINDER PERFORMANCE IMPROVEMENT: FeedWordPress's FeedFinder class now uses array_unique() to make sure that it doesn't waste time repeatedly iterating over and polling the same URI. Props to Camilo (http://projects.radgeek.com/2008/12/14/feedwordpress-20081214/#comment-20090122160414).

2008.1214

  • 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.

  • 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 interface tweaks).

  • BUG WITH TAGS FOR SYNDICATED ARTICLES FIXE

Requires: 3.0 or higher
Compatible up to: 3.5.2
Last Updated: 2013-5-4
Downloads: 763,663

Ratings

3 stars
3.7 out of 5 stars

Support

1 of 12 support threads in the last two months have been resolved.

Got something to say? Need help?

Compatibility

+
=
Not enough data

2 people say it works.
3 people say it's broken.

100,2,2 0,1,0
100,3,3 100,2,2 100,4,4 0,1,0
0,1,0 67,6,4 0,1,0
83,6,5 0,1,0
44,18,8 43,14,6
63,19,12 0,3,0 67,3,2 100,1,1
0,1,0 100,1,1 33,9,3 27,30,8
78,9,7 0,1,0 31,35,11
20,5,1
29,7,2
33,12,4 100,1,1
100,3,3 19,16,3
27,11,3 32,25,8
67,6,4
100,3,3 75,4,3 0,1,0
0,4,0 25,4,1 60,5,3
50,2,1 100,1,1 100,1,1
21,14,3 75,4,3 100,1,1 0,1,0
50,2,1 63,19,12 0,1,0 50,8,4 100,1,1
60,5,3
37,35,13
43,14,6
17,6,1
34,32,11
15,34,5 0,4,0 0,4,0
0,5,0 0,6,0 36,14,5
37,19,7 0,9,0 27,11,3
25,12,3
8,12,1
25,4,1
60,5,3
100,3,3
17,6,1
40,5,2