| @@ -1,266 +1,291 @@ | ||
| 1 | 1 | === FeedWordPress === |
| 2 | -Contributors: radgeek | |
| 3 | -Donate link: https://fwpplugin.com/donate/ | |
| 2 | +Contributors: Charles Johnson | |
| 3 | +Donate link: http://feedwordpress.radgeek.com/ | |
| 4 | 4 | Tags: syndication, aggregation, feed, atom, rss |
| 5 | 5 | Requires at least: 4.5 |
| 6 | -Tested up to: 7.0 | |
| 7 | -Stable tag: 2026.0517 | |
| 8 | -License: GPLv2 or later | |
| 9 | -License URI: https://www.gnu.org/licenses/gpl-2.0.html | |
| 6 | +Tested up to: 4.7 | |
| 7 | +Stable tag: 2016.1213 | |
| 10 | 8 | |
| 11 | -FeedWordPress syndicates content from feeds you choose into your WordPress weblog. | |
| 9 | +FeedWordPress syndicates content from feeds you choose into your WordPress weblog. | |
| 12 | 10 | |
| 13 | 11 | == Description == |
| 14 | 12 | |
| 15 | -* Author: [C. Johnson](https://fwpplugin.com/contact/) | |
| 16 | -* Project URI: <http://fwpplugin.com/> | |
| 13 | +* Author: [Charles Johnson](http://radgeek.com/contact) | |
| 14 | +* Project URI: <http://feedwordpress.radgeek.com/> | |
| 17 | 15 | * License: GPL 2. See License below for copyright jots and tittles. |
| 18 | 16 | |
| 19 | -FeedWordPress is an Atom/RSS aggregator for WordPress. It syndicates content from feeds that you choose into your WordPress weblog, and then the content it syndicates appears as a series of special posts in your WordPress posts database. If you syndicate several feeds then you can use WordPress's posts database and templating engine as the back-end of an aggregation ("planet") website. It was developed, originally, as a utility/hobby project, because I needed a more flexible replacement for [Planet][] for aggregator sites that I administered. | |
| 17 | +FeedWordPress is an Atom/RSS aggregator for WordPress. It syndicates content | |
| 18 | +from feeds that you choose into your WordPress weblog; the content it syndicates | |
| 19 | +appears as a series of special posts in your WordPress posts database. If you | |
| 20 | +syndicate several feeds then you can use WordPress's posts database and | |
| 21 | +templating engine as the back-end of an aggregation ("planet") website. It was | |
| 22 | +developed, originally, because I needed a more flexible replacement for | |
| 23 | +[Planet][] to use at Feminist Blogs, an aggregator site that I used to administer. | |
| 20 | 24 | |
| 21 | -[Planet]: https://web.archive.org/web/20051029095046/http://www.planetplanet.org/ | |
| 25 | +[Planet]: http://www.planetplanet.org/ | |
| 22 | 26 | |
| 23 | -FeedWordPress is designed with flexibility, ease of use, and ease of configuration in mind. You'll need a working installation of WordPress (version [4.5][] or later), and it helps to have SFTP or FTP access to your web host. The ability to create cron jobs on your web host is helpful but not required. | |
| 27 | +FeedWordPress is designed with flexibility, ease of use, and ease of | |
| 28 | +configuration in mind. You'll need a working installation of WordPress (version | |
| 29 | +[3.0] or later), and also FTP or SFTP access to your web host. The ability to | |
| 30 | +create cron jobs on your web host is helpful but not required. You *don't* need | |
| 31 | +to tweak any plain-text configuration files and you *don't* need shell access | |
| 32 | +to your web host to make it work. (Although, I should point out, web hosts that | |
| 33 | +*don't* offer shell access are *bad web hosts*.) | |
| 24 | 34 | |
| 25 | - [WordPress]: https://wordpress.org/ | |
| 26 | - [4.5]: http://codex.wordpress.org/Version_4.5 | |
| 35 | + [WordPress]: http://wordpress.org/ | |
| 36 | + [WordPress MU]: http://mu.wordpress.org/ | |
| 37 | + [3.0]: http://codex.wordpress.org/Version_3.0 | |
| 27 | 38 | |
| 28 | 39 | == Installation == |
| 29 | 40 | |
| 30 | 41 | To use FeedWordPress, you will need: |
| 31 | 42 | |
| 32 | -* an installed and configured copy of [WordPress](https://wordpress.org/) (version 4.5 or later). | |
| 43 | +* an installed and configured copy of [WordPress][] or [WordPress MU][] | |
| 44 | + (version 3.0 or later). | |
| 33 | 45 | |
| 34 | -* the ability to install new plugins on your site using either WordPress's Plugins Repository, SFTP, FTP or shell access to your web host | |
| 46 | +* FTP, SFTP or shell access to your web host | |
| 35 | 47 | |
| 36 | 48 | = New Installations = |
| 37 | 49 | |
| 38 | -1. Download the FeedWordPress installation package and extract the files on your computer. | |
| 50 | +1. Download the FeedWordPress installation package and extract the files on | |
| 51 | + your computer. | |
| 39 | 52 | |
| 40 | -2. Create a new directory named `feedwordpress` in the `wp-content/plugins` directory of your WordPress installation. Use an FTP or SFTP client to upload the contents of your FeedWordPress archive to the new directory that you just created on your web host. | |
| 53 | +2. Create a new directory named `feedwordpress` in the `wp-content/plugins` | |
| 54 | + directory of your WordPress installation. Use an FTP or SFTP client to | |
| 55 | + upload the contents of your FeedWordPress archive to the new directory | |
| 56 | + that you just created on your web host. | |
| 41 | 57 | |
| 42 | 58 | 3. Log in to the WordPress Dashboard and activate the FeedWordPress plugin. |
| 43 | 59 | |
| 44 | -4. Once the plugin is activated, a new **Syndication** section should appear in your WordPress admin menu. Click here to add new syndicated feeds, set up configuration options, and determine how FeedWordPress will check for updates. For help, see the [FeedWordPress Quick Start][] page. | |
| 45 | - | |
| 60 | +4. Once the plugin is activated, a new **Syndication** section should | |
| 61 | + appear in your WordPress admin menu. Click here to add new syndicated | |
| 62 | + feeds, set up configuration options, and determine how FeedWordPress | |
| 63 | + will check for updates. For help, see the [FeedWordPress Quick Start][] | |
| 64 | + page. | |
| 65 | + | |
| 46 | 66 | [FeedWordPress Quick Start]: http://feedwordpress.radgeek.com/wiki/quick-start |
| 47 | 67 | |
| 48 | 68 | = Upgrades = |
| 49 | 69 | |
| 50 | -To *upgrade* an existing installation of FeedWordPress to the most recent release: | |
| 70 | +To *upgrade* an existing installation of FeedWordPress to the most recent | |
| 71 | +release: | |
| 51 | 72 | |
| 52 | -1. Download the FeedWordPress installation package and extract the files on your computer. | |
| 73 | +1. Download the FeedWordPress installation package and extract the files on | |
| 74 | + your computer. | |
| 53 | 75 | |
| 54 | -2. Upload the new PHP files to `wp-content/plugins/feedwordpress`, overwriting any existing FeedWordPress files that are there. | |
| 76 | +2. Upload the new PHP files to `wp-content/plugins/feedwordpress`, | |
| 77 | + overwriting any existing FeedWordPress files that are there. | |
| 78 | + | |
| 79 | +3. Log in to your WordPress administrative interface immediately in order | |
| 80 | + to see whether there are any further tasks that you need to perform | |
| 81 | + to complete the upgrade. | |
| 55 | 82 | |
| 56 | -3. Log in to your WordPress administrative interface immediately in order to see whether there are any further tasks that you need to perform to complete the upgrade. | |
| 83 | +4. Enjoy your newer and hotter installation of FeedWordPress | |
| 57 | 84 | |
| 58 | -4. Enjoy your newer and hotter installation of FeedWordPress! | |
| 59 | - | |
| 60 | 85 | == Using and Customizing FeedWordPress == |
| 61 | 86 | |
| 62 | -FeedWordPress has many options which can be accessed through the WordPress Dashboard, and a lot of functionality accessible programmatically through WordPress templates or plugins. For further documentation of the ins and outs, see the documentation at the [FeedWordPress project homepage][]. | |
| 87 | +FeedWordPress has many options which can be accessed through the WordPress | |
| 88 | +Dashboard, and a lot of functionality accessible programmatically through | |
| 89 | +WordPress templates or plugins. For further documentation of the ins and | |
| 90 | +outs, see the documentation at the [FeedWordPress project homepage][]. | |
| 63 | 91 | |
| 64 | 92 | [FeedWordPress project homepage]: http://feedwordpress.radgeek.com/ |
| 65 | 93 | |
| 66 | -== Screenshots == | |
| 67 | - | |
| 68 | -1. Syndicated Sites Settings | |
| 69 | -2. Dashboard widget for Syndicated Sources | |
| 70 | -3. Feed and Update Settings (single feed) | |
| 71 | -4. Feed and Update Settings (defaults for all feeds) | |
| 72 | - | |
| 73 | 94 | == Changelog == |
| 74 | 95 | |
| 75 | -= 2026.0517 = | |
| 76 | - | |
| 77 | -* BUG FIX FOR Custom Post Settings AFTER WordPress/FeedWordPress UPGRADE: If you used "Custom Post Settings" fields in Syndication > Posts to set custom post fields on syndicated articles (either static text or dynamic values using the XPath-like syntax), these may have stopped creating custom settings fields as expected after upgrading FeedWordPress or after upgrading WordPress to the most recent version. This is due to a regression introduced by the SimplePie version compatibility fix in 2025.1209. That has been fixed thanks to a patch submitted by @fl0om on Github; if you noticed that posts were being syndicated but syndicated posts were not assigned, then the custom post setting fields that you expected, upgrading to this point release should hopefully resolve that issue for you. | |
| 78 | - | |
| 79 | -= 2025.1209 = | |
| 80 | - | |
| 81 | -* COMPATIBILITY FIXES FOR WORDPRESS 6.9 (Fixes "PHP Fatal error: Cannot make static method SimplePie\\Parser::declare_html_entities() non static in class FeedWordPie_Parser" error, "PHP Fatal error: Uncaught TypeError: Return value of SimplePie\\File::get_headers() must be of the type array, null returned" error, or "PHP Fatal error: Uncaught TypeError: Argument 1 passed to SimplePie\\File::SimplePie\\{closure}() must be of the type string, array given" error after WordPress 6.9 upgrade): This version includes fixes to critical compatibility issues with WordPress 6.9 and WP 6.9's upgrade to SimplePie 1.9.0+. If you recently upgraded to WordPress 6.9 and noticed problems with updating or accessing your site, or messages about a "Critical issue" or fatal PHP errors in the interface or your error logs then a quick upgrade to this point release should hopefully resolve that issue for you. | |
| 82 | - | |
| 83 | -= 2024.1119 = | |
| 84 | - | |
| 85 | -* COMPATIBILITY FIX FOR WORDPRESS 6.7 (Fixes "Uncaught TypeError: Argument 1 passed to SimplePie\Cache\BaseDataCache::__construct() must implement interface SimplePie\Cache\Base" error after WordPress 6.7 upgrade): This version includes a fix to a critical compatibility issue with SimplePie 1.8.0+'s new requirements for namespaced classes and interfaces. (Updating to WordPress 6.7 also means that you get an update to a more recent version of SimplePie included with the platform; unfortunately, the new version of SimplePie introduces code changes which are no doubt a good idea in the long run, but which broke backward compatibility with the technique that FeedWordPress uses to extend SimplePie classes.) If you recently upgraded to WordPress 6.7 and noticed that FeedWordPress suddenly stopped updating, or that you started seeing messages about a "Critical issue" or fatal PHP errors in the interface or your error logs -- especially when attempting to check feeds for updates within the FeedWordPress admin interface -- then a quick upgrade to this point release should hopefully resolve that issue for you. | |
| 86 | - | |
| 87 | -= 2024.0511 = | |
| 88 | - | |
| 89 | -* COMPATIBILITY FIX FOR "Uncaught TypeError: in_array()" ERROR: This version includes a fix to a fatal error that some users encountered with some versions of PHP 8. If after upgrading to a recent version of FeedWordPress, you encountered a message about a "critical error" or error messages indicating something like "Uncaught TypeError: in_array() Argument #2", then a couple of code changes in this version should hopefully resolve that error for you. | |
| 90 | - | |
| 91 | -= 2024.0428 = | |
| 92 | - | |
| 93 | -* IMPORTANT SECURITY FIX: This version includes an important fix for a security vulnerability reported to me through Wordfence and WordPress support channels. | |
| 94 | - | |
| 95 | - Vulnerability CVE-2024-0839 allowed for an insecure Direct Object Reference which could allow contents of Private, Pending, or otherwise non-Published post objects to be accessed by an attacker possessing or generating the internal guid URI of the post object. This vulnerability has been eliminated in the current version; to protect your site's security PLEASE BE SURE TO UPGRADE AS SOON AS POSSIBLE to version 2024.0428 or later, via the WordPress Plugin Repository or via Github. | |
| 96 | - | |
| 97 | -* ADDITIONAL COMPATIBILITY FIXES AND CODE CLEANUP: This version includes numerous fixes to improve compatibility fixes for ongoing new releases of PHP, and does some additional code clean-up to remove some obsolete methods of generating output, and to do a better job of sanitizing input and escaping output in the FeedWordPress administrative dashboard. It features numerous fixes and improvements contributed by user @GwynethLlewelyn and several new hooks allowing for translation of interface elements. | |
| 98 | - | |
| 99 | -= 2022.0222 = | |
| 100 | - | |
| 101 | -* ADDITIONAL CODE CLEANUP: This version does some additional code clean-up to remove some obsolete methods of generating output, and to do a better job of sanitizing input and escaping output in the FeedWordPress administrative dashboard. | |
| 102 | - | |
| 103 | -= 2022.0204 = | |
| 104 | - | |
| 105 | -* ADDITIONAL CODE CLEANUP: This version does some additional code clean-up to remove some obsolete methods of generating output, and to do a better job of sanitizing input and escaping output in the FeedWordPress administrative dashboard. | |
| 106 | - | |
| 107 | -= 2022.0123 = | |
| 108 | - | |
| 109 | -* IMPORTANT SECURITY FIX: This version includes an important fix for a security vulnerability reported to me through WPScan and WordPress support channels. | |
| 110 | - | |
| 111 | - Vulnerability CVE-2021-25055 allowed for an XSS (Cross-Site Scripting) attack using a specially crafted URL for a page within the FeedWordPress admin interface. (To be exploited, an existing user with login credentials that allow them to access the FeedWordPress dashboard would have to follow the malicious URL and log in.) This vulnerability has been corrected in the current version; to protect your site's security PLEASE BE SURE TO UPGRADE AS SOON AS POSSIBLE to version 2022.0123 or later, via the WordPress Plugin Repository or via Github. | |
| 112 | - | |
| 113 | -* BUG FIXES: Fixes a number of small possible bugs when creating new syndicated posts under unusual conditions -- a sanity check is built in to avoid infinite loops in case of certain unexpected error outcomes when creating new users; some more possible sources of PHP 8 "Countable" warnings are eliminated, etc. | |
| 114 | - | |
| 115 | -= 2021.0713 = | |
| 116 | - | |
| 117 | -* WORDPRESS 5.6, 5.7.x COMPATIBILITY FIXES. This release introduces fixes to annoying or worse warnings resulting from | |
| 118 | - the deprecation of WordPress's built-in WP_Feed_Cache class. This should resolve the problem if you are encountering | |
| 119 | - annoying, worrying, or breaking problems related to the PHP warnings: "Deprecated: class-wp-feed-cache.php is | |
| 120 | - <strong>deprecated</strong> since version 5.6.0", and/or "Message: ./cache is not writable. Make sure you've set the | |
| 121 | - correct relative or absolute path, and that the location is server-writable." | |
| 122 | - | |
| 123 | -* Fixes PHP warning for "count(): Parameter must be an array or an object that implements Countable in | |
| 124 | - .../wp-content/plugins/feedwordpress/feedwordpress.php on line 1566" | |
| 125 | - | |
| 126 | -* Miscellaneous fixes for other missing variable and global warnings. | |
| 127 | - | |
| 128 | -* Code cleanup and reorganization to allow better modularization of error messages, warning dialogs, and extended text. | |
| 129 | - | |
| 130 | -= 2020.0818 = | |
| 131 | - | |
| 132 | -* WORDPRESS 5.5 COMPATIBILITY FIXES, RESOLVES WARNING NOTICES OR WP-ADMIN LOCKOUT. WordPress 5.5 incorporated a newer release of SimplePie, version 1.5.5, which is pretty rad, but FeedWordPress classes that relied on SimplePie 1.3.1's method signatures would then produce PHP warning notices. That should be pretty innocuous, but depending on web server configurations, some users could get locked out of their own wp-admin interface by the display of error notices in the browser at inopportune times. In any case, I have added code to switch between backward-compatible modules for SimplePie 1.3.1 or updated modules compatible with SimplePie 1.5.5, based on the version available in your WordPress installation; so these notices and their untoward effects should be eliminated. | |
| 133 | - | |
| 134 | -* PHP 7.4 COMPATIBILITY FIX: Magic quotes were deprecated and then removed back in PHP 5.x, and in PHP 7.4 the vestigial `get_magic_quotes_gpc()` function has been deprecated. We don't need to worry about it anymore for versions of PHP still supported by WordPress. The reference to the function in the MyPHP utility class caused PHP warnings in more recent versions of PHP; so it has now been removed. | |
| 135 | - | |
| 136 | -* DIVERS BUG FIXES AND PHP WARNING NOTICES RESOLVED, thanks to @oppiansteve's fixes and pull requests. (Thanks!) | |
| 137 | - | |
| 138 | -* JQUERY COMPATIBILITY FIXES, RESOLVES MYSTERIOUS VANISHING FEED SELECTOR IN WP-ADMIN. An upgrade to WordPress's packaged jQuery caused the drop-down box for feed settings (in Syndication > Feeds & Updates, Syndication > Posts & Links, etc.) to vanish shortly after pageload. That was awkward, so I disabled the now-incompatible interface chrome that was causing it to vanish. | |
| 139 | - | |
| 140 | -= 2020.0118 = | |
| 141 | - | |
| 142 | -* WORDPRESS COMPATIBILITY TESTING. It's been some time since a public release of FeedWordPress; so I have tested the plugin functionality with recent versions of WordPress and incorporated a number of PHP 7-compatibility related tweaks. | |
| 143 | - | |
| 144 | -* FEED PARSING FAULT TOLERANCE. If FeedWordPress fails to parse a feed using normal XML functions, it will attempt to convert any named entities that may be causing a problem, and then try to parse again. Props to @inanimatt for utility functions that help make the code go. | |
| 145 | - | |
| 146 | -* PAUSING UPDATES. In Syndication > Feeds & Updates, you can now instruct FeedWordPress to temporarily pause or resume updating feeds -- whatever update method you are using, you can put new updates on hold for a while so that you can fiddle with setings, run tests, or do whatever you need to do before allowing updates to resume. | |
| 147 | - | |
| 148 | -* CODE MODERNIZATION, PHP 7.x COMPATIBILITY AND CLEANUP AND REORGANIZATION. I have been dusting out nooks and crannies in the code and hiving more functionality off into discrete modules. A number of FeedWordPress users have also offered pull requests to eliminate bothersome PHP notices and warnings related to PHP 7.x compatibility -- in particular removing uses of deprecated `each()` functions, and avoiding use of `count()` on null values -- which I have rolled into the main branch release. Props to @manzoorwanijk, @tristanleboss, @martinburchell and @oppiansteve | |
| 149 | - | |
| 150 | -= 2017.1020 = | |
| 151 | - | |
| 152 | -* ADD BOILERPLATE / CREDITS FEATURE AVAILABLE IN POSTS & LINKS SETTINGS PANEL. I have added a new settings panel to the off-the-shelf features of FeedWordPress, under Syndication > Posts & Links (or under the Posts settings page for any individual feed), which allows you to define boilerplate text that should appear in connection with every syndicated post, or with every post syndicated from a particular feed. So, for example, if you want each syndicated post to include a byline reading "This is a syndicated post, reprinted from (LINK TO ORIGINAL SOURCE WEBSITE).", you could set up this byline from within the FeedWordPress settings interface, by going to the Boilerplate / Credits panel, and adding a line to appear BEFORE the CONTENT of each syndicated post, using the text and shortcode "This is a syndicated post, reprinted from [source]." For those of you who have corresponded with me about this feature before, you may be familiar with it from the long-standing "experimental" add-on, FWP+: Add Attribution; I've decided that it's been enough years, and I've had enough requests, that the Add Attribution feature may as well be included in the main FeedWordPress code. | |
| 153 | - | |
| 154 | - Back when FeedWordPress was first created, the assumption was that a well-behaved aggregator would include boilerplate text to indicate the source of syndicated posts, but that the best way to do this was to provide a set of syndication-specific template tags so that the administrator setting up the site could edit their Theme template files with constructs like: | |
| 155 | - | |
| 156 | - <?php if (is_syndicated()) : ?> | |
| 157 | - <p class="byline">This post by <?php the_author(); ?> originally | |
| 158 | - appeared at <a href="<?php the_syndication_source_link(); ?>"><?php | |
| 159 | - the_syndication_source(); ?></a>.</p> | |
| 160 | - <?php else : ?> | |
| 161 | - <p class="byline">By <?php the_author(); ?>.</p> | |
| 162 | - <?php endif; ?> | |
| 163 | - | |
| 164 | - You can still do this, of course, and for maximum expressive power and flexibility, it is certainly the best way to do it. Template Tags are documented here: <http://feedwordpress.radgeek.com/wiki/templates/> However, (1) it requires writing PHP code, which not everyone is comfortable doing; and (2) it requires altering template files within your Theme, which is not always possible, especially given the increasing role that prepackaged commercial themes have come to play in the WordPress ecosystem. So, now, you can get some basic features for adding boilerplate text and attribution credits even without touching your template files, and without having to add custom add-ons for FeedWordPress. Enjoy! | |
| 165 | - | |
| 166 | -* MINOR CODE MODERNIZATION, PHP 7.1 COMPATIBILITY AND BUG FIXES. This project is now 12+ years old (good lord), and there are still some places where code was written at a time when PHP was a very different language from what it is now. Props to @david-robinson-practiceweb for pointing out and sending a pull request to fix some instances where obsolete PHP reference notation (`&$q` on parameters and so on) created a compatibility problem for PHP 7.1. Props to an email correspondent for pointing out a place in SyndicatedPost where excerpts should be generated from post content using encoding-aware mb_substr(), instead of naively running them through substr(). I've begun making some efforts throughout to begin auditing some of the creakiest old code in the project, to update what needs updating and improve documentation throughout. | |
| 167 | - | |
| 168 | -= 2017.0913 = | |
| 169 | - | |
| 170 | -* PARTIAL FIX FOR 2X DUPLICATE POSTS APPEARING ON DUAL HTTP/HTTPS SITES: Some users reported an issue in which their FeedWordPress sites, which are over both insecure HTTP and over HTTPS, would pick up exactly 2 copies of every post or almost every post from certain feeds, and where the guids for each of the pair of duplicate posts would look exactly alike, except for a difference in the protocol, for example: | |
| 171 | - | |
| 172 | - http://www.example.com/?guid=c1cd28da39e8d7babcf6499983aca545 | |
| 173 | - https://www.example.com/?guid=c1cd28da39e8d7babcf6499983aca545 | |
| 174 | - | |
| 175 | - ... where www.example.com is the server that your own copy of FeedWordPress is installed. This release of FeedWordPress normalizes post guid prefixes so as to avoid or limit the scope of this problem. | |
| 176 | - | |
| 177 | -* PHP 7 Compatibility: eliminate remaining sources of PHP 7 compatibility-check failures -- remove the use of depreciated mysql_error() function, and make sure all classes make use of __construct() convention for constructors. | |
| 178 | - | |
| 179 | -* AVOID "PHP Warning: shell_exec() has been disabled for security reasons in [...]/feedwordpress/feeds-page.php on line 197": FeedWordPress uses the PHP shell_exec() function in a very narrowly limited way for information gathering, trying to find the real path to curl or wget on your system, so that it can give as realistic as possible a recommendation for the sample crontab line displayed in Syndication > Feeds & Updates. Some web hosting environments disable shell_exec for security reasons (since it could in theory be used to do a lot more stuff than the very limited information gathering FWP uses it for); in which case, this part of the code in FeedWordPress could spit out a nasty-looking and potentially worrisome-looking error message. So, now this code is fenced with checks to make sure that shell_exec is available, before FWP attempts to make use of it. | |
| 180 | - | |
| 181 | 96 | = 2016.1213 = |
| 182 | 97 | |
| 183 | -* WORDPRESS BACKWARD COMPATIBILITY FOR VERSIONS [4.5, 4.7]: This change fixes a fatal PHP error (on some web server configurations you'd see the message "Fatal error: require_once(): Failed opening required '[...]/wp-includes/class-wp-feed-cache.php'" on others, you might just see an HTTP 500 Internal Server Error or a blank page) when using FeedWordPress with versions of WordPress before 4.7. A change that I introduced to avoid a code module that had been deprecated in version 4.7 ended up relying on code modules that were only introduced as of version 4.7; so now, instead, FeedWordPress attempts to detect which modules the current version of the WordPress core makes available, and load the right modules depending on your WordPress version. | |
| 98 | +* WORDPRSS BACKWARD COMPATIBILITY FOR VERSIONS [4.5, 4.7]: This change fixes | |
| 99 | + a fatal PHP error (on some web server configurations you'd see the message | |
| 100 | + "Fatal error: require_once(): Failed opening required '[...]/wp-includes/class-wp-feed-cache.php'" | |
| 101 | + on others, you might just see an HTTP 500 Internal Server Error or a blank | |
| 102 | + page) when using FeedWordPress with versions of WordPress before 4.7. A | |
| 103 | + change that I introduced to avoid a code module that had been deprecated in | |
| 104 | + version 4.7 ended up relying on code modules that were only introduced as | |
| 105 | + of version 4.7; so now, instead, FeedWordPress attempts to detect which | |
| 106 | + modules the current version of the WordPress core makes available, and load | |
| 107 | + the right modules depending on your WordPress version. | |
| 184 | 108 | |
| 185 | - In theory, up to this point, FeedWordPress supported any version of WordPress from version 3.0 onward. In practice, version 3.0 was released over 6 years ago, and I can realistically commit only to testing out new releases of FeedWordPress with a few prior versions of WordPress; so I've updated the "Requires at least" field to version 4.5, the first major release issued in 2016. If you've really got to use FeedWordPress with older versions of WordPress, it will probably still work with any moderately modern release of WordPress, but I won't promise to keep it working with releases of WordPress that are more than about a year old. | |
| 186 | - | |
| 109 | + In theory, up to this point, FeedWordPress supported any version of | |
| 110 | + WordPress from version 3.0 onward. In practice, version 3.0 was released | |
| 111 | + over 6 years ago, and I can realistically commit only to testing out new | |
| 112 | + releases of FeedWordPress with a few prior versions of WordPress; so I've | |
| 113 | + updated the "Requires at least" field to version 4.5, the first major | |
| 114 | + release issued in 2016. If you've really got to use FeedWordPress with | |
| 115 | + older versions of WordPress, it will probably still work with any moderately | |
| 116 | + modern release of WordPress, but I won't promise to keep it working with | |
| 117 | + releases of WordPress that are more than about a year old. | |
| 118 | + | |
| 187 | 119 | = 2016.1211 = |
| 188 | 120 | |
| 189 | 121 | * WORDPRESS COMPATIBILITY: Tested with new versions of WordPress up to 4.7. |
| 190 | 122 | |
| 191 | -* PHP WARNINGS UNDER WP 4.7: Eliminated cause of a PHP warning under WP 4.7 "Parameter 1 to FeedWordPressHTTPAuthenticator::set_auth_options expected to be reference" Warnings were due to a change in how http_api_curl hook is sometimes called in WP 4.7; so I changed the signature of the event handling method to avoid the notice. Props to @cogdog, @froomkin, @gwynethllewelyn et al. for flagging the issue and @garymarkfuller for suggesting a preliminary fix to the issue that was fairly similar to the solution I ended up adopting. | |
| 123 | +* PHP WARNINGS UNDER WP 4.7: Eliminated cause of a PHP warning under WP 4.7 | |
| 124 | + "Parameter 1 to FeedWordPressHTTPAuthenticator::set_auth_options expected to be reference" | |
| 125 | + Warnings were due to a change in how http_api_curl hook is sometimes called | |
| 126 | + in WP 4.7; so I changed the signature of the event handling method to avoid | |
| 127 | + the notice. Props to @cogdog, @froomkin, @gwynethllewelyn et al. for flagging | |
| 128 | + the issue and @garymarkfuller for suggesting a preliminary fix to the issue | |
| 129 | + that was fairly similar to the solution I ended up adopting. | |
| 192 | 130 | |
| 193 | -* PHP 7 and PHP Strict Standards compatibility changes: @alexiskulash @daidais and @zoul0813 all sent pull requests through Github to fix some issues from a very old code base that has made its way from PHP 3.x through 5.x to the roll-out of PHP 7. Class methods should now fare better under modern versions of PHP and generate fewer "Deprecated" notices. | |
| 131 | +* PHP 7 and PHP Strict Standards compatibility changes: @alexiskulash @daidais | |
| 132 | + and @zoul0813 all sent pull requests through Github to fix some issues from | |
| 133 | + a very old code base that has made its way from PHP 3.x through 5.x to the | |
| 134 | + roll-out of PHP 7. Class methods should now fare better under modern versions | |
| 135 | + of PHP and generate fewer "Deprecated" notices. | |
| 194 | 136 | |
| 195 | -* IMPROVEMENTS TO SCHEDULED AND AUTOMATIC UPDATES: use wp_loaded hook to check for magic URL parameters and to execute updates, to do pageload-based automatic updates, etc. Ensures that anything plugins or themes need to do in init to set up custom post types, taxonomies, etc. will be done before the update_feedwordpress updates are attempted. If you saw posts not getting put into the correct custom post type or custom taxonomies or similar problems when performing scheduled updates, but the problem seemed to go away when you manually performed updates through the wp-admin interface, then you might be able to solve those problems with this update. | |
| 137 | +* IMPROVEMENTS TO SCHEDULED AND AUTOMATIC UPDATES: use wp_loaded hook to check | |
| 138 | + for magic URL parameters and to execute updates, to do pageload-based automatic | |
| 139 | + updates, etc. Ensures that anything plugins or themes need to do in init to set | |
| 140 | + up custom post types, taxonomies, etc. will be done before the update_feedwordpress | |
| 141 | + updates are attempted. If you saw posts not getting put into the correct custom | |
| 142 | + post type or custom taxonomies or similar problems when performing scheduled updates, | |
| 143 | + but the problem seemed to go away when you manually performed updates through the | |
| 144 | + wp-admin interface, then you might be able to solve those problems with this update. | |
| 196 | 145 | |
| 197 | 146 | = 2016.0420 = |
| 198 | 147 | |
| 199 | 148 | * WORDPRESS COMPATIBILITY: Tested with new versions of WordPress up to 4.5. |
| 200 | 149 | |
| 201 | -* FILTERS AND ADD-ONS: Allow filters and add-ons to filter terms and taxonomy (categories, tags, custom taxonomies, etc.) more thoroughly and more fine-grainedly using syndicated_post_terms_match, syndicated_post_terms_match_{taxonomy}, syndicated_post_terms_unfamiliar, syndicated_post_terms_mapping, syndicated_item_feed_terms, and syndicated_item_preset_terms filters. | |
| 150 | +* FILTERS AND ADD-ONS: Allow filters and add-ons to filter terms and taxonomy | |
| 151 | + (categories, tags, custom taxonomies, etc.) more thoroughly and more | |
| 152 | + fine-grainedly using syndicated_post_terms_match, syndicated_post_terms_match_{taxonomy}, | |
| 153 | + syndicated_post_terms_unfamiliar, syndicated_post_terms_mapping, | |
| 154 | + syndicated_item_feed_terms, and syndicated_item_preset_terms filters. | |
| 202 | 155 | |
| 203 | -* FILTERS AND ADD-ONS: Globals $fwp_channel and $fwp_feedmeta REMOVED. These global variables, originally introduced to allow filters access to information about the source feed in `syndicated_item` filters were deprecated 6+ years ago. If you have any filters or add-ons which still depend on these global variables, you've been using obsolete techniques and 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>. | |
| 156 | +* FILTERS AND ADD-ONS: Globals $fwp_channel and $fwp_feedmeta REMOVED. | |
| 157 | + These global variables, originally introduced to allow filters access to | |
| 158 | + information about the source feed in `syndicated_item` filters were | |
| 159 | + deprecated 6+ years ago. If you have any filters or add-ons which still | |
| 160 | + depend on these global variables, you've been using obsolete techniques | |
| 161 | + and you should see about fixing them to access data about the source feed | |
| 162 | + using the SyndicatedPost::link element instead. For documentation, see | |
| 163 | + the FeedWordPress documentation wiki at | |
| 164 | + <http://feedwordpress.radgeek.com/wiki/syndicatedpost> and | |
| 165 | + <http://feedwordpress.radgeek.com/wiki/syndicatedlink>. | |
| 204 | 166 | |
| 205 | -* BUGFIX: Syndication > Diagnostics HTTP diagnostic test widget was broken due to a dumb error on my part. Now fixed. | |
| 167 | +* BUGFIX: Syndication > Diagnostics HTTP diagnostic test widget was broken due to | |
| 168 | + a dumb error on my part. Now fixed. | |
| 169 | + | |
| 170 | +* SMALL CODING CHANGES: Lots of small changes to code organization, incorporation | |
| 171 | + of some PHP 5.x coding conventions, etc. | |
| 206 | 172 | |
| 207 | -* SMALL CODING CHANGES: Lots of small changes to code organization, incorporation of some PHP 5.x coding conventions, etc. | |
| 208 | - | |
| 209 | 173 | = 2015.0514 = |
| 210 | 174 | |
| 211 | -* IMPORTANT SECURITY UPDATE: This version includes two important fixes for potential security vulnerabilities reported to me through support channels. | |
| 175 | +* IMPORTANT SECURITY UPDATE: This version includes two important fixes for | |
| 176 | + potential security vulnerabilities reported to me through support channels. | |
| 177 | + | |
| 178 | + The first is a common problem across several plugins due to an ambiguity in | |
| 179 | + the WordPress documentation and a change in the behavior of WordPress's | |
| 180 | + built-in add_query_arg() and remove_query_arg() functions | |
| 181 | + which could, under certain low-probability conditions, allow for potential | |
| 182 | + XSS attack vectors. This fixes issue # 39 | |
| 183 | + reported at <https://github.com/radgeek/feedwordpress/issues/39> | |
| 184 | + Thanks to github.com/quassy | |
| 185 | + | |
| 186 | + The second is a security vulnerability fixes a security vulnerability that | |
| 187 | + was reported to me privately (thanks to Adrián M. F.) which, under other | |
| 188 | + low-probability conditions, could allow for SQL insertion attacks by | |
| 189 | + a malicious user with access to login credentials, which would compromise | |
| 190 | + data security. | |
| 212 | 191 | |
| 213 | - The first is a common problem across several plugins due to an ambiguity in the WordPress documentation and a change in the behavior of WordPress's built-in add_query_arg() and remove_query_arg() functions which could, under certain low-probability conditions, allow for potential XSS attack vectors. This fixes issue # 39 reported at <https://github.com/radgeek/feedwordpress/issues/39> Thanks to github.com/quassy | |
| 192 | + It is *IMPORTANT* and worth your while to upgrade FeedWordPress as soon as | |
| 193 | + possible in order to eliminate these vulnerabilities. If you have any | |
| 194 | + questions or if there is something blocking you from making the upgrade | |
| 195 | + which you need my help with, don't hesitate to get in touch. | |
| 214 | 196 | |
| 215 | - The second fixes a security vulnerability that was reported to me privately (thanks to Adrián M. F.) which, under other low-probability conditions, could allow for SQL insertion attacks by a malicious user with access to login credentials, which would compromise data security. | |
| 197 | +* ADMIN UI BUGFIX: "Update Now" button in feeds setting pages should now work | |
| 198 | + once again instead of causing a PHP fatal error. See | |
| 199 | + <https://github.com/radgeek/feedwordpress/issues/46> | |
| 200 | + | |
| 201 | +* SEVERAL OTHER SMALL BUG FIXES. See <https://github.com/radgeek/feedwordpress/issues/32> | |
| 202 | + <https://github.com/radgeek/feedwordpress/issues/30> | |
| 203 | + <https://github.com/radgeek/feedwordpress/issues/29> | |
| 204 | + etc. | |
| 216 | 205 | |
| 217 | - It is *IMPORTANT* and worth your while to upgrade FeedWordPress as soon as possible in order to eliminate these vulnerabilities. If you have any questions or if there is something blocking you from making the upgrade which you need my help with, don't hesitate to get in touch. | |
| 218 | - | |
| 219 | -* ADMIN UI BUGFIX: "Update Now" button in feeds setting pages should now work once again instead of causing a PHP fatal error. See <https://github.com/radgeek/feedwordpress/issues/46> | |
| 220 | - | |
| 221 | -* SEVERAL OTHER SMALL BUG FIXES. See <https://github.com/radgeek/feedwordpress/issues/32> <https://github.com/radgeek/feedwordpress/issues/30> <https://github.com/radgeek/feedwordpress/issues/29> etc. | |
| 222 | - | |
| 223 | 206 | = 2014.0805 = |
| 224 | 207 | |
| 225 | -* FILTERS AND ADD-ONS: A number of new hooks for filters and add-ons to further customize the behavior of FWP have been added. | |
| 208 | +* FILTERS AND ADD-ONS: A number of new hooks for filters and add-ons to | |
| 209 | + further customize the behavior of FWP have been added. | |
| 226 | 210 | |
| 227 | -* COMPATIBILITY/BUGFIX: Many users saw odd characters, especially "n," appearing in posts in versions of WordPress from 3.6 on, due to a change in when the API expects HTML data for posts to be slashed and when it does not. This has been fixed, so that the junk characters should no longer appear, regardless of your version of WordPress. | |
| 211 | +* COMPATIBILITY/BUGFIX: Many users saw odd characters, especially "n," | |
| 212 | + appearing in posts in versions of WordPress from 3.6 on, due to a change | |
| 213 | + in when the API expects HTML data for posts to be slashed and when it | |
| 214 | + does not. This has been fixed, so that the junk characters should no | |
| 215 | + longer appear, regardless of your version of WordPress. | |
| 228 | 216 | |
| 229 | -* BUGFIX: A bug preventing FWP from saving categories assigned under Syndication > Categories & Tags has been fixed. | |
| 217 | +* BUGFIX: A bug preventing FWP from saving categories assigned under | |
| 218 | + Syndication > Categories & Tags has been fixed. | |
| 219 | + | |
| 220 | +* BUGFIX: Post-editing related metaboxes should now show up when you edit | |
| 221 | + items of any post type, including custom types, not only normal WordPress | |
| 222 | + posts. | |
| 223 | + | |
| 224 | +* BUGFIX: A bug in the admin UI that caused the "Alternative Feeds" / | |
| 225 | + "Find Feeds" box to throw a permissions error has been fixed. | |
| 226 | + | |
| 227 | +* BUGFIX: A bug preventing proper mapping of categories and other terms in | |
| 228 | + 2013.0504 has been fixed. | |
| 229 | + | |
| 230 | +* BUGFIX: A number of small fixes contributed through Github by Flynsarmy | |
| 231 | + should eliminate PHP warnings for many users on several methods that are | |
| 232 | + called as static methods within FeedWordPress. | |
| 230 | 233 | |
| 231 | -* BUGFIX: Post-editing related metaboxes should now show up when you edit items of any post type, including custom types, not only normal WordPress posts. | |
| 232 | - | |
| 233 | -* BUGFIX: A bug in the admin UI that caused the "Alternative Feeds" / "Find Feeds" box to throw a permissions error has been fixed. | |
| 234 | - | |
| 235 | -* BUGFIX: A bug preventing proper mapping of categories and other terms in 2013.0504 has been fixed. | |
| 236 | - | |
| 237 | -* BUGFIX: A number of small fixes contributed through Github by Flynsarmy should eliminate PHP warnings for many users on several methods that are called as static methods within FeedWordPress. | |
| 238 | - | |
| 239 | 234 | = 2013.0504 = |
| 235 | + | |
| 236 | +* BUGFIX: PHP 5.4 compatibility -- includes some more extensive fixes to | |
| 237 | + compatibility issues with PHP 5.4's handling of global variables | |
| 240 | 238 | |
| 241 | -* BUGFIX: PHP 5.4 compatibility -- includes some more extensive fixes to compatibility issues with PHP 5.4's handling of global variables | |
| 239 | +* DIAGNOSTICS: New diagnostics settings added to help track behavior of | |
| 240 | + terms (categories, post tags, etc.) for syndicated posts. | |
| 242 | 241 | |
| 243 | -* DIAGNOSTICS: New diagnostics settings added to help track behavior of terms (categories, post tags, etc.) for syndicated posts. | |
| 244 | - | |
| 245 | 242 | = 2012.0504 = |
| 246 | 243 | |
| 247 | -* MODULE REORGANIZATION: Should ensure 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. | |
| 244 | +* MODULE REORGANIZATION: Should ensure that all needed submodules will be | |
| 245 | + properly included regardless of whether you are installing from github, | |
| 246 | + from SVN, or from the WordPress plugins page. If you've been getting | |
| 247 | + fatal errors about required modules not being found, this release should | |
| 248 | + hopefully resolve the issue. | |
| 248 | 249 | |
| 249 | 250 | = 2012.0503 = |
| 250 | 251 | |
| 251 | -* BUGFIX: Works properly again with WordPress installations that use a MySQL table name prefix other than the default `wp_` prefix. | |
| 252 | +* BUGFIX: Works properly again with WordPress installations that use a | |
| 253 | + MySQL table name prefix other than the default `wp_` prefix. | |
| 254 | + | |
| 255 | +* BUGFIX: Includes a couple of significant PHP 5.4 compatibility fixes. | |
| 256 | + Now that PHP 5.4 is more widely deployed, Diagnostics will now also | |
| 257 | + show PHP version and some other potentially useful troubleshooting | |
| 258 | + information. | |
| 252 | 259 | |
| 253 | -* 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. | |
| 260 | +* ADMIN UI: Better indicates your options when deleting a syndicated post | |
| 261 | + so as to let you know whether it will be Trashed (and thus not | |
| 262 | + resyndicated) or Erased (and thus potentially resyndicated) | |
| 263 | + | |
| 264 | +* ADMIN UI: Adds an AJAXy Test Expression button to allow live testing of | |
| 265 | + sample results from expressions in Custom Post Settings. | |
| 254 | 266 | |
| 255 | -* 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) | |
| 256 | - | |
| 257 | -* ADMIN UI: Adds an AJAXy Test Expression button to allow live testing of sample results from expressions in Custom Post Settings. | |
| 258 | - | |
| 259 | 267 | = 2012.1218 = |
| 260 | 268 | |
| 261 | -* 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. | |
| 262 | - | |
| 269 | +* WORDPRESS VISUAL EDITOR FIXED. There was an unlisted change in the | |
| 270 | + 2012.1212 release which had the effect of disabling the WordPress Visual | |
| 271 | + Editor for all posts syndicated by FeedWordPress. Many users reported | |
| 272 | + this as a bug. It was actually a deliberate decision -- a crappy way to | |
| 273 | + try to deal with a crappy situation. (Many users had previously reported | |
| 274 | + a "bug" in which all the paragraph or line breaks seemed to be stripped | |
| 275 | + out of their syndicated posts; the issue turned out to be that the | |
| 276 | + Visual Editor was stripping out `<p>` and `<br/>` tags on the assumption | |
| 277 | + that the resulting post would be sent through standard WordPress | |
| 278 | + formatting filters. But under default settings, posts syndicated by FWP | |
| 279 | + deliberately bypass WordPress formatting filters.) In any case, this | |
| 280 | + version adopts a more flexible compromise. *If* FeedWordPress is set up | |
| 281 | + to bypass WordPress formatting filters (as it is by default), *then* | |
| 282 | + the Visual Editor will be disabled for syndicated posts (since using it | |
| 283 | + would produce incorrect results). If on the other hand FeedWordPress is | |
| 284 | + set up to expose syndicated posts to WordPress formatting filters (as it | |
| 285 | + usually is for those using the Visual Editor to manually edit posts), | |
| 286 | + then the Visual Editor tab will be re-enabled for syndicated posts. | |
| 287 | + | |
| 263 | 288 | * BUG FIX: PERMALINKS REWRITTEN FOR CUSTOM POST TYPES AS WELL AS NORMAL |
| 264 | 289 | WORDPRESS POSTS. If you had WordPress set up to syndicate incoming posts |
| 265 | 290 | to a custom post type (under Syndication > Posts & Links), and asked |
| 266 | 291 | FeedWordPress to make "permalinks point to the original site", then |
| @@ -269,9 +294,9 @@ | ||
| 269 | 294 | normal WordPress posts, not for custom post types. In 2012.1218 this bug |
| 270 | 295 | has been fixed: all post types will now have permalinks rewritten unless |
| 271 | 296 | you request for permalinks to point to the local copy on your aggregator |
| 272 | 297 | site. |
| 273 | - | |
| 298 | + | |
| 274 | 299 | * BUG FIX: ELIMINATES "PHP Fatal error: Call to a member function |
| 275 | 300 | setting() on a non-object...." Some changes to the in-memory caching of |
| 276 | 301 | information about feed subscriptions could result in a fatal PHP error |
| 277 | 302 | in cases where you have de-activated one of your subscriptions, but |
| @@ -287,9 +312,9 @@ | ||
| 287 | 312 | * BUG FIX: CATEGORY BOXES IN SYNDICATION > CATEGORIES & TAGS. Some minor |
| 288 | 313 | bugs in the appearance and animation of category checkboxes (for |
| 289 | 314 | example, the checkbox used to select categories for syndicated posts on |
| 290 | 315 | the Syndication > Categories & Tags settings page) have been fixed. |
| 291 | - | |
| 316 | + | |
| 292 | 317 | = 2012.1212 = |
| 293 | 318 | |
| 294 | 319 | * WORDPRESS 3.5 COMPATIBILITY: This release has been tested for compatibility |
| 295 | 320 | with new releases of WordPress, up to version 3.5, and any documented |
| @@ -323,9 +348,9 @@ | ||
| 323 | 348 | interface. This has been fixed: FWP will continue to generate new slugs |
| 324 | 349 | for syndicated posts, but when syndicated posts are updated, they will |
| 325 | 350 | retain the slug that they had at the time of the update; any manual |
| 326 | 351 | changes to the post slug should be preserved. |
| 327 | - | |
| 352 | + | |
| 328 | 353 | * USER-AGENT STRING: FeedWordPress now sends a distinctive User-Agent |
| 329 | 354 | string identifying itself, and noting that it is a feed aggregator. |
| 330 | 355 | |
| 331 | 356 | * MISCELLANEOUS PERFORMANCE IMPROVEMENTS: A number of changes have been |
| @@ -360,9 +385,9 @@ | ||
| 360 | 385 | Username/Password" link underneath the Feed URL. Enter the username and |
| 361 | 386 | password for accessing the feed, then select the authentication method. (If |
| 362 | 387 | you're not sure which method your feed provider uses, try Basic first.) |
| 363 | 388 | Save Changes, and syndicate away. |
| 364 | - | |
| 389 | + | |
| 365 | 390 | NOTE: HTTP Digest support requires the curl module for PHP. If you are not |
| 366 | 391 | sure whether this module has been installed, contact your web hosting |
| 367 | 392 | provider to check. |
| 368 | 393 | |
| @@ -403,9 +428,9 @@ | ||
| 403 | 428 | static pages. What actually happened is that in these rare cases the |
| 404 | 429 | existing static page was mistaken for an older version of the new incoming |
| 405 | 430 | syndicated post, which was then stored as a new revision of the original |
| 406 | 431 | page. The bug that caused these mistaken identities has been fixed. |
| 407 | - | |
| 432 | + | |
| 408 | 433 | * BUGFIX: UNWANTED AUTOMATIC PAGE-LOAD-BASED UPDATES NO LONGER A NUISANCE. |
| 409 | 434 | Some users encountered a bug in which FeedWordPress would adopt an automatic |
| 410 | 435 | page-load-based update method, even if they had requested that it not do |
| 411 | 436 | so, and that it use a manual or cron job update method instead. The bug |
| @@ -422,9 +447,9 @@ | ||
| 422 | 447 | * FEED UPDATE SCHEDULING IMPROVEMENTS: UI. The Syndicated Sources table now |
| 423 | 448 | provides considerably more data to understand update scheduling, when |
| 424 | 449 | specific scheduling decisions are made because of, e.g., requests from the |
| 425 | 450 | feed producer. |
| 426 | - | |
| 451 | + | |
| 427 | 452 | * FEED UPDATE SCHEDULING IMPROVEMENTS: ENFORCEABLE "MINIMUM INTERVAL" SETTING |
| 428 | 453 | TO SPACE OUT UPDATES. Some feeds request specific update schedules, using |
| 429 | 454 | standard elements such as sy:updateFrequency and rss:ttl. Normally, |
| 430 | 455 | FeedWordPress respects any scheduling requests that a feed makes -- if it |
| @@ -441,9 +466,9 @@ | ||
| 441 | 466 | over a longer interval of time. Before, they could not do this: FWP always |
| 442 | 467 | sped up to meet the indicated update schedule. Now, they can do this, by |
| 443 | 468 | using the new "Minimum Interval" setting in Syndication --> Feeds & |
| 444 | 469 | Updates.. |
| 445 | - | |
| 470 | + | |
| 446 | 471 | = 2011.0706 = |
| 447 | 472 | |
| 448 | 473 | * WP 3.2 COMPATIBILITY: ELIMINATES FATAL ERROR "Call to undefined method |
| 449 | 474 | WP_SimplePie_File::WP_SimplePie_File() in |
| @@ -460,9 +485,9 @@ | ||
| 460 | 485 | previously syndicated produced some very slow queries (usually, but not |
| 461 | 486 | always, involving a scan over the MD5(post_guid) column of the table). The |
| 462 | 487 | code that prepares MySQL queries for previously-syndicated checks has been |
| 463 | 488 | revised to eliminate the MD5(post_guid) scan entirely, and to significantly |
| 464 | - improve performance by eliminating other unnecessary clauses. | |
| 489 | + improve performance by eliminating other unnecessary clauses. | |
| 465 | 490 | |
| 466 | 491 | * BUGFIX: NO LONGER DESTROYS STICKY POSTS. Previous versions could destroy |
| 467 | 492 | (or, more precisely, replace the content of) sticky posts due to some |
| 468 | 493 | queries mashed together in unexpected ways by WordPress. Version 2011.0706 |
| @@ -482,9 +507,9 @@ | ||
| 482 | 507 | POSTS. The work-around for handling filtered URIs in guid elements has now |
| 483 | 508 | been extended to handle URIs that were filtered because of leading or |
| 484 | 509 | trailing whitespace, in addition to URIs that were filtered because of |
| 485 | 510 | unapproved schemes. |
| 486 | - | |
| 511 | + | |
| 487 | 512 | * WP 3.1.3 COMPAT / BUGFIX: RELATIVE URLS IN GUIDS NO LONGER PRODUCE DUPLICATE |
| 488 | 513 | POSTS. The work-around for handling filtered URIs in guid elements has now |
| 489 | 514 | been extended to handle URIs that were altered without being filtered out |
| 490 | 515 | entirely (most commonly because a scheme was added to a relative URL). |
| @@ -552,9 +577,9 @@ | ||
| 552 | 577 | |
| 553 | 578 | * AUTHOR LISTS: Lists of authors presented on the Author settings pages |
| 554 | 579 | should now be easier to scan through, with author names arranged in |
| 555 | 580 | alphabetical order. |
| 556 | - | |
| 581 | + | |
| 557 | 582 | * FEED ITEM DATE PARSING: More tweaks to make date-time handling more |
| 558 | 583 | resilient when feeds provide broken or weird values for the timestamps |
| 559 | 584 | on syndicated items. FWP will now attempt to work around unparseable |
| 560 | 585 | timezone values. |
| @@ -562,12 +587,12 @@ | ||
| 562 | 587 | * AUTHOR MATCHING: Now attempts to match author names against the WP login |
| 563 | 588 | name in addition to display_name; when creating user record, also fills |
| 564 | 589 | in some best-guess values for nickname, firstname and lastname. Also |
| 565 | 590 | properly picks up Atom 1.0 author/uri data from feed. |
| 566 | - | |
| 591 | + | |
| 567 | 592 | * COMPATIBILITY: FeedWordPress has been successfully tested for |
| 568 | 593 | compatibility with recent releases of WordPress, up to version 3.1.2. |
| 569 | - | |
| 594 | + | |
| 570 | 595 | = 2011.0211 = |
| 571 | 596 | |
| 572 | 597 | * BUGFIX: DUPLICATE POSTS WHEN GUIDS ARE TOO LONG: When feeds included |
| 573 | 598 | exceptionally long GUIDs, FeedWordPress could occasionally get into |
| @@ -588,9 +613,9 @@ | ||
| 588 | 613 | Feeds & Updates. This is especially helpful for making quick, short-term |
| 589 | 614 | changes to a subscription (for example, to pull in all the previous |
| 590 | 615 | items from a web service, before settling down to pulling in only newly |
| 591 | 616 | updated items). |
| 592 | - | |
| 617 | + | |
| 593 | 618 | * DIAGNOSTICS SYSTEM: Added several new diagnostics which are useful in |
| 594 | 619 | troubleshooting, and established a framework for add-on modules to hook |
| 595 | 620 | in with their own diagnostic messages. |
| 596 | 621 | |
| @@ -596,9 +621,9 @@ | ||
| 596 | 621 | |
| 597 | 622 | * UI: Adjusted some internal coding, which should allow for settings |
| 598 | 623 | pages and add-ons to properly display multiple category pickers on a |
| 599 | 624 | single settings page. |
| 600 | - | |
| 625 | + | |
| 601 | 626 | * PHP4 COMPATIBILITY TWEAKS: This version makes some tweaks to the handling |
| 602 | 627 | of object references which should improve compatibility with older |
| 603 | 628 | versions of PHP. (Although, I should note, web hosts that still force |
| 604 | 629 | you to run under PHP 4 -- in 2011! -- are *bad web hosts*.) |
| @@ -603,9 +628,9 @@ | ||
| 603 | 628 | versions of PHP. (Although, I should note, web hosts that still force |
| 604 | 629 | you to run under PHP 4 -- in 2011! -- are *bad web hosts*.) |
| 605 | 630 | |
| 606 | 631 | * IMPROVED PERFORMANCE: This version eliminates a *major* performance drag |
| 607 | - that shows up on sites with large numbers of users (due to some poor | |
| 632 | + that shows up on sites with large numbers of users (due to some poor | |
| 608 | 633 | decisions about where to place a user query, which caused the user table |
| 609 | 634 | to be scanned frequently when it did not need to be). If you experienced |
| 610 | 635 | serious problems with CPU load or slow database performance under |
| 611 | 636 | 2010.0905, which kicked in immediately when FWP was loaded and tended |
| @@ -628,9 +653,9 @@ | ||
| 628 | 653 | Tags being assigned. This bug has now been fixed: in 2010.0905, Tags and |
| 629 | 654 | Categories should be correctly assigned to all posts, regardless of |
| 630 | 655 | whether they were added from manual updates, cron jobs, or automatic |
| 631 | 656 | updates. |
| 632 | - | |
| 657 | + | |
| 633 | 658 | = 2010.0903 = |
| 634 | 659 | |
| 635 | 660 | * WORDPRESS 3 REQUIRED: Please note that this release of FeedWordPress |
| 636 | 661 | *requires* WordPress 3.0 or later. If you are currently using a 2.x |
| @@ -649,9 +674,9 @@ | ||
| 649 | 674 | problem for myself on my own machines. However, the markup of Syndicated |
| 650 | 675 | Sources has undergone significant changes and corrections since |
| 651 | 676 | 2010.0623, and two independent sources who had been having this problem |
| 652 | 677 | confirm that they no longer encounter it with the updated version. For |
| 653 | - the time being, I am going to declare this bug squashed. | |
| 678 | + the time being, I am going to declare this bug squashed. | |
| 654 | 679 | |
| 655 | 680 | * BUGFIX: MORE PROTECTION AGAINST FATAL ERRORS FROM PLUGGABLE VERSIONS OF |
| 656 | 681 | SimplePie: FeedWordPress now takes some precautions that should help to |
| 657 | 682 | better avoid conflicts for users who have installed pluggable versions |
| @@ -678,9 +703,9 @@ | ||
| 678 | 703 | * ADDING MULTIPLE FEEDS: FeedWordPress now provides a convenient mode for |
| 679 | 704 | adding multiple feeds at once, using either a copy-and-pasted list, or |
| 680 | 705 | else an OPML file. Go to Syndication --> Syndicated Sources and check |
| 681 | 706 | out the two new buttons underneath the New Source input box. When you |
| 682 | - have to add a number of feeds at once, this can save you considerable | |
| 707 | + have to add a number of feeds at once, this can save you considerable | |
| 683 | 708 | time and trouble. |
| 684 | 709 | |
| 685 | 710 | * IMPROVED HANDLING OF AUTHORS WITH DUPLICATE E-MAIL ADDRESS AND AUTHORS |
| 686 | 711 | WITH NAMES WRITTEN IN FOREIGN SCRIPTS: WordPress 3 is increasingly picky |
| @@ -692,9 +717,9 @@ | ||
| 692 | 717 | better, and systematically works to avoid clashes between syndicated |
| 693 | 718 | authors' account names or in their e-mail addresses, which should result |
| 694 | 719 | in significantly better results in mapping author names to WordPress |
| 695 | 720 | user accounts. |
| 696 | - | |
| 721 | + | |
| 697 | 722 | * MAPPING CATEGORIES ON SYNDICATED POSTS TO TAGS NOW BETTER SUPPORTED: |
| 698 | 723 | In previous versions, the only way for the Categories provided by a |
| 699 | 724 | syndicated feed to be mapped into Post Tags was to instruct FWP to |
| 700 | 725 | create new tags, rather than new categories, for unfamiliar categories |
| @@ -704,14 +729,14 @@ | ||
| 704 | 729 | now do this by creating a tag (under Posts ==> Post Tags) before |
| 705 | 730 | importing the post; when the syndicated category matches a pre-existing |
| 706 | 731 | tag, the incoming post will be tagged with that tag, without creating |
| 707 | 732 | a local Post Category. |
| 708 | - | |
| 733 | + | |
| 709 | 734 | * REL-TAG MICROFORMAT SUPPORT FOR INLINE TAGS: Syndicated posts that |
| 710 | 735 | contain inline tags, marked up using the Rel-Tag microformat |
| 711 | 736 | <http://microformats.org/wiki/rel-tag>, are now tagged with the tags |
| 712 | 737 | provided by Rel-Tag format links. |
| 713 | - | |
| 738 | + | |
| 714 | 739 | * MUCH GREATER CONTROL OVER CATEGORY AND TAG MAPPING: This is partly the |
| 715 | 740 | result of building in support for a potentially endless set of custom |
| 716 | 741 | taxonomies (see below), but in general there has been a great deal of |
| 717 | 742 | effort towards giving you more control over how categories and tags |
| @@ -732,9 +757,9 @@ | ||
| 732 | 757 | taxonomies, you may be pleased to find that FeedWordPress now allows you |
| 733 | 758 | to feed incoming posts into any custom feed type that you wish, and to |
| 734 | 759 | map categories and tags from the feed to custom taxonomies as well as |
| 735 | 760 | to the standard Category and Tag taxonomies. |
| 736 | - | |
| 761 | + | |
| 737 | 762 | * STORING NAMESPACED CUSTOM FEED ELEMENTS IN POST CUSTOM FIELDS: If you |
| 738 | 763 | would like to use FeedWordPress's support for storing custom meta-data |
| 739 | 764 | from feed elements in the custom fields for a post (for example, to |
| 740 | 765 | store geolocation data or iTunes media meta-data), you'll find that it's |
| @@ -761,9 +786,9 @@ | ||
| 761 | 786 | it means that much more power and ease for folks who are customizing |
| 762 | 787 | FeedWordPress through PHP filters or add-on modules. Fuller |
| 763 | 788 | documentation will be put up at the Wiki at feedwordpress.radgeek.org |
| 764 | 789 | soon. |
| 765 | - | |
| 790 | + | |
| 766 | 791 | = 2010.0623 = |
| 767 | 792 | |
| 768 | 793 | * WORDPRESS 3.0 COMPATIBILITY / AUTHOR MAPPING INTERFACE ISSUES: I |
| 769 | 794 | resolved a couple of outstanding issues with the author mapping |
| @@ -770,9 +795,9 @@ | ||
| 770 | 795 | interface (Syndication --> Authors), which were preventing new users |
| 771 | 796 | from being created correctly and author mapping rules from being set up |
| 772 | 797 | correctly. These partly had to do with new restrictions on user account |
| 773 | 798 | creation introduced in WordPress 3.0; anyway, they should now be fixed. |
| 774 | - | |
| 799 | + | |
| 775 | 800 | * MORE EFFICIENT SYNDICATED URL LOOKUPS: Several users noticed that the |
| 776 | 801 | bug fix introduced in 2010.0528 for compatibility with post-listing |
| 777 | 802 | plugins caused a lot more queries to the database in order to look up |
| 778 | 803 | numerical post IDs from the URL provided to the filter. This shouldn't |
| @@ -796,14 +821,14 @@ | ||
| 796 | 821 | unsubscribed feed can now easily be viewed in a special "Inactive" |
| 797 | 822 | section of the Syndicated Sources page. (As a side benefit, if you've |
| 798 | 823 | accidentally, or only temporarily, turned off the subscription to a |
| 799 | 824 | feed, it is now much easier to restore the feed to being active, or to |
| 800 | - delete it permanently, if you prefer. | |
| 825 | + delete it permanently, if you prefer. | |
| 801 | 826 | |
| 802 | 827 | * UI: FEED FINDER / SWITCH FEED INTERFACE IMPROVEMENTS: changes to styling |
| 803 | 828 | and options for the feed finder / switch feed, which should now make it |
| 804 | 829 | easier, in some cases, to find alternative feeds, and make interface |
| 805 | - options more clearly visible. | |
| 830 | + options more clearly visible. | |
| 806 | 831 | |
| 807 | 832 | * FILTERS: `syndicated_item_published` and `syndicated_item_updated` NOW |
| 808 | 833 | PROPERLY AFFECT THE DATING OF POSTS. These filters used to affect some |
| 809 | 834 | date-related settings, but not others -- and, most importantly, not the |
| @@ -863,10 +888,10 @@ | ||
| 863 | 888 | use the `syndicated_item_published` and `syndicated_item_updated` filter |
| 864 | 889 | hooks to write filters or add-ons which directly change the post date |
| 865 | 890 | and most-recently-updated timestamps on incoming syndicated posts. Props |
| 866 | 891 | to niska for pointing out where the filters needed to be applied in |
| 867 | - order to change WordPress's internal timestamps for incoming posts. | |
| 868 | - | |
| 892 | + order to change WordPress's internal timestamps for incoming posts. | |
| 893 | + | |
| 869 | 894 | = 2010.0531 = |
| 870 | 895 | |
| 871 | 896 | * PERMALINK / CUSTOM FIELDS PROBLEM RESOLVED: An issue in 2010.0528 caused |
| 872 | 897 | some posts to be imported without the proper syndication-related |
| @@ -907,9 +932,9 @@ | ||
| 907 | 932 | advantage of the SimplePie object representations of items, feeds, etc., |
| 908 | 933 | rather than the MagpieRSS arrays, but the MagpieRSS arrays will still |
| 909 | 934 | be available and older filters should continue to work as they have in |
| 910 | 935 | the past. |
| 911 | - | |
| 936 | + | |
| 912 | 937 | * COMPATIBILITY WITH WORDPRESS 2.9.x and 3.0: This release has been tested |
| 913 | 938 | for the existing WordPress 2.9.x branch and with the upcoming release of |
| 914 | 939 | WordPress 3.0. Changes in the user interface JavaScript between WordPress |
| 915 | 940 | 2.8.x and WordPress 2.9 caused the tag box interface element to break in |
| @@ -935,9 +960,9 @@ | ||
| 935 | 960 | been eliminated entirely for pages that cover each aspect of handling |
| 936 | 961 | a feed: Feeds & Updates, Posts & Links, Authors, Categories & Tags, |
| 937 | 962 | and Back End handling of the database and diagnostic information. |
| 938 | 963 | Extensive new interface hooks allow add-on modules to significantly |
| 939 | - change or extend the FeedWordPress admin interface and workflow. | |
| 964 | + change or extend the FeedWordPress admin interface and workflow. | |
| 940 | 965 | |
| 941 | 966 | * STORING INFORMATION FROM THE FEED IN CUSTOM FIELDS: Many users |
| 942 | 967 | have written to request the ability to store information from elements |
| 943 | 968 | in the feed in a custom field on each post. (So that, for example, if |
| @@ -992,9 +1017,9 @@ | ||
| 992 | 1017 | correctly parse a date, to fall back to a more intelligent default. This |
| 993 | 1018 | should hopefully avoid most or all error conditions that have resulted |
| 994 | 1019 | in articles being erroneously dated to the dawn of the Unix epoch |
| 995 | 1020 | (31 December 1969 or 1 January 1970). |
| 996 | - | |
| 1021 | + | |
| 997 | 1022 | * FULL-TEXT "EXCERPTS" NOW PROPERLY SHORTENED. Based on a straightforward |
| 998 | 1023 | reading of the existing RSS specs, it's reasonable for the |
| 999 | 1024 | rss:description element to be read as a plaintext summary or excerpt for |
| 1000 | 1025 | the item containing the description -- with the full text of the item, |
| @@ -1028,9 +1053,9 @@ | ||
| 1028 | 1053 | documentation wiki at |
| 1029 | 1054 | <http://feedwordpress.radgeek.com/wiki/add-ons-and-filters> |
| 1030 | 1055 | |
| 1031 | 1056 | * FILTER API: A number of new utility methods have been added to the |
| 1032 | - SyndicatedPost class to make it easier for filters and add-ons to | |
| 1057 | + SyndicatedPost class to make it easier for filters and add-ons to | |
| 1033 | 1058 | |
| 1034 | 1059 | * FILTER API: Globals $fwp_channel and $fwp_feedmeta DEPRECATED. These |
| 1035 | 1060 | global variables, originally introduced to allow filters access to |
| 1036 | 1061 | information about the source feed in `syndicated_item` filters (which |
| @@ -1102,14 +1127,14 @@ | ||
| 1102 | 1127 | encountered an error in which any time they attempted to add a new feed |
| 1103 | 1128 | through the FeedFinder interface, FeedWordPress would fail and display |
| 1104 | 1129 | an HTTP request failure diagnostic message. The subtle bug has been |
| 1105 | 1130 | fixed, and with it, most of these errors should now be eliminated. |
| 1106 | - | |
| 1131 | + | |
| 1107 | 1132 | Be sure to upgrade your MagpieRSS to the most recent MagpieRSS version |
| 1108 | 1133 | after you have insalled FeedWordPress 2009.0618, or this bug fix will |
| 1109 | 1134 | not take effect. |
| 1110 | 1135 | |
| 1111 | -= 2009.0613 = | |
| 1136 | += 2009.0613 = | |
| 1112 | 1137 | |
| 1113 | 1138 | * INTERFACE/BUGFIX: WORDPRESS 2.8 CATEGORY BOX FIX. Thanks to a subtle |
| 1114 | 1139 | change in class names between the WordPress 2.7 and 2.8 stylesheets, |
| 1115 | 1140 | category boxes in the FeedWordPress settings interface tended to overflow |
| @@ -1114,9 +1139,9 @@ | ||
| 1114 | 1139 | change in class names between the WordPress 2.7 and 2.8 stylesheets, |
| 1115 | 1140 | category boxes in the FeedWordPress settings interface tended to overflow |
| 1116 | 1141 | and have a lot of messy-looking overlapping text under WordPress 2.8. |
| 1117 | 1142 | This has now been fixed. |
| 1118 | - | |
| 1143 | + | |
| 1119 | 1144 | * FeedFinder FAILURE DIAGNOSTICS: When FWP's FeedFinder fails to find any |
| 1120 | 1145 | feeds at a given URL (for example, when you are trying to add a |
| 1121 | 1146 | subscription through the administrative interface and you run into an |
| 1122 | 1147 | error message), FeedWordPress now provides more diagnostic information |
| @@ -1144,9 +1169,9 @@ | ||
| 1144 | 1169 | Corresponding to these new subpages, the old Syndication Settings and |
| 1145 | 1170 | Feed Settings subpages have been cleaned up and simplified, and now only |
| 1146 | 1171 | link to the appropriate subpages for options that can be set in the |
| 1147 | 1172 | Posts, Authors, or Categories & Tags subpages. |
| 1148 | - | |
| 1173 | + | |
| 1149 | 1174 | * FEATURE: ADD CUSTOM SETTINGS TO EACH SYNDICATED POST: FeedWordPress has |
| 1150 | 1175 | long had an interface for creating custom settings for each syndicated |
| 1151 | 1176 | *feed* which could be retrieved in templates using the `get_feed_meta()` |
| 1152 | 1177 | template function. But it had no feature for adding custom fields to |
| @@ -1334,9 +1359,9 @@ | ||
| 1334 | 1359 | Please note that if you have already encountered this issue on your |
| 1335 | 1360 | blog, upgrading FeedWordPress will prevent it from re-occurring in the |
| 1336 | 1361 | future, but you still need to do two other things to fix the existing |
| 1337 | 1362 | problem on your blog. |
| 1338 | - | |
| 1363 | + | |
| 1339 | 1364 | First, for each feed where posts have been mis-attributed, you need to |
| 1340 | 1365 | change the existing author mapping rules to re-map a a syndicated |
| 1341 | 1366 | author's name to the proper target account. Go to **Syndication --> |
| 1342 | 1367 | Authors**, select the feed you want to change from the drop-down list, |
| @@ -1342,9 +1367,9 @@ | ||
| 1342 | 1367 | Authors**, select the feed you want to change from the drop-down list, |
| 1343 | 1368 | and then change the settings under the "Syndicated Authors" section. |
| 1344 | 1369 | (You will probably need to select "will be assigned to a new user..." to |
| 1345 | 1370 | create a new user account with the appropriate name.) |
| 1346 | - | |
| 1371 | + | |
| 1347 | 1372 | Second, for each feed where posts have been mis-attributed, you need to |
| 1348 | 1373 | re-assign already-syndicated posts that were mis-attributed to the |
| 1349 | 1374 | correct author. You can do that from **Syndication --> Authors** by |
| 1350 | 1375 | using the author re-assignment feature, described below. |
| @@ -1364,9 +1389,9 @@ | ||
| 1364 | 1389 | your templates and feeds: you can have FeedWordPress report that the |
| 1365 | 1390 | source of a post is the aggregator feed itself, or you can have it |
| 1366 | 1391 | report that the source of a post is the original source that the |
| 1367 | 1392 | aggregator originally syndicated the post from. |
| 1368 | - | |
| 1393 | + | |
| 1369 | 1394 | By default, FeedWordPress will report the aggregator, not the original |
| 1370 | 1395 | source, as the source of a syndicated item. |
| 1371 | 1396 | |
| 1372 | 1397 | * LOAD BALANCING AND TIME LIMITING FEATURES FOR UPDATES: Some users have |
| @@ -1380,9 +1405,9 @@ | ||
| 1380 | 1405 | time limits are usually in the vicinity of 30 seconds, so an update |
| 1381 | 1406 | time limit of 25 seconds or so should provide plenty of time for updates |
| 1382 | 1407 | while allowing a cushion of time for other, non-update-related functions |
| 1383 | 1408 | to do their work.) |
| 1384 | - | |
| 1409 | + | |
| 1385 | 1410 | If feed updates are interrupted by the time limit, FeedWordPress uses |
| 1386 | 1411 | some simple load balancing features to make sure that updates to other |
| 1387 | 1412 | feeds will not be blocked by the time-hogging feed, and will also make |
| 1388 | 1413 | sure that when the interrupted update is resumed, FeedWordPress will |
| @@ -1447,9 +1472,9 @@ | ||
| 1447 | 1472 | familiar category; (3) to create a new category with that name, or, |
| 1448 | 1473 | now, you can also have FeedWordPress (4) create a new *tag* with that |
| 1449 | 1474 | name. This option can be set site-wide under Syndication --> Options, |
| 1450 | 1475 | or it can be set on a feed-by-feed basis in a feed's Edit screen. |
| 1451 | - | |
| 1476 | + | |
| 1452 | 1477 | In addition, you can now set particular tags to apply to all incoming |
| 1453 | 1478 | syndicated posts, under Syndication --> Options, or you can set tags |
| 1454 | 1479 | to apply to all incoming syndicated posts from a particular feed in that |
| 1455 | 1480 | feed's Edit screen. |
| @@ -1467,9 +1492,9 @@ | ||
| 1467 | 1492 | setting from "Protect" to "Expose." |
| 1468 | 1493 | |
| 1469 | 1494 | * `<atom:source>` ELEMENTS NOW INCLUDED IN ATOM FEED: Atom 1.0 provides |
| 1470 | 1495 | a standard method for aggregators to indicate information about the original source of |
| 1471 | - a syndicated post, using the `<atom:source>` element. FeedWordPress now | |
| 1496 | + a syndicated post, using the `<atom:source>` element. FeedWordPress now | |
| 1472 | 1497 | introduces standard `<atom:source>` elements including the title, homepage, and |
| 1473 | 1498 | feed URI of the source from which a syndicated post was syndicated. Cf. |
| 1474 | 1499 | <http://www.atomenabled.org/developers/syndication/atom-format-spec.php#element.source> |
| 1475 | 1500 | |
| @@ -1511,9 +1536,9 @@ | ||
| 1511 | 1536 | categories by separating them at whitespace.) Unfortunately, del.icio.us |
| 1512 | 1537 | recently broke the existing behavior by changing host names for their |
| 1513 | 1538 | feeds from del.icio.us to feeds.delicious.com. Version 0.993 accounts |
| 1514 | 1539 | for the new host name and un-breaks the tag splitting. |
| 1515 | - | |
| 1540 | + | |
| 1516 | 1541 | = 0.992 = |
| 1517 | 1542 | |
| 1518 | 1543 | * AUTHOR RE-MAPPING: FeedWordPress now offers considerable control over |
| 1519 | 1544 | how author names on a feed are translated into usernames within the |
| @@ -1529,9 +1554,9 @@ | ||
| 1529 | 1554 | "Administrator." These settings also allow administrators to filter out |
| 1530 | 1555 | posts by particular users, and to control what will happen when |
| 1531 | 1556 | FeedWordPress encounters a post by an unrecognized user on that |
| 1532 | 1557 | particular feed. |
| 1533 | - | |
| 1558 | + | |
| 1534 | 1559 | * BUG RELATED TO URIS CONTAINING AMPERSAND CHARACTERS FIXED: A bug in |
| 1535 | 1560 | WordPress 2.x's handling of URIs in Blogroll links created problems for |
| 1536 | 1561 | updating any feeds whose URIs included an ampersand character, such as |
| 1537 | 1562 | Google News RSS feeds and other feeds that have multiple parameters |
| @@ -1676,9 +1701,9 @@ | ||
| 1676 | 1701 | which, among other things, allows you to access information about the |
| 1677 | 1702 | feed from which an item is syndicated using the $post->feed and the |
| 1678 | 1703 | $post->feedmeta elements (where $post is the name of the second |
| 1679 | 1704 | parameter). |
| 1680 | - | |
| 1705 | + | |
| 1681 | 1706 | NOTE THAT THE OLD GLOBAL VARIABLES ARE STILL AVAILABLE, for the time |
| 1682 | 1707 | being at least, so existing filters will not break with the upgrade. |
| 1683 | 1708 | They should be considered deprecated, however, and may be eliminated in |
| 1684 | 1709 | the future. |
| @@ -1847,9 +1872,9 @@ | ||
| 1847 | 1872 | category to all syndicated posts from a particular feed, it meant that |
| 1848 | 1873 | they'd have at least one familiar category (the category or categories |
| 1849 | 1874 | you were applying), and that would get all posts past the filter no |
| 1850 | 1875 | matter what categories they were originally from. |
| 1851 | - | |
| 1876 | + | |
| 1852 | 1877 | Well, no longer. You can still apply categories to all syndicated posts |
| 1853 | 1878 | (using either Syndication --> Options, or the feed-level settings under |
| 1854 | 1879 | Links --> Syndicated). But these categories are not applied to the post |
| 1855 | 1880 | until *after* it has already passed by the "familiar categories" filter. |
| @@ -1876,11 +1901,11 @@ | ||
| 1876 | 1901 | get_feed_meta() function or the $fwp_feedmeta global, note that the |
| 1877 | 1902 | data formerly located under the `uri` and `name` fields is now located |
| 1878 | 1903 | under the `link/uri` field and the `link/name` field, respectively. Note |
| 1879 | 1904 | also that you can access the link ID number for any given feed under the |
| 1880 | - global $fwp_feedmeta['link/id'] (in plugins) or | |
| 1905 | + global $fwp_feedmeta['link/id'] (in plugins) or | |
| 1881 | 1906 | get_feed_meta('link/id') (in a template in post contexts). |
| 1882 | - | |
| 1907 | + | |
| 1883 | 1908 | * FEATURE: the settings for individual feeds can now be edited using a |
| 1884 | 1909 | humane interface (where formerly you had to tweak key-value pairs in the |
| 1885 | 1910 | Link Notes section). To edit settings for a feed, pick the feed that you |
| 1886 | 1911 | want under Links --> Syndicated and click the Edit link. |
| @@ -1924,9 +1949,9 @@ | ||
| 1924 | 1949 | certain period of time has passed. The amount of time is normally set |
| 1925 | 1950 | randomly for each feed, in a period between 30 minutes and 2 hours (so |
| 1926 | 1951 | as to stagger updates over time rather than polling all of the feeds at once. However, the length of time between updates can also be set |
| 1927 | 1952 | directly by the feed, which brings us to ... |
| 1928 | - | |
| 1953 | + | |
| 1929 | 1954 | * FEATURE: FeedWordPress now respects the settings in the `ttl` and |
| 1930 | 1955 | Syndication Module RSS elements. Feeds with these elements set will not |
| 1931 | 1956 | be polled any more frequently than they indicate with these feeds unless |
| 1932 | 1957 | the user manually forces FeedWordPress to poll the feed (see Links --> |
| @@ -1950,11 +1975,11 @@ | ||
| 1950 | 1975 | of a contributor's website manually (that is, prevent it from being |
| 1951 | 1976 | automatically updated from the feed channel link on each update). To |
| 1952 | 1977 | set the URI manually, put a line like this in the Link Notes section |
| 1953 | 1978 | of a feed: |
| 1954 | - | |
| 1979 | + | |
| 1955 | 1980 | hardcode url: yes |
| 1956 | - | |
| 1981 | + | |
| 1957 | 1982 | You can also instruct FeedWordPress to use hardcoded URIs by default |
| 1958 | 1983 | on all feeds using Options --> Syndication |
| 1959 | 1984 | |
| 1960 | 1985 | * FEATURE: by default, when FeedWordPress finds new syndicated posts, |
| @@ -1966,44 +1991,123 @@ | ||
| 1966 | 1991 | |
| 1967 | 1992 | |
| 1968 | 1993 | = From 0.91 to 0.95 = |
| 1969 | 1994 | |
| 1970 | -* BUG FIX: Fixed an obscure bug in the handling of categories: categories with trailing whitespace could cause categories with duplicate names to be created. This no longer happens. While I was at it I tightened up the operation of FeedWordPress::lookup_categories() a bit in general. | |
| 1995 | +* BUG FIX: Fixed an obscure bug in the handling of categories: | |
| 1996 | + categories with trailing whitespace could cause categories with | |
| 1997 | + duplicate names to be created. This no longer happens. While I was | |
| 1998 | + at it I tightened up the operation of | |
| 1999 | + FeedWordPress::lookup_categories() a bit in general. | |
| 1971 | 2000 | |
| 1972 | -* FEATURE DEPRECATED: the feed setting `hardcode categories` is now deprecated in favor of `unknown categories` (see below), which allows you to strip off any syndication categories not already in your database using `unknown categories: default` or `unknown categories: filter`. If you have `hardcode categories: yes` set on a feed, this will be treated as `unknown categories: default` (i.e., no new categories will be added, but if a post doesn't match any of the categories it will be added in the default category--usually "Uncategorized" or "General"). | |
| 2001 | +* FEATURE DEPRECATED: the feed setting `hardcode categories` is now | |
| 2002 | + deprecated in favor of `unknown categories` (see below), which | |
| 2003 | + allows you to strip off any syndication categories not already in | |
| 2004 | + your database using `unknown categories: default` or `unknown | |
| 2005 | + categories: filter`. If you have `hardcode categories: yes` set on a | |
| 2006 | + feed, this will be treated as `unknown categories: default` (i.e., | |
| 2007 | + no new categories will be added, but if a post doesn't match any of | |
| 2008 | + the categories it will be added in the default category--usually | |
| 2009 | + "Uncategorized" or "General"). | |
| 1973 | 2010 | |
| 1974 | -* FEATURE: You can now set global defaults as to whether or not FeedWordPress will update the Link Name and Link Description settings for feeds automatically from the feed title and feed tagline. (By default, it does, as it has in past versions.) Whether this behavior is turned on or off, you can still override the default behavior using feed settings of `hardcode name: yes`, `hardcode name: no`, `hardcode description: yes`, or `hardcode description: no`. | |
| 2011 | +* FEATURE: You can now set global defaults as to whether or not | |
| 2012 | + FeedWordPress will update the Link Name and Link Description | |
| 2013 | + settings for feeds automatically from the feed title and feed | |
| 2014 | + tagline. (By default, it does, as it has in past versions.) Whether | |
| 2015 | + this behavior is turned on or off, you can still override the | |
| 2016 | + default behavior using feed settings of `hardcode name: yes`, | |
| 2017 | + `hardcode name: no`, `hardcode description: yes`, or `hardcode | |
| 2018 | + description: no`. | |
| 1975 | 2019 | |
| 1976 | -* FEATURE: Users can now provide one or several "aliases" for an author, just as they can for a category. For example, to make FeedWordPress treat posts by "Joseph Cardinal Ratzinger" and "Pope Benedict XVI" as by the same author, edit the user profile for Pope Benedict XVI and add a line like this to the "User profile" field: | |
| 1977 | - | |
| 2020 | +* FEATURE: Users can now provide one or several "aliases" for an | |
| 2021 | + author, just as they can for a category. For example, to make | |
| 2022 | + FeedWordPress treat posts by "Joseph Cardinal Ratzinger" and "Pope | |
| 2023 | + Benedict XVI" as by the same author, edit the user profile for Pope | |
| 2024 | + Benedict XVI and add a line like this to the "User profile" field: | |
| 2025 | + | |
| 1978 | 2026 | a.k.a.: Joseph Cardinal Ratzinger |
| 1979 | - | |
| 1980 | - You can add several aliases, each on a line by itself. You can also add any other text you like to the Profile without interfering with the aliases. | |
| 1981 | - | |
| 1982 | -* FEATURE: Users can now choose how to handle syndicated posts that are in unfamiliar categories or by unfamiliar authors (i.e., categories or authors whose names are not yet in the WordPress database). By default, FeedWordPress will (as before) create a new category (or new author) and use it for the current post and any future posts. This behavior can be changed, either for all feeds or for one or another particular feed. | |
| 1983 | - | |
| 1984 | - There are now three different options for an unfamiliar author: (1) FeedWordPress can create a new author account and attribute the syndicated post to the new account; (2) FeedWordPress can attribute the post to an author if the author's name is familiar, and to a default author (currently, this means the Site Administrator account) if it is not; (3) FeedWordPress can drop posts by unfamiliar authors and syndicate only posts by authors who are already in the database. | |
| 1985 | - | |
| 1986 | - There are, similarly, two different options for an unfamiliar category: (1) FeedWordPress can create new categories and place the syndicated post in them; (2) FeedWordPress can drop the unfamiliar categories and place syndicated posts only in categories that it is already familiar with. In addition, FeedWordPress 0.95 lets you choose whether posts that are in *no* familiar categories should be syndicated (and placed in the default category for the blog) or simply dropped. | |
| 1987 | - | |
| 1988 | - You can set the default behavior for both authors and categories using the settings in Options --> Syndication. You can also set different behavior for specific feeds by adding the `unfamiliar author` and / or `unfamiliar categories` settings to the Link Notes section of a feed: | |
| 1989 | - | |
| 2027 | + | |
| 2028 | + You can add several aliases, each on a line by itself. You can also | |
| 2029 | + add any other text you like to the Profile without interfering with | |
| 2030 | + the aliases. | |
| 2031 | + | |
| 2032 | +* FEATURE: Users can now choose how to handle syndicated posts that | |
| 2033 | + are in unfamiliar categories or by unfamiliar authors (i.e., | |
| 2034 | + categories or authors whose names are not yet in the WordPress | |
| 2035 | + database). By default, FeedWordPress will (as before) create a new | |
| 2036 | + category (or new author) and use it for the current post and any | |
| 2037 | + future posts. This behavior can be changed, either for all feeds or | |
| 2038 | + for one or another particular feed. | |
| 2039 | + | |
| 2040 | + There are now three different options for an unfamiliar author: (1) | |
| 2041 | + FeedWordPress can create a new author account and attribute the | |
| 2042 | + syndicated post to the new account; (2) FeedWordPress can attribute | |
| 2043 | + the post to an author if the author's name is familiar, and to a | |
| 2044 | + default author (currently, this means the Site Administrator | |
| 2045 | + account) if it is not; (3) FeedWordPress can drop posts by | |
| 2046 | + unfamiliar authors and syndicate only posts by authors who are | |
| 2047 | + already in the database. | |
| 2048 | + | |
| 2049 | + There are, similarly, two different options for an unfamiliar | |
| 2050 | + category: (1) FeedWordPress can create new categories and place the | |
| 2051 | + syndicated post in them; (2) FeedWordPress can drop the unfamiliar | |
| 2052 | + categories and place syndicated posts only in categories that it is | |
| 2053 | + already familiar with. In addition, FeedWordPress 0.95 lets you | |
| 2054 | + choose whether posts that are in *no* familiar categories should be | |
| 2055 | + syndicated (and placed in the default category for the blog) or | |
| 2056 | + simply dropped. | |
| 2057 | + | |
| 2058 | + You can set the default behavior for both authors and categories | |
| 2059 | + using the settings in Options --> Syndication. You can also set | |
| 2060 | + different behavior for specific feeds by adding the `unfamiliar | |
| 2061 | + author` and / or `unfamiliar categories` settings to the Link Notes | |
| 2062 | + section of a feed: | |
| 2063 | + | |
| 1990 | 2064 | unfamiliar author: (create|default|filter) |
| 1991 | 2065 | unfamiliar categories: (create|default|filter) |
| 1992 | - | |
| 1993 | - A setting of `unfamiliar author: create` will make FeedWordPress create new authors to match unfamiliar author names *for this feed alone*. A setting of `unfamiliar author: default` will make it assign posts from unfamiliar authors to the default user account. A setting of `unfamiliar author: filter` will cause all posts (from this feed alone) to be dropped unless they are by an author already listed in the database. Similiarly, `unfamiliar categories: create` will make FeedWordPress create new categories to match unfamiliar category names *for this feed alone*; `unfamiliar categories: default` will cause it to drop any unfamiliar category names; and `unfamiliar categories: filter` will cause it to *both* drop any unfamiliar category names *and* to only syndicate posts that are placed in one or more familiar categories. | |
| 1994 | - | |
| 1995 | - These two new features allow users to do some coarse-grained filtering without having to write a PHP filter. Specifically, they offer an easy way for you to filter feeds by category or by author. Suppose, for example, that you only wanted to syndicate posts that your contributors place in the "Llamas" category. You could do so by setting up your installation of WordPress so that the only category in the database is "Llamas," and then use Options --> Syndication to set "Unfamiliar categories" to "don't create new categories and don't syndicate posts unless they match at least one familiar category". Now, when you update, only posts in the "Llamas" category will be syndicated by FeedWordPress. | |
| 1996 | - | |
| 1997 | - Similarly, if you wanted to filter one particular feed so that only posts by (for example) the author "Earl J. Llama" were syndicated to your site, you could do so by creating a user account for Earl J. Llama, then adding the following line to the settings for the feed in Link Notes: | |
| 1998 | - | |
| 2066 | + | |
| 2067 | + A setting of `unfamiliar author: create` will make FeedWordPress | |
| 2068 | + create new authors to match unfamiliar author names *for this feed | |
| 2069 | + alone*. A setting of `unfamiliar author: default` will make it | |
| 2070 | + assign posts from unfamiliar authors to the default user account. A | |
| 2071 | + setting of `unfamiliar author: filter` will cause all posts (from | |
| 2072 | + this feed alone) to be dropped unless they are by an author already | |
| 2073 | + listed in the database. Similiarly, `unfamiliar categories: create` | |
| 2074 | + will make FeedWordPress create new categories to match unfamiliar | |
| 2075 | + category names *for this feed alone*; `unfamiliar categories: | |
| 2076 | + default` will cause it to drop any unfamiliar category names; and | |
| 2077 | + `unfamiliar categories: filter` will cause it to *both* drop any | |
| 2078 | + unfamiliar category names *and* to only syndicate posts that are | |
| 2079 | + placed in one or more familiar categories. | |
| 2080 | + | |
| 2081 | + These two new features allow users to do some coarse-grained | |
| 2082 | + filtering without having to write a PHP filter. Specifically, they | |
| 2083 | + offer an easy way for you to filter feeds by category or by author. | |
| 2084 | + Suppose, for example, that you only wanted to syndicate posts that | |
| 2085 | + your contributors place in the "Llamas" category. You could do so by | |
| 2086 | + setting up your installation of WordPress so that the only category | |
| 2087 | + in the database is "Llamas," and then use Options --> Syndication to | |
| 2088 | + set "Unfamiliar categories" to "don't create new categories and | |
| 2089 | + don't syndicate posts unless they match at least one familiar | |
| 2090 | + category". Now, when you update, only posts in the "Llamas" category | |
| 2091 | + will be syndicated by FeedWordPress. | |
| 2092 | + | |
| 2093 | + Similarly, if you wanted to filter one particular feed so that only | |
| 2094 | + posts by (for example) the author "Earl J. Llama" were syndicated to | |
| 2095 | + your site, you could do so by creating a user account for Earl J. | |
| 2096 | + Llama, then adding the following line to the settings for the feed | |
| 2097 | + in Link Notes: | |
| 2098 | + | |
| 1999 | 2099 | unfamiliar author: filter |
| 2000 | - | |
| 2001 | - This will cause any posts from this feed that are not authored by Earl J. Llama to be discarded, and only the posts by Earl J. Llama will be syndicated. (If the setting is used on one specific feed, it will not affect how posts from other feeds are syndicated.) | |
| 2002 | - | |
| 2100 | + | |
| 2101 | + This will cause any posts from this feed that are not authored by | |
| 2102 | + Earl J. Llama to be discarded, and only the posts by Earl J. Llama | |
| 2103 | + will be syndicated. (If the setting is used on one specific feed, it | |
| 2104 | + will not affect how posts from other feeds are syndicated.) | |
| 2105 | + | |
| 2003 | 2106 | == License == |
| 2004 | 2107 | |
| 2005 | -The FeedWordPress plugin is copyright © 2005-2021 by Charles Johnson. It uses code derived or translated from: | |
| 2108 | +The FeedWordPress plugin is copyright © 2005-2010 by Charles Johnson. It uses | |
| 2109 | +code derived or translated from: | |
| 2006 | 2110 | |
| 2007 | 2111 | - [wp-rss-aggregate.php][] by [Kellan Elliot-McCrea](kellan@protest.net) |
| 2008 | 2112 | - [SimplePie][] feed parser by Ryan Parman, Geoffrey Sneddon, Ryan McCue, et al. |
| 2009 | 2113 | - [MagpieRSS][] feed parser by [Kellan Elliot-McCrea](kellan@protest.net) |
| @@ -2011,11 +2115,16 @@ | ||
| 2011 | 2115 | - [WordPress Blog Tool and Publishing Platform](http://wordpress.org/) |
| 2012 | 2116 | |
| 2013 | 2117 | according to the terms of the [GNU General Public License][]. |
| 2014 | 2118 | |
| 2015 | -This program is free software; you can redistribute it and/or modify it under the terms of the [GNU General Public License][] as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. | |
| 2119 | +This program is free software; you can redistribute it and/or modify it under | |
| 2120 | +the terms of the [GNU General Public License][] as published by the Free | |
| 2121 | +Software Foundation; either version 2 of the License, or (at your option) any | |
| 2122 | +later version. | |
| 2016 | 2123 | |
| 2017 | -This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. | |
| 2124 | +This program is distributed in the hope that it will be useful, but WITHOUT ANY | |
| 2125 | +WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A | |
| 2126 | +PARTICULAR PURPOSE. See the GNU General Public License for more details. | |
| 2018 | 2127 | |
| 2019 | 2128 | [wp-rss-aggregate.php]: http://laughingmeme.org/archives/002203.html |
| 2020 | 2129 | [SimplePie]: http://www.simplepie.org/ |
| 2021 | 2130 | [MagpieRSS]: http://magpierss.sourceforge.net/ |
