This release was intended mainly to provide a quick fix for a problem that some users encountered after installing yesterday’s release, 2011.1018. Users whose web hosting environments have the curl module for PHP installed got an important new feature — the ability to set usernames and passwords on feeds to use with HTTP Basic or HTTP Digest authentication. Users who didn’t have the curl module unfortunately got a bug, which caused error messages like “WP HTTP Error: There are no HTTP transports available which can complete the requested request.” to pop up. If you’ve been seeing an error message like that, this release should hopefully fix your problem.

While I had my hands in the code, I went ahead and did some general work to improve the interface and better generalize the HTTP authentication feature for users who do not have the curl module installed. (Most web hosts install it, but not all.) You should hopefully now find the process of adding an authenticated feed much more natural: just put the URL into the Subscribe box and tell FeedWordPress to check it out; when FWP detects that the feed requests login credentials, it will come back and suggest that you enter a username and password before subscribing. When you enter the credentials and re-check the feed, FeedWordPress will allow you to subscribe and immediately set up those credentials for future feed updates. I hope it should all be fairly straightforward, but if you have any questions, don’t hesitate to ask.

Here’s the official changelog for this release:

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

As always, if you notice any problems, have any questions, need any help, or just want to say “Hi,” don’t hesitate to drop me a line via e-mail or through the comment form.

Please remember that your ongoing gifts to the project tip jar, besides being immensely kind, and very much appreciated, are also what make it possible for me to take out the time for ongoing development, timely fixes, and support for the FeedWordPress project.

Now get on out there and check out the new release.

This announcement is actually going to sum up the changes for a couple of different releases of FeedWordPress. The previous public release, 2011.0721, was released some time ago, and has been available at through the WordPress plugin repository, but I was unable to post the announcement on the project due to an unfortunate combination of two factors: a technical breakdown at the old project website, and a cross-country move that effectively prevented me from taking the time to fix the breakdown. Happily, the move is over and, rather than fixing the breakdown, I have simply decided to migrate the project website over to a brand new home. (Same URL as before, but running the latest release of WordPress.) So, without further ado, here are the changes made in today’s release, along with the changes that 2011.0721 had already introduced:

Version 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: syndicateditemguid FILTERS FIXED. Previous versions of
  FeedWordPress theoretically allowed for filters on the syndicateditemguid
  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: syndicateditemguid filters should now
  properly control not only the final database record, but also the initial
  uniqueness test applied to posts.

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

As always, if you notice any problems, have any questions, need any help, or just want to say “Hi,” don’t hesitate to drop me a line via e-mail or through the comment form. Keep in mind that while I do my best to answer any e-mails I receive about FeedWordPress, I’m currently working through a significant backlog of e-mails (somewhere in the high dozens or low hundreds) that accumulated while I was making my move. So for the time being, you can assume I’ll be getting back to you, but it may be a few days before that happens.

Now download and enjoy!

This release has two major functions: first, to provide compatibility with the most recent release of WordPress, WordPress 3.2. If you encountered a fatal error like this:

 Call to undefined method WP_SimplePie_File::WP_SimplePie_File()
in [1]/wp-content/plugins/feedwordpress/feedwordpress.php
on line 1841.

… then this release should eliminate that problem.

Second, to provide some significant performance improvements, mainly in the SQL queries used to determine whether incoming syndicated posts have been previously syndicated, or whether they represent new content. If you’ve been having CPU, memory or other database-related problems with the most recent couple releases of FeedWordPress, this update may offer some relief.

In addition, this release provides some important bugfixes related to sticky posts and duplicate post issues.

Here are the major changes since Version 2011.0602:

• WP 3.2 COMPATIBILITY: ELIMINATES FATAL ERROR “Call to undefined method
  WPSimplePieFile::WPSimplePieFile() in
  [2]/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(postguid) column of the table). The
  code that prepares MySQL queries for previously-syndicated checks has been
  revised to eliminate the MD5(postguid) 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.

If, after making this upgrade, you experience (or continue to experience) any serious issues with WP 3.1.3-3.1.4 or with WP 3.2, please contact me with as detailed as possible a description of what you’re seeing. It will help out a lot if you can include the following diagnostic information. (If you don’t include it, you’ll probably just get an e-mail back from me asking you to provide it.)

1. The versions of WordPress and FeedWordPress you’re currently using.

2. The specific URL(s) of the feed or feeds where you are encountering the problem;

