| @@ -1,260 +1,7 @@ | ||
| 1 | 1 | FeedWordPress Change Log |
| 2 | 2 | ======================== |
| 3 | 3 | |
| 4 | -Changes from 0.991 to 0.992 | |
| 5 | -* AUTHOR RE-MAPPING: FeedWordPress now offers considerable control over | |
| 6 | - how author names on a feed are translated into usernames within the | |
| 7 | - WordPress database. When a post by an unrecognized author comes in, | |
| 8 | - Administrators can now specify any username as the default username to | |
| 9 | - assign the post to by setting the option in Syndication --> Options | |
| 10 | - (formerly FeedWordPress only allowed you to assign such posts to user | |
| 11 | - #1, the site administrator). Administrators can also create re-mapping | |
| 12 | - rules for particular feeds (under Syndication --> Syndicated Sites --> | |
| 13 | - Edit), so that (for example) any posts attributed to "Administrator" | |
| 14 | - on the feed <http://praxeology.net/blog/feed/> will be assigned to | |
| 15 | - a user named "Roderick T. Long," rather than a user named | |
| 16 | - "Administrator." These settings also allow administrators to filter out | |
| 17 | - posts by particular users, and to control what will happen when | |
| 18 | - FeedWordPress encounters a post by an unrecognized user on that | |
| 19 | - particular feed. | |
| 20 | - | |
| 21 | -* BUG RELATED TO URIS CONTAINING AMPERSAND CHARACTERS FIXED: A bug in | |
| 22 | - WordPress 2.x's handling of URIs in Blogroll links created problems for | |
| 23 | - updating any feeds whose URIs included an ampersand character, such as | |
| 24 | - Google News RSS feeds and other feeds that have multiple parameters | |
| 25 | - passed through HTTP GET. If you experienced this bug, the most likely | |
| 26 | - effect was that FeedWordPress simply would not import new posts from a | |
| 27 | - feed when instructred to do so, returning a "0 new posts" response. In | |
| 28 | - other cases, it might lead to unpredictable results from feed updates, | |
| 29 | - such as importing posts which were not contained in the feed being | |
| 30 | - syndicated, but which did appear elsewhere on the same website. This bug | |
| 31 | - has, hopefully, been resolved, by correcting for the bug in WordPress. | |
| 32 | - | |
| 33 | -Changes from 0.99 to 0.991 | |
| 34 | -* WORDPRESS MU COMPATABILITY: FeedWordPress should now be compatible with | |
| 35 | - recent releases of WordPress MU. Once FeedWordPress is made available | |
| 36 | - as a plugin, each individual blog can choose to activate FeedWordPress | |
| 37 | - and syndicate content from its own set of contributors. | |
| 38 | - | |
| 39 | -* DISPLAY OF MAGPIE WARNINGS: A number of MagpieRSS warnings or error | |
| 40 | - messages that were displayed when performing an automatic update are | |
| 41 | - no longer displayed, unless debugging parameters have been explicitly | |
| 42 | - enabled. | |
| 43 | - | |
| 44 | -* BUG RELATED TO INTERNATIONAL CHARACTERS IN AUTHOR NAMES FIXED: Due to a | |
| 45 | - subtle incompatability between the way that FeedWordPress generated new | |
| 46 | - user information, and the way that WordPress 2.0 and later added new | |
| 47 | - authors to the database, FeedWordPress might end up creating duplicate | |
| 48 | - authors, or throwing a critical error message, when it encountered | |
| 49 | - authors whose names included international characters. This | |
| 50 | - incompatability has now been fixed; hopefully, authors with | |
| 51 | - international characters in their names should now be handled properly. | |
| 52 | - | |
| 53 | -* media:content BUG IN MAGPIERSS FIXED: A bug in MagpieRSS's handling of | |
| 54 | - namespaced elements has been fixed. Among other things, this bug caused | |
| 55 | - items containing a Yahoo MediaRSS `<media:content>` element (such as | |
| 56 | - many of the feeds produced by wordpress.com) to be represented | |
| 57 | - incorrectly, with only a capital "A" where the content of the post | |
| 58 | - should have been. Feeds containing `<media:content>` elements should now | |
| 59 | - be syndicated correctly. | |
| 60 | - | |
| 61 | -* update_feedwordpress PARAMETER: You can now use an HTTP GET parameter | |
| 62 | - (`update_feedwordpress=1`) to request that FeedWordPress poll its feeds | |
| 63 | - for updates. When used together with a crontab or other means of | |
| 64 | - scheduling tasks, this means that you can keep your blog automatically | |
| 65 | - updated on a regular schedule, even if you do not choose to use the | |
| 66 | - cron-less automatic updates option. | |
| 67 | - | |
| 68 | -* Some minor interface-related bugs were also fixed. | |
| 69 | - | |
| 70 | - | |
| 71 | -Changes from 0.981 to 0.99 | |
| 72 | -Version 0.99 adds several significant new features, fixes some bugs, and | |
| 73 | -provides compatability with WordPress 2.2.x and 2.3.x. | |
| 74 | - | |
| 75 | -* WORDPRESS 2.2 AND 2.3 COMPATIBILITY: FeedWordPress should now be | |
| 76 | - compatible with WordPress version 2.2 and the upcoming WordPress | |
| 77 | - version 2.3. In particular, it has been tested extensively against | |
| 78 | - WordPress 2.2.3 and WordPress 2.3 Release Candidate 1. | |
| 79 | - | |
| 80 | -* AUTOMATIC UPDATES WITHOUT CRON: FeedWordPress now allows you to | |
| 81 | - automatically schedule checks for new posts without using external task | |
| 82 | - scheduling tools such as cron. In order to enable automatic updates, go | |
| 83 | - to **Syndication --> Options** and set "Check for new posts" to | |
| 84 | - "automatically." For details, see "Automatic Feed Updates" in | |
| 85 | - README.text. | |
| 86 | - | |
| 87 | - An important side-effect of the changes to the update system is that if | |
| 88 | - you were previously using the cron job and the `update-feeds.php` script | |
| 89 | - to schedule updates, you need to change your cron set-up. The old | |
| 90 | - `update-feeds.php` script no longer exists. Instead, if you wish to use | |
| 91 | - a cron job to guarantee updates on a particular schedule, you should | |
| 92 | - have the cron job fetch the front page of your blog (for example, by | |
| 93 | - using `curl http://www.zyx.com/blog/ > /dev/null`) instead of activating | |
| 94 | - the `update-feeds.php` script. If automatic updates have been enabled, | |
| 95 | - fetching the front page will automatically trigger the update process. | |
| 96 | - | |
| 97 | -* INTERFACE REORGANIZATION: All FeedWordPress functions are now located | |
| 98 | - under a top-level "Syndication" menu in the WordPress Dashboard. To | |
| 99 | - manage the list of syndicated sites, manually check for new posts on | |
| 100 | - one or more feeds, or syndicate a new site, you should use the main page | |
| 101 | - under **Syndication**. To change global settings for FeedWordPress, | |
| 102 | - you should use **Syndication --> Options**. | |
| 103 | - | |
| 104 | -* FILE STRUCTURE REORGANIZATION: Due to a combination of changing styles | |
| 105 | - for FeedWordPress plugins and lingering bugs in the FeedWordPress admin | |
| 106 | - menu code, the code for FeedWordPress is now contained in two different | |
| 107 | - PHP files, which should be installed together in a subdirectory of your | |
| 108 | - plugins directory named `feedwordpress`. (See README.text for | |
| 109 | - installation and upgrade instructions relating to the change.) | |
| 110 | - | |
| 111 | -* MULTIPLE CATEGORIES SETTING: Some feeds use non-standard methods to | |
| 112 | - indicate multiple categories within a single category element. (The most | |
| 113 | - popular site to do this is del.icio.us, which separates tags with a | |
| 114 | - space.) FeedWordPress now allows you to set an optional setting, for any | |
| 115 | - feed which does this, indicating the character or characters used to | |
| 116 | - divide multiple categories, using a Perl-compatible regular expression. | |
| 117 | - (In the case of del.icio.us feeds, FeedWordPress will automatically use | |
| 118 | - \s for the pattern without your having to do any further configuration.) | |
| 119 | - To turn this setting on, simply use the "Edit" link for the feed that | |
| 120 | - you want to turn it on for. | |
| 121 | - | |
| 122 | -* REGULAR EXPRESSION BUG FIXED: Eliminated a minor bug in the regular | |
| 123 | - expressions for e-mail addresses (used in parsing RSS `author` | |
| 124 | - elements), which could produce unsightly error messages for some users | |
| 125 | - parsing RSS 2.0 feeds. | |
| 126 | - | |
| 127 | -* DATE / UPDATE BUG FIXED: A bug in date handling was eliminated that may | |
| 128 | - have caused problems if any of (1) WordPress, or (2) PHP, or (3) your | |
| 129 | - web server, or (4) your MySQL server, has been set to use a different | |
| 130 | - time zone from the one that any of the others is set to use. If | |
| 131 | - FeedWordPress has not been properly updating updated posts, or has been | |
| 132 | - updating posts when there shouldn't be any changes for the update, this | |
| 133 | - release may solve that problem. | |
| 134 | - | |
| 135 | -* GOOGLE READER BUGS FIXED: A couple of bugs that made it difficult for | |
| 136 | - FeedWordPress to interact with Google Reader public feeds have been | |
| 137 | - fixed. Firstly, if you encountered an error message reading "There was a | |
| 138 | - problem adding the newsfeed. [SQL: ]" when you tried to add the feed, | |
| 139 | - the cause of this error has been fixed. Secondly, if you succeeded in | |
| 140 | - getting FeedWordPress to check a Google Reader feed, only to find that | |
| 141 | - the title of posts had junk squashed on to the end of them, that bug | |
| 142 | - has been fixed too. To fix this bug, you must install the newest version | |
| 143 | - of the optional MagpieRSS upgrade. | |
| 144 | - | |
| 145 | -* FILTER PARAMETERS: Due to an old, old bug in WordPress 1.5.0 (which was | |
| 146 | - what was available back when I first wrote the filter interface), | |
| 147 | - FeedWordPress has traditionally only passed one parameter to | |
| 148 | - syndicated_item and syndicated_post filters functions -- an array | |
| 149 | - containing either the Magpie representation of a syndicated item from | |
| 150 | - the feed, or the database representation of a post about to be inserted | |
| 151 | - into the WordPress database. If you needed information about the feed | |
| 152 | - that the item came from, this was accessible only through a pair of | |
| 153 | - global variables, $fwp_channel and $fwp_feedmeta. | |
| 154 | - | |
| 155 | - Since it's been a pretty long time since WordPress 1.5.0 was in | |
| 156 | - widespread usage, I have gone ahead and added an optional second | |
| 157 | - parameter to the invocation of the syndicated_item and syndicated_post | |
| 158 | - filters. If you have written a filter for FeedWordPress that uses either | |
| 159 | - of these hooks, you can now register that filter to accept 2 parameters. | |
| 160 | - If you do so, the second parameter will be a SyndicatedPost object, | |
| 161 | - which, among other things, allows you to access information about the | |
| 162 | - feed from which an item is syndicated using the $post->feed and the | |
| 163 | - $post->feedmeta elements (where $post is the name of the second | |
| 164 | - parameter). | |
| 165 | - | |
| 166 | - NOTE THAT THE OLD GLOBAL VARIABLES ARE STILL AVAILABLE, for the time | |
| 167 | - being at least, so existing filters will not break with the upgrade. | |
| 168 | - They should be considered deprecated, however, and may be eliminated in | |
| 169 | - the future. | |
| 170 | - | |
| 171 | -* FILTER CHANGE / BUGFIX: the array that is passed as the first argument | |
| 172 | - syndicated_post filters no longer is no longer backslash-escaped for | |
| 173 | - MySQL when filters are called. This was originally a bug, or an | |
| 174 | - oversight; the contents of the array should only be escaped for the | |
| 175 | - database *after* they have gone through all filters. IF YOU HAVE WRITTEN | |
| 176 | - ANY syndicated_post FILTERS THAT PRESUME THE OLD BEHAVIOR OF PASSING IN | |
| 177 | - STRINGS THAT ARE ALREADY BACKSLASH-ESCAPED, UPDATE YOUR FILTERS | |
| 178 | - ACCORDINGLY. | |
| 179 | - | |
| 180 | -* OTHER MINOR BUGFIXES AND INTERNAL CHANGES: The internal architecture of | |
| 181 | - FeedWordPress has been significantly changed to make the code more | |
| 182 | - modular and clean; hopefully this should help reduce the number of | |
| 183 | - compatibility updates that are needed, and make them easier and quicker | |
| 184 | - when they are needed. | |
| 185 | - | |
| 186 | -Changes from 0.98 to 0.981 | |
| 187 | -Version 0.981 is a narrowly targeted bugfix and compatibility release, whose | |
| 188 | -main purpose is to resolve a major outstanding problem: the incompatibility | |
| 189 | -between version 0.98 of WordPress and the recently released WordPress 2.1. | |
| 190 | - | |
| 191 | -* WORDPRESS 2.1 COMPATIBILITY: FeedWordPress is now compatible with | |
| 192 | - WordPress 2.1, as well as retaining its existing support for WordPress | |
| 193 | - 2.0 and 1.5. Incompatibilities that resulted in database warnings, fatal | |
| 194 | - errors, and which prevented FeedWordPress from syndicating new posts, | |
| 195 | - have been eliminated. | |
| 196 | - | |
| 197 | -* RSS-FUNCTIONS.PHP RENAMED TO RSS.PHP: if you use the upgraded MagpieRSS | |
| 198 | - replacement that's included with FeedWordPress, be sure to note that | |
| 199 | - there are now *two* files to upload from the `OPTIONAL/wp-includes` | |
| 200 | - subdirectory in order to carry out the upgrade: rss-functions.php and | |
| 201 | - rss.php. **It is necessary to upload both files**, due to a change in | |
| 202 | - the file naming scheme in WordPress 2.1, and it is necessary to do so | |
| 203 | - whether you are using WordPress 2.1 or not. If you only upload the | |
| 204 | - `rss-functions.php` file as in previous installations you will not have | |
| 205 | - a working copy of MagpieRSS; the rss.php file contains the actual code. | |
| 206 | - | |
| 207 | -* DATE BUG AFFECTING SOME PHP INSTALLATIONS RESOLVED: due to a subtle bug | |
| 208 | - in parse_w3cdtf(), some installations of PHP encountered problems with | |
| 209 | - FeedWordPress's attempt to date posts, which would cause some new posts | |
| 210 | - on Atom feeds to be dated as if they had apppeared in 1969 or 1970 | |
| 211 | - (thus, effectively, never appearing on front apge at all). This bug in | |
| 212 | - the date handling should now be fixed. | |
| 213 | - | |
| 214 | -* PHP <?=...?> SHORT FORM ELIMINATED: some installations of PHP do not | |
| 215 | - allow the <?=...?> short form for printing PHP values, which was used | |
| 216 | - extensively in the FeedWordPress interface code. Since this could cause | |
| 217 | - fatal errors for users with the wrong installation of PHP, the short | |
| 218 | - form has been replaced with full PHP echo statements, and is no longer | |
| 219 | - used in FeedWordPress. | |
| 220 | - | |
| 221 | -* BETTER USER INTERFACE INTEGRATION WITH WORDPRESS 2.x: Some minor changes | |
| 222 | - have been made to help the FeedWordPress interface pages blend in better | |
| 223 | - with the user interface when running under WordPress 2.x. | |
| 224 | - | |
| 225 | -* GLOBAL CATEGORIES BUG RESOLVED: a bug that prevented some users from | |
| 226 | - setting one or more categories to apply to syndicated posts from all | |
| 227 | - feeds (using the checkbox interface under Options --> Syndication) has | |
| 228 | - been resolved. | |
| 229 | - | |
| 230 | -Changes from 0.97 to 0.98 | |
| 231 | - | |
| 232 | -* WORDPRESS 2.0 COMPATIBILITY: This is a narrowly-targeted release to | |
| 233 | - solve a major outstanding problem. FeedWordPress is now compatible with | |
| 234 | - both WordPress 1.5 and WordPress 2.0. Incompatibilities that caused | |
| 235 | - fatal SQL errors, and a more subtle bug with off-kilter counts of posts | |
| 236 | - under a given category, have been resolved. FeedWordPress tests for | |
| 237 | - database schema using the global $wp_db_version variable (if null, then | |
| 238 | - we presume that we're dealing with WordPress 1.5). | |
| 239 | - | |
| 240 | - NOTE: I have **not** fully tested FeedWordPress with WordPress 2.0. | |
| 241 | - Further testing may reveal more bugs. However, you should now be able | |
| 242 | - to get at least basic FeedWordPress functionality up and running. | |
| 243 | - | |
| 244 | -* AUTHOR MATCHING: FeedWordPress tests several fields to see if it can | |
| 245 | - identify the author of the post as a user already in the WordPress user | |
| 246 | - database. In previous versions, it tested the user login, the nickname, | |
| 247 | - and tested for "aliases" listed in the Profile (see documentation). FWP | |
| 248 | - now also matches authors on the basis of e-mail address (*if* an e-mail | |
| 249 | - address is present). This is particularly helpful for formats such as | |
| 250 | - RSS 2.0, in which authors are primarily identified by e-mail addresses. | |
| 251 | - | |
| 252 | 4 | Changes from 0.96 to 0.97 |
| 253 | 5 | ------------------------- |
| 254 | 6 | |
| 255 | 7 | * INSTALLATION PROCEDURE: Some of the changes between 0.96 and 0.97 |
