FeedWordPress Development Version — Revision 409700: Settings: allow for a setting to cap the total number of polls per general …

I recently committed the following change to the Development Version of FeedWordPress:

Settings: allow for a setting to cap the total number of polls per general update. No UI yet, but soon.

This change will be part of the next public release of FeedWordPress. Interested? Curious? You can check out the details at the WordPress plugin repository ...

Posted in Log

FeedWordPress Development Version — Revision 409700: Settings: allow for a setting to cap the total number of polls per general …

I recently committed the following change to the Development Version of FeedWordPress:

Settings: allow for a setting to cap the total number of polls per general update. No UI yet, but soon.

This change will be part of the next public release of FeedWordPress. Interested? Curious? You can check out the details at the WordPress plugin repository ...

Posted in Log

FeedWordPress Development Version — Revision 409685: Update Scheduling: improvements to handling of feed-requested update …

I recently committed the following change to the Development Version of FeedWordPress:

Update Scheduling: improvements to handling of feed-requested update scheduling. Include a time-staggering fudge factor for all update schedules, including feed-requested ones. If a user sets a longer interval between updates than is requested by the feed, user can choose whether to speed up at feed's request, or to stick to FWP's normal schedule.

This change will be part of the next public release of FeedWordPress. Interested? Curious? You can check out the details at the WordPress plugin repository ...

Posted in Log

FeedWordPress Development Version — Revision 409685: Update Scheduling: improvements to handling of feed-requested update …

I recently committed the following change to the Development Version of FeedWordPress:

Update Scheduling: improvements to handling of feed-requested update scheduling. Include a time-staggering fudge factor for all update schedules, including feed-requested ones. If a user sets a longer interval between updates than is requested by the feed, user can choose whether to speed up at feed's request, or to stick to FWP's normal schedule.

This change will be part of the next public release of FeedWordPress. Interested? Curious? You can check out the details at the WordPress plugin repository ...

Posted in Log

FeedWordPress Development Version — Revision 409662: Syndicated Sources: provide some better copy and more clear language about …

I recently committed the following change to the Development Version of FeedWordPress:

Syndicated Sources: provide some better copy and more clear language about where scheduling decisions come from.

This change will be part of the next public release of FeedWordPress. Interested? Curious? You can check out the details at the WordPress plugin repository ...

Posted in Log

FeedWordPress Development Version — Revision 409662: Syndicated Sources: provide some better copy and more clear language about …

I recently committed the following change to the Development Version of FeedWordPress:

Syndicated Sources: provide some better copy and more clear language about where scheduling decisions come from.

This change will be part of the next public release of FeedWordPress. Interested? Curious? You can check out the details at the WordPress plugin repository ...

Posted in Log

FeedWordPress 2011.0706: WordPress 3.2 compatibility, better performance

FeedWordPress version 2011.0706 is now available for download..

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

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.