3. An indication of whether you are seeing the problem on all your feeds, or seeing it on some feeds but not on others; and whether you are seeing it on all posts from the affected feeds, or just seeing it on some posts but not on others;

4. The update method that you are using (automatic updates before page load, after page load, manual updates from within the WordPress interface, a cron job…); and

5. Any FeedWordPress-related add-ons you may be using, if any, or any significant special settings you may have set under Syndication –> Posts & Links (for example, whether you have set syndicated posts to come in as Drafts or hold them as Pending, rather than publishing immediately; whether you are making any use of Custom Post Types under the Advanced settings; etc.).

Please remember that your ongoing gifts to the project tip jar, besides being immensely kind, and very much appreciated, and an ongoing source of real satisfaction for which I am deeply greatful, are also what make it possible for me to take out the time for ongoing development, timely fixes, and support for the FeedWordPress project.

Now get on out there and check out the new release.

Here are the major changes since Version 2011.0531:

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

If, after making this upgrade, you continue to experience serious compatibility problems with WP 3.1.3, especially including duplicate posts, please contact me with as detailed as possible a description of what you’re seeing. It will help out a lot if you can include the following diagnostic information:

1. The specific URL(s) of the feed or feeds where you are encountering the problem;

2. An indication of whether you are seeing the problem on all your feeds, or seeing it on some feeds but not on others; and whether you are seeing it on all posts from the affected feeds, or just seeing it on some posts but not on others;

3. The update method that you are using (automatic updates before page load, after page load, manual updates from within the WordPress interface, a cron job…); and

4. Any FeedWordPress-related add-ons you may be using, if any, or any significant special settings you may have set under Syndication –> Posts & Links (for example, whether you have set syndicated posts to come in as Drafts or hold them as Pending, rather than publishing immediately; whether you are making any use of Custom Post Types under the Advanced settings; etc.).

If everything looks alright on your end — and I think that this changes should fix most of the issues that have thus far been reported to me — then great. As usual, any other issues you may have with the release, or any other questions I can help answer, or anything that you would like to see included in a future release, are all good reasons to drop me a line and let me know how I can help you. And as always, your ongoing gifts from the FWP user community to the project tip jar, besides being generous and immensely kind and an ongoing source of real and sustaining gratitude for me as a developer, are also what make ongoing development, timely fixes, and support for FeedWordPress possible.

Now y’all get out of here and enjoy the new release.

Here’s what’s changed since Version 2011.0512:

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

As always, if you have any issues with the release, or any questions I can help answer, 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. If you have an issue to report, please be sure to tell me what version of FeedWordPress you’re using, what version of WordPress you’re using it with, which web browser you are using to view the FeedWordPress user interface, and try to tell me, as clearly as possible, (1) what you were trying to do, (2) what the circumstances were, (3) what you expected to see, and (4) what you ended up seeing instead.

Please remember that your generous gifts to the project tip jar make ongoing development, compatibility releases and support for FeedWordPress possible.

Download and enjoy!

This announcement will actually cover details for a couple of maintenance releases that I’ve pushed out since 2010.0905. This is mainly a maintenance release, with a number of small tweaks around the edges, most of them for better internal performance or organization, but — if you’re upgrading from 2010.0905 — it includes one important, major performance improvement. And it includes a number of changes which should make it much quicker and much less painful to troubleshoot if you encounter any problems with your feeds. Besides having brought the ChangeLog up to date with the most recent version of the code, here are some of the main things that have changed:

Changes since Version 2010.0905

• BUGFIX: AVOID 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). You can also use it to include private parameters with values that you do not wish to make publicly visible when a syndicated post displays the URL of its source feed — such as API keys or passwords.

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

Changes since Version 2011.0211.2

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

As always…

As always, if you have any issues with the release, or any questions I can help answer, 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. If you have an issue to report, please be sure to tell me what version of FeedWordPress you’re using, what version of WordPress you’re using it with, which web browser you are using to view the FeedWordPress user interface, and try to tell me, as clearly as possible, (1) what you were trying to do, (2) what the circumstances were, (3) what you expected to see, and (4) what you ended up seeing instead.

Please remember that your generous gifts to the project tip jar make ongoing development and support for FeedWordPress possible.

Now get on out there, download and enjoy!

FeedWordPress 2010.0905 is now available for download.

I’ve pushed out this release quickly because it contains fixes to an important issue that y’all helped me discover in early user reports back about FeedWordPress 2010.0903. As I mentioned in the release notes, the new release of FeedWordPress has some extensive internal changes to allow for a great deal more flexibility in how it handles Categories and Tags (up to and including support for custom taxonomies provided by plugins). Unfortunately, the changes introduced a bug, due to the fact that the new method used to insert Categories and Tags in WordPress 3 screens the terms to be inserted by the current logged-in user’s capabilities. Which is fine for normal operations within the WordPress administrative interface; but since automatic updates and updates from FeedWordPress cron jobs are typically carried out without any user logged in whose credentials could be checked, this meant that several users noticed posts being inserted with only the category Uncategorized, and with no Tags. Which presents a problem.

Fortunately, the problem has been fixed in today’s quick upgrade:

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

All you need to do to apply the fix is download the newest release and drop it into place in your WordPress plugins directory. As always, if you have any issues with the release, or any questions I can help answer, 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. If you have an issue to report, please be sure to tell me what version of FeedWordPress you’re using, what version of WordPress you’re using it with, which web browser you are using to view the FeedWordPress user interface, and try to tell me, as clearly as possible, (1) what you were trying to do, (2) what the circumstances were, (3) what you expected to see, and (4) what you ended up seeing instead.

Download and enjoy!.

Now stop just a minute. Before you proceed, be advised: FeedWordPress 2010.0903 has been thoroughly tested for compatibility with WordPress 3.0. It also requires WordPress 3.0. If you do not have WordPress 3.0 installed, and aren’t yet ready to make the upgrade, you should not attempt to upgrade to this version of FeedWordPress, until you are ready to make the upgrade to WP3.

This release includes a big passle of improvements, fixes, and new features. Some of them have been a long time coming; others are new and fancy. For the fixes, you may be most interested in a fix which apparently solves a really vexing vanishing act that Syndicated Sources performed for some users on various versions of Internet Explorer — where a big chunk of the user interface would suddenly disappear as soon as you added your first feed. You may also notice some of the new features, like subscribing to multiple feeds or the reductions in memory consumption. Many of the best changes, though you may not even notice — a great deal of the improvements are in low-level interface work, and if I’ve done my job right it will make your life a few minutes more pleasant every day, without you hardly even noticing it. Many of them are improvements under the hood, which are mainly intended for uber-geeks, hotrodders, or — and here is where it matters for the rest of you — Add-On and Filter Developers, who will have that much more of a chance to enrich the FeedWordPress ecosystem. But there’s also plenty that should be right out on the surface, for anyone to see, and I hope you enjoy it.

Here’s a breakdown of some of the major changes since the previous release:

• 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 <geo:lat> tag. Huzzah!

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

Download and enjoy! If you have any issues with the release, or any questions I can help answer, 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. If you have an issue to report, please be sure to tell me what version of FeedWordPress you’re using, what version of WordPress you’re using it with, which web browser you are using to view the FeedWordPress user interface, and try to tell me, as clearly as possible,

One of the remarkable fact about this release is the number of the new features in this release — including improved namespace support, subscription to multiple feeds, and custom post type and taxonomy support — that I was able to make due to the generous support of FeedWordPress users, whose gifts made it possible for me to devote a several solid days to some major new conveniences and some significant internal overhauls that have dramatically improved FeedWordPres’s flexibility and power. I’d like to thank all the FWP users who have helped make ongoing development possible. It’s really flattering, y’all, and I’m incredibly grateful that you’ve made it possible for me to devote the needed time to this project.

As always, please remember that your generous gifts to the project tip jar make ongoing development, quick fixes and timely support for FeedWordPress possible.

Now get out there and enjoy FeedWordPress 2010.0903!

I would like to suggest and this idea is withdrawn from the pligg module. they had a code that automatically fetches the website thumbnail in rss import module. If a add on as such could be built or could be integrated in core , to automatically add the website snap from snapping services and add that with the excerpt, it would be rocking.
Hope there would be plausible discussion in this regard.

Thanks and Regards.

My incoming atom feed looks like this:

…

…
33.831032 -117.893439
…

…

FWP should allow me to set “Custom Post Settings” which sets “Custom fields can be used to add extra metadata to a post that you can use in themes.”
Syndication -> Post & Links -> Custom Post Settings

My key/value looks like this:
Key: wpgeorsspt
Value: $(georss:point)

But the field never gets created or filled in my posts.

Is this because FWP does not support GEORSS elements?