| @@ -1,431 +1,7 @@ | ||
| 1 | 1 | FeedWordPress Change Log |
| 2 | 2 | ======================== |
| 3 | -Changes from 2009.0613 to 2009.0618 | |
| 4 | -* BUGFIX: MYSTERY ERRORS WITH WITH WP_Http_Fsockopen HTTP TRANSPORT | |
| 5 | - ELIMINATED: Thanks to a combination of a subtle bug in FeedWordPress, | |
| 6 | - and changes to the HTTP transport code in WordPress, a number of users | |
| 7 | - encountered an error in which any time they attempted to add a new feed | |
| 8 | - through the FeedFinder interface, FeedWordPress would fail and display | |
| 9 | - an HTTP request failure diagnostic message. The subtle bug has been | |
| 10 | - fixed, and with it, most of these errors should now be eliminated. | |
| 11 | - | |
| 12 | - Be sure to upgrade your MagpieRSS to the most recent MagpieRSS version | |
| 13 | - after you have insalled FeedWordPress 2009.0618, or this bug fix will | |
| 14 | - not take effect. | |
| 15 | 3 | |
| 16 | - | |
| 17 | -Changes from 2009.0612 to 2009.0613 | |
| 18 | -* INTERFACE/BUGFIX: WORDPRESS 2.8 CATEGORY BOX FIX. Thanks to a subtle | |
| 19 | - change in class names between the WordPress 2.7 and 2.8 stylesheets, | |
| 20 | - category boxes in the FeedWordPress settings interface tended to overflow | |
| 21 | - and have a lot of messy-looking overlapping text under WordPress 2.8. | |
| 22 | - This has now been fixed. | |
| 23 | - | |
| 24 | -* FeedFinder FAILURE DIAGNOSTICS: When FWP's FeedFinder fails to find any | |
| 25 | - feeds at a given URL (for example, when you are trying to add a | |
| 26 | - subscription through the administrative interface and you run into an | |
| 27 | - error message), FeedWordPress now provides more diagnostic information | |
| 28 | - for the reasons behind the failure. If that helps you, great; if not, | |
| 29 | - it should help me respond more intelligently to your support request.. | |
| 30 | - | |
| 31 | -Changes from 2008.1214 to 2009.0612 | |
| 32 | -* WORDPRESS 2.8 COMPATIBILITY: FeedWordPress 2009.0612 has been tested for | |
| 33 | - compatibility with the recent version 2.8 release of WordPress. | |
| 34 | - | |
| 35 | -* INTERFACE RESTRUCTURING: In order to avoid settings posts from becoming | |
| 36 | - too crowded, and to modularize and better organize the user interface, | |
| 37 | - new "Posts" and "Categories & Tags" subpages have been created under the | |
| 38 | - "Syndication" menu. "Posts" controls settings for individal syndicated | |
| 39 | - posts (such as publication status, comment and ping status, whether or | |
| 40 | - not to use the original location of the post as the permalink, whether | |
| 41 | - or not to expose posts to formatting filters, and so on). "Categories & | |
| 42 | - Tags" controls settings for assigning new syndicated posts to categories | |
| 43 | - and tags, such as categories or tags to apply to all syndicated posts, | |
| 44 | - and how to handle categories that do not yet exist in the WordPress | |
| 45 | - database. These subpages, like the Authors subpage, handle settings for | |
| 46 | - the global default level and for individual syndicated feeds. | |
| 47 | - | |
| 48 | - Corresponding to these new subpages, the old Syndication Settings and | |
| 49 | - Feed Settings subpages have been cleaned up and simplified, and now only | |
| 50 | - link to the appropriate subpages for options that can be set in the | |
| 51 | - Posts, Authors, or Categories & Tags subpages. | |
| 52 | - | |
| 53 | -* FEATURE: ADD CUSTOM SETTINGS TO EACH SYNDICATED POST: FeedWordPress has | |
| 54 | - long had an interface for creating custom settings for each syndicated | |
| 55 | - *feed* which could be retrieved in templates using the `get_feed_meta()` | |
| 56 | - template function. But it had no feature for adding custom fields to | |
| 57 | - each individual syndicated *post*. In response to requests from users, I | |
| 58 | - have added the ability to apply custom fields to each individual | |
| 59 | - syndicated post, using the new Syndication --> Posts subpage. You can | |
| 60 | - set up custom fields to be applied to every syndicated post, or custom | |
| 61 | - fields to be applied to syndicated posts from a particular feed. | |
| 62 | - | |
| 63 | -* FEATURE: MAGPIERSS VERSION CHECK AND UPGRADE: FeedWordPress will attempt | |
| 64 | - to determine whether or not you are using the upgraded version of | |
| 65 | - MagpieRSS that comes packaged with FeedWordPress. If not, it will throw | |
| 66 | - an error on admin pages, and, if you are a site administrator, it will | |
| 67 | - give you the option to ignore the error message, or to attempt an | |
| 68 | - automatic upgrade (using a native file copy). If the file copy fails, | |
| 69 | - FeedWordPress will offer some guidance on how to perform the upgrade | |
| 70 | - manually. | |
| 71 | - | |
| 72 | -* BLANK POSTS PROBLEM NO LONGER OCCURS WITH OLD & BUSTED MAGPIERSS: Due | |
| 73 | - to the fact that I relied on a content normalization that occurs in my | |
| 74 | - upgraded version of MagpieRSS, but not in the old & busted version of | |
| 75 | - MagpieRSS that ships with WordPress, until this version, if you tried to | |
| 76 | - syndicate an Atom feed without having performed the (*strongly | |
| 77 | - recommended*) MagpieRSS upgrade, all of the posts would come up with | |
| 78 | - completely blank contents. That's not because MagpieRSS couldn't read | |
| 79 | - the data, but rather because the new Magpie version puts that data in a | |
| 80 | - location where the old version doesn't, and I was only looking in that | |
| 81 | - newer location. Now it checks for both, meaning that posts will continue | |
| 82 | - to display their contents even if you don't upgrade MagpieRSS. (But you | |
| 83 | - **really should** upgrade it, anyway.) | |
| 84 | - | |
| 85 | -* BUGFIX: RELATIVE URI RESOLUTION FOR POST CONTENT RESTORED. Some time | |
| 86 | - back, I added support for resolving relative URIs against xml:base on | |
| 87 | - feeds that support it to the MagpieRSS upgrade in FeedWordPress. Then I | |
| 88 | - took out code that did the same thing from the main FeedWordPress code. | |
| 89 | - Of course, the problem is that some people, even though it is clearly | |
| 90 | - stupid or evil to do so, still include relative URIs for images or links | |
| 91 | - in posts on feed formats that do *not* adequately support xml:base | |
| 92 | - (notably, RSS 2.0 feeds). In response to a user request, I have added | |
| 93 | - this functionality back in, so that MagpieRSS will resolve any relative | |
| 94 | - URIs that it knows how to resolve using xml:base, and then FeedWordPress | |
| 95 | - will attempt to resolve any relative URIs that are left over afterwards. | |
| 96 | - | |
| 97 | -* BUGFIX: INTERFACE OPTION FOR SETTING SYNDICATED POST PUBLICATION STATUS | |
| 98 | - ON A FEED-BY-FEED BASIS HAS BEEN RESTORED: Due to a version-checking | |
| 99 | - bug, users of WordPress 2.7.x lost an option from the "Edit a syndicated | |
| 100 | - feed" interface which allowed them to determine whether newly syndicated | |
| 101 | - posts should be published immediately, held as "Pending Review," saved | |
| 102 | - as drafts, or saved as private posts. (The option to change this | |
| 103 | - setting globally remained in place, but users could no longer set it on | |
| 104 | - a feed-by-feed basis.) The version-checking bug has been fixed, and the | |
| 105 | - option has been restored. | |
| 106 | - | |
| 107 | -* BUGFIX: "ARE YOU SURE?" FATAL ERROR ELIMINATED AND SECURITY IMPROVED: | |
| 108 | - Under certain circumstances (for example, when users have configured | |
| 109 | - their browser or proxy not to send HTTP Referer headers, for privacy or | |
| 110 | - other reasons), many features in the FeedWordPress administrative | |
| 111 | - interface (such as adding new feeds or changing settings) would hit a | |
| 112 | - fatal error, displaying only a cryptic message reading "Are you sure?" | |
| 113 | - and a blank page following it. This problem has been eliminated by | |
| 114 | - taking advantage of WordPress's nonce functions, which allow the | |
| 115 | - security check which ran into this error to work properly even without | |
| 116 | - receiving an HTTP Referer header. (N.B.: WordPress's nonce functions | |
| 117 | - were first introduced in WordPress 2.0.3. If you're using FeedWordPress | |
| 118 | - with an older version of WordPress, there's no fix for this problem: | |
| 119 | - you'll just need to turn Referer headers back on. Sorry.) | |
| 120 | - | |
| 121 | -* BUGFIX: MANUALLY-ALTERED POST STATUS, COMMENT STATUS, AND PING STATUS NO | |
| 122 | - LONGER REVERTED BY POST UPDATES: If you manually altered the post status, | |
| 123 | - comment status, or ping status of a syndicated post from what it was set | |
| 124 | - to when first syndicated -- for example, if you had a feed that was set | |
| 125 | - to bring in new posts as "Pending Review," and you then marked some of | |
| 126 | - the pending posts as "Published" and others as "Unpublished" -- then | |
| 127 | - in previous versions of FeedWordPress, these manual changes to the | |
| 128 | - status would be lost -- so that, for example, your Published or Unpublished | |
| 129 | - articles would revert to Pending Review -- if the source feed made any | |
| 130 | - upates to the item. This could make the Pending Review feature both | |
| 131 | - unreliable and also extremely frustrating to work with. The good news is | |
| 132 | - that this bug has since been fixed: if you manually update the status | |
| 133 | - of a post, it will no longer be reverted if or when the post is updated. | |
| 134 | - | |
| 135 | -* BUGFIX: OCCASIONAL FATAL ERROR ON UPDATE ELIMINATED: Under certain | |
| 136 | - limited conditions (specifically, when both the title and the content of | |
| 137 | - a post to be updated are empty), an attempt to update the post would | |
| 138 | - result in a fatal error. This has been fixed. | |
| 139 | - | |
| 140 | -* INTERFACE: "CONFIGURE SETTINGS" CONVENIENCE LINK ADDED TO CONFIRMATION | |
| 141 | - MESSAGE WHEN A NEW FEED IS ADDED: When you add a new subscription to | |
| 142 | - FeedWordPress, the message box that appears to confirm it now includes a | |
| 143 | - handy link to the feed's settings subpage, so that you can quickly set | |
| 144 | - up any special settings you may want to set up for the new feed, without | |
| 145 | - having to hunt through the list of all your other subscriptions to pick | |
| 146 | - out the new one. | |
| 147 | - | |
| 148 | -* INTERFACE: SIMPLIFYING AND CLARIFYING AUTOMATIC UPDATES SETTINGS. I have | |
| 149 | - removed an interval setting for the cronless automatic updates which has | |
| 150 | - confused many FeedWordPress users. In past versions of FWP, when you | |
| 151 | - turned on automatic updates, you would be presented with a time interval | |
| 152 | - setting which controlled how often FeedWordPress would check for feeds | |
| 153 | - ready to be polled for updates. (That is, it DID NOT control how often | |
| 154 | - feeds *would be polled*; it controlled how often FeedWordPress would | |
| 155 | - *check* for feeds that *had become ready to poll*. The schedule on which | |
| 156 | - feeds became ready for polling was still controlled either by requests | |
| 157 | - encoded in elements within the feed itself, or else according to an | |
| 158 | - internal calculation within FeedWordPress, averaging out to about 1 hour, | |
| 159 | - if the feed did not include any scheduling request elements.) Since many | |
| 160 | - users very often (and understandably) confused the purpose of this | |
| 161 | - setting, and since the setting is for a feature that's actually very | |
| 162 | - unlikely to require any manual control by the user, I have removed the | |
| 163 | - setting; FeedWordPress now simply uses the default value of checking for | |
| 164 | - feeds to poll every 10 minutes. | |
| 165 | - | |
| 166 | -* FEEDFINDER PERFORMANCE IMPROVEMENT: FeedWordPress's FeedFinder class | |
| 167 | - now uses `array_unique()` to make sure that it doesn't waste time | |
| 168 | - repeatedly iterating over and polling the same URI. Props to Camilo | |
| 169 | - (<http://projects.radgeek.com/2008/12/14/feedwordpress-20081214/#comment-20090122160414>). | |
| 170 | - | |
| 171 | -Changes from 2008.1105 to 2008.1214 | |
| 172 | - | |
| 173 | -* WORDPRESS 2.7 COMPATIBILITY: FeedWordPress has been tested for | |
| 174 | - compatibility with the newly released WordPress 2.7. WordPress 2.7 has | |
| 175 | - deprecated the Snoopy library for HTTP requests, which caused a fatal | |
| 176 | - error for users who had not installed the MagpieRSS upgrade (or whose | |
| 177 | - installation of the MagpieRSS upgrade was overwritten by a recent update | |
| 178 | - of WordPress). FeedWordPress now handles things gracefully when Snoopy | |
| 179 | - is not immediately available. | |
| 180 | - | |
| 181 | -* INTERFACE SPIFFED UP: Interface elements have been updated so that | |
| 182 | - FeedWordPress's management interface fits in more naturally with the | |
| 183 | - WordPress 2.7 interface (including a new logo and a number of small | |
| 184 | - interface tweaks). | |
| 185 | - | |
| 186 | -* BUG WITH TAGS FOR SYNDICATED ARTICLES FIXED: Several users encountered a | |
| 187 | - bug with the option to add tags to all syndicated posts under | |
| 188 | - Syndication --> Settings -- if you told FeedWordPress to add more than | |
| 189 | - one tag to all syndicated posts, instead of doing so correctly, it would | |
| 190 | - add a *single* tag instead, whose name was composed of the names of all | |
| 191 | - the tags you asked it to add. This bug was the result of nothing more | |
| 192 | - dignified than a typographical error on my part. It has now been fixed. | |
| 193 | - | |
| 194 | -* MORE INFORMATION AVAILABLE WHEN FEEDWORDPRESS CAN'T FIND A FEED: When | |
| 195 | - you enter a URL for a new syndication source, FeedWordPress uses a | |
| 196 | - simple feed-finding algorithm (originally based on Mark Pilgrim's | |
| 197 | - Universal Feed Finder) to try to determine whether the URL is the URL | |
| 198 | - for a feed, or, if the URL points to an ordinary website rather than to | |
| 199 | - a feed, whether there is a feed for that website. All well and good, but | |
| 200 | - if FeedWordPress failed to find a feed, for whatever reason, it would | |
| 201 | - typically return nothing more than a nasty little note to the effect of | |
| 202 | - "no feed found," without any explanation of what went wrong. | |
| 203 | - FeedWordPress now keeps track of error conditions from the HTTP | |
| 204 | - requests that it uses in the course of looking for the feed, and so may | |
| 205 | - be able to give you a bit more information about the nature of the | |
| 206 | - problem if something goes wrong. | |
| 207 | - | |
| 208 | - | |
| 209 | -Changes from 2008.1101 to 2008.1105 | |
| 210 | - | |
| 211 | -* INTERFACE RESTRUCTURING AND SYNDICATION --> AUTHORS PAGE: As a first | |
| 212 | - step towards modularizing and better organizing the user interface, a | |
| 213 | - new "Authors" subpage has been created under the Syndication menu, which | |
| 214 | - controls settings for syndicated authors, both at the global default | |
| 215 | - level and at level of individual syndicated feeds. | |
| 216 | - | |
| 217 | -* BUG RELATED TO THE ATTRIBUTION OF POSTS TO THE WRONG AUTHOR FIXED: Some | |
| 218 | - users encountered an issue in which posts by different authors on | |
| 219 | - different blogs -- especially blogs generated by Blogger -- were | |
| 220 | - mistakenly attributed to a single author. The problem was caused by the | |
| 221 | - way in which FeedWordPress matches syndicated authors to user accounts | |
| 222 | - in the WordPress database: normally, if two feeds each list an author | |
| 223 | - with the same e-mail address, they are counted as being the same person. | |
| 224 | - Normally this works well, but it creates an issue in cases where | |
| 225 | - blogging software assigns a single anonymous e-mail address to users who | |
| 226 | - do not want their real e-mail address published. This is, for example, | |
| 227 | - what Blogger does (by giving all users a default e-mail address of | |
| 228 | - <noreply@blogger.com> if they don't want their own e-mail address | |
| 229 | - listed). FeedWordPress now allows the user to correct for this problem | |
| 230 | - with a couple of new settings under **Syndication --> Authors**, which | |
| 231 | - allow users to turn off e-mail based author matching for particular | |
| 232 | - addresses, or, if desired, to turn it off entirely. By default, e-mail | |
| 233 | - based author matching is still turned on, but disabled for a list of | |
| 234 | - known generic e-mail addresses. Right now, the "list" consists entirely | |
| 235 | - of <noreply@blogger.com>; if you know other addresses that should be | |
| 236 | - added, please [contact me](http://radgeek.com/contact) to let me know. | |
| 237 | - | |
| 238 | - Please note that if you have already encountered this issue on your | |
| 239 | - blog, upgrading FeedWordPress will prevent it from re-occurring in the | |
| 240 | - future, but you still need to do two other things to fix the existing | |
| 241 | - problem on your blog. | |
| 242 | - | |
| 243 | - First, for each feed where posts have been mis-attributed, you need to | |
| 244 | - change the existing author mapping rules to re-map a a syndicated | |
| 245 | - author's name to the proper target account. Go to **Syndication --> | |
| 246 | - Authors**, select the feed you want to change from the drop-down list, | |
| 247 | - and then change the settings under the "Syndicated Authors" section. | |
| 248 | - (You will probably need to select "will be assigned to a new user..." to | |
| 249 | - create a new user account with the appropriate name.) | |
| 250 | - | |
| 251 | - Second, for each feed where posts have been mis-attributed, you need to | |
| 252 | - re-assign already-syndicated posts that were mis-attributed to the | |
| 253 | - correct author. You can do that from **Syndication --> Authors** by | |
| 254 | - using the author re-assignment feature, described below. | |
| 255 | - | |
| 256 | -* AUTHOR RE-ASSIGNMENT FOR A PARTICULAR FEED: The author settings page | |
| 257 | - for each syndicated feed, under **Syndication --> Authors**, now | |
| 258 | - includes an section titled "Fixing mis-matched authors," which provides | |
| 259 | - an interface for re-assigning or deleting all posts attributed to a | |
| 260 | - particular author on a particular feed. | |
| 261 | - | |
| 262 | -* SUPPORT FOR `<atom:source>` ELEMENT IN SYNDICATED FEEDS: Some feeds | |
| 263 | - (for example, those produced by FeedWordPress) aggregate content from | |
| 264 | - several different sources, and include information about the original | |
| 265 | - source of the post in an `<atom:source>` element. A new setting under | |
| 266 | - **Syndication --> Options** allows you to control what FeedWordPress | |
| 267 | - will report as the source of posts syndicated from aggregator feeds in | |
| 268 | - your templates and feeds: you can have FeedWordPress report that the | |
| 269 | - source of a post is the aggregator feed itself, or you can have it | |
| 270 | - report that the source of a post is the original source that the | |
| 271 | - aggregator originally syndicated the post from. | |
| 272 | - | |
| 273 | - By default, FeedWordPress will report the aggregator, not the original | |
| 274 | - source, as the source of a syndicated item. | |
| 275 | - | |
| 276 | -* LOAD BALANCING AND TIME LIMITING FEATURES FOR UPDATES: Some users have | |
| 277 | - encountered issues due to running up against PHP execution time limits | |
| 278 | - during the process of updating large syndicated feeds, or a very large | |
| 279 | - set of syndicated feeds. FeedWordPress now has a feature that allows you | |
| 280 | - to limit the total amount of time spent updating a feed, through the | |
| 281 | - "Time limit on updates" setting under **Syndication --> Options**. By | |
| 282 | - turning on this setting and adjusting the time limit to a low enough | |
| 283 | - figure to avoid your PHP installation's time-out setting. (PHP execution | |
| 284 | - time limits are usually in the vicinity of 30 seconds, so an update | |
| 285 | - time limit of 25 seconds or so should provide plenty of time for updates | |
| 286 | - while allowing a cushion of time for other, non-update-related functions | |
| 287 | - to do their work.) | |
| 288 | - | |
| 289 | - If feed updates are interrupted by the time limit, FeedWordPress uses | |
| 290 | - some simple load balancing features to make sure that updates to other | |
| 291 | - feeds will not be blocked by the time-hogging feed, and will also make | |
| 292 | - sure that when the interrupted update is resumed, FeedWordPress will | |
| 293 | - skip ahead to resume processing items at the point at which it was | |
| 294 | - interrupted last time, so that posts further down in the feed will | |
| 295 | - eventually get processed, and not get blocked by the amount of time it | |
| 296 | - takes to process the items higher up in the feed. | |
| 297 | - | |
| 298 | -* `guid` INDEX CREATION BUTTON: FeedWordPress frequently issues queries on | |
| 299 | - the `guid` column of the WordPress posts database (since it uses post | |
| 300 | - guid URIs to keep track of which posts it has syndicated). In very large | |
| 301 | - FeedWordPress installations, you can often significantly improve | |
| 302 | - performance by creating a database index on the `guid` column, but | |
| 303 | - normally you would need to poke around with MySQL or a tool like | |
| 304 | - phpMyAdmin to do this. FeedWordPress can now save you the trouble: to | |
| 305 | - create an index on the `guid` column, just go to | |
| 306 | - **Syndication --> Options**, and mash the button at the bottom of the | |
| 307 | - "Back End" section. | |
| 308 | - | |
| 309 | -Changes from 2008.1030 to 2008.1101 | |
| 310 | - | |
| 311 | -* INTERFACE BUG THAT PREVENTED ADDING NEW SITES FIXED: The UI reforms in | |
| 312 | - FWP 2008.1030 unintentionally introduced a bug that prevents clean | |
| 313 | - installations of FeedWordPress from providing an input box for adding | |
| 314 | - new feeds to the list of syndicated feeds. This bug has been fixed. | |
| 315 | - | |
| 316 | -Changes from 0.993 to 2008.1030 | |
| 317 | - | |
| 318 | -* WORDPRESS 2.6 COMPATIBILITY: FeedWordPress should now be compatible with | |
| 319 | - WordPress 2.6, and should work more or less seamlessly with the new post | |
| 320 | - revision system. A bug which caused multiple new revisions to be created | |
| 321 | - for posts on certain feeds, regardless of whether or not the item had | |
| 322 | - been updated, has been fixed. | |
| 323 | - | |
| 324 | -* INTERFACE IMPROVEMENTS: The user interface has been substantially | |
| 325 | - restyled to fit in better with the visual style of WordPress 2.5 and | |
| 326 | - 2.6. | |
| 327 | - | |
| 328 | -* YOUTUBE BUG FIXED: POSTS SYNDICATED THROUGH AN AUTOMATIC UPDATE ARE NO | |
| 329 | - LONGER STRIPPED OF `<OBJECT>` TAGS AND CERTAIN OTHER HTML ELEMENTS: Due | |
| 330 | - to the way that some versions of WordPress process posts that are | |
| 331 | - inserted into the database when no user is logged in, many users | |
| 332 | - experienced an issue where YouTube videos and other content using the | |
| 333 | - HTML `<object>` tag would be stripped out of posts that were syndicated | |
| 334 | - during an automatic update. (Posts that were syndicated through manual | |
| 335 | - updates from within the WordPress Dashboard were not affected, because | |
| 336 | - the issue does not arise when an update is executed under a logged-in | |
| 337 | - administrator's credentials.) This bug has now been fixed; YouTube | |
| 338 | - videos and other content using `<object>` tags should now appear | |
| 339 | - properly in syndicated posts, regardless of the way in which the post | |
| 340 | - was syndicated. | |
| 341 | - | |
| 342 | -* AJAX BUGS FIXED: Bugs which blocked the normal operation of WordPress | |
| 343 | - 2.5's AJAX interface elements when FeedWordPress was activated have been | |
| 344 | - fixed. | |
| 345 | - | |
| 346 | -* TAG SUPPORT: A couple of features have been introduced to take advantage | |
| 347 | - of the tagging features in WordPress 2.3.x, 2.5.x, and 2.6.x. Now, when | |
| 348 | - unfamiliar categories are encountered for posts on a feed, you can | |
| 349 | - choose for FeedWordPress (1) to drop the category; (2) to drop the | |
| 350 | - category and to filter out any post that does not match at least one | |
| 351 | - familiar category; (3) to create a new category with that name, or, | |
| 352 | - now, you can also have FeedWordPress (4) create a new *tag* with that | |
| 353 | - name. This option can be set site-wide under Syndication --> Options, | |
| 354 | - or it can be set on a feed-by-feed basis in a feed's Edit screen. | |
| 355 | - | |
| 356 | - In addition, you can now set particular tags to apply to all incoming | |
| 357 | - syndicated posts, under Syndication --> Options, or you can set tags | |
| 358 | - to apply to all incoming syndicated posts from a particular feed in that | |
| 359 | - feed's Edit screen. | |
| 360 | - | |
| 361 | -* FORMATTING FILTERS: There is a new option available under Syndication -> | |
| 362 | - Options which allows users to choose whether or not to expose syndicated | |
| 363 | - posts to being altered by formatting filters. By default, FeedWordPress | |
| 364 | - has always protected syndicated posts (which are already in display-ready | |
| 365 | - HTML when they are syndicated) from being reformatted by formatting | |
| 366 | - filters. However, this approach means that certain plugins which depend | |
| 367 | - on formatting filters (for example, to add "Share This" bars or relevant | |
| 368 | - links to the end of a post) are blocked from working on any syndicated | |
| 369 | - posts. If you want to use one of these plugins together with | |
| 370 | - FeedWordPress, you can now do so by changing the "Formatting Filters" | |
| 371 | - setting from "Protect" to "Expose." | |
| 372 | - | |
| 373 | -* `<atom:source>` ELEMENTS NOW INCLUDED IN ATOM FEED: Atom 1.0 provides | |
| 374 | - a standard method for aggregators to indicate information about the original source of | |
| 375 | - a syndicated post, using the `<atom:source>` element. FeedWordPress now | |
| 376 | - introduces standard `<atom:source>` elements including the title, homepage, and | |
| 377 | - feed URI of the source from which a syndicated post was syndicated. Cf. | |
| 378 | - <http://www.atomenabled.org/developers/syndication/atom-format-spec.php#element.source> | |
| 379 | - | |
| 380 | -* MODULARIZATION OF CODE: The code for different elements of FeedWordPress | |
| 381 | - has been broken out into several modules for easier inspection, | |
| 382 | - documentation, and maintenance of the code. | |
| 383 | - | |
| 384 | -* VERSIONING SCHEME CHANGED: FeedWordPress's feature set has proven stable | |
| 385 | - enough that it can now be removed from beta status; a good thing, since | |
| 386 | - I was very quickly running out of version numbers to use. New releases | |
| 387 | - of FeedWordPress will have version numbers based on the date of their | |
| 388 | - release. | |
| 389 | - | |
| 390 | -Changes from 0.992 to 0.993 | |
| 391 | - | |
| 392 | -* WORDPRESS 2.5.1 COMPATIBILITY: FeedWordPress should now be compatible | |
| 393 | - with WordPress 2.5.1. | |
| 394 | - | |
| 395 | -* WORDPRESS 2.5 INTERFACE IMPROVEMENTS: FeedWordPress's Dashboard | |
| 396 | - interface has undergone several cosmetic changes that should help it | |
| 397 | - integrate better with the WordPress Dashboard interface in WordPress | |
| 398 | - version 2.5.x. | |
| 399 | - | |
| 400 | -* SYNDICATED POSTS CAN BE MARKED AS "PENDING REVIEW": WordPress 2.3 users | |
| 401 | - can now take advantage of WordPress's new "Pending Review" features for | |
| 402 | - incoming syndicated posts. Posts marked as "Pending Review" are not | |
| 403 | - published immediately, but are marked as ready to be reviewed by an | |
| 404 | - Administrator or Editor, who can then choose to publish the post or | |
| 405 | - hold it back. If you want to review syndicated posts from a particular | |
| 406 | - feed, or from all feeds, before they are posted, then use | |
| 407 | - Syndication --> Syndicated Sites --> Edit or Syndication --> Options to | |
| 408 | - change the settings for handling new posts. | |
| 409 | - | |
| 410 | -* AWARE OF NEW URI FOR del.icio.us FEEDS: Previous releases of | |
| 411 | - FeedWordPress already automatically split del.icio.us tags up | |
| 412 | - appropriately appropriately when generating categories. (del.icio.us | |
| 413 | - feeds smoosh all the tags into a single `<dc:subject>` element, | |
| 414 | - separated by spaces; FeedWordPress un-smooshes them into multiple | |
| 415 | - categories by separating them at whitespace.) Unfortunately, del.icio.us | |
| 416 | - recently broke the existing behavior by changing host names for their | |
| 417 | - feeds from del.icio.us to feeds.delicious.com. Version 0.993 accounts | |
| 418 | - for the new host name and un-breaks the tag splitting. | |
| 419 | - | |
| 420 | 4 | Changes from 0.991 to 0.992 |
| 421 | 5 | --------------------------- |
| 422 | 6 | * AUTHOR RE-MAPPING: FeedWordPress now offers considerable control over |
| 423 | 7 | how author names on a feed are translated into usernames within the |
| @@ -456,9 +32,9 @@ | ||
| 456 | 32 | has, hopefully, been resolved, by correcting for the bug in WordPress. |
| 457 | 33 | |
| 458 | 34 | Changes from 0.99 to 0.991 |
| 459 | 35 | -------------------------- |
| 460 | -* WORDPRESS MU COMPATIBILITY: FeedWordPress should now be compatible with | |
| 36 | +* WORDPRESS MU COMPATABILITY: FeedWordPress should now be compatible with | |
| 461 | 37 | recent releases of WordPress MU. Once FeedWordPress is made available |
| 462 | 38 | as a plugin, each individual blog can choose to activate FeedWordPress |
| 463 | 39 | and syndicate content from its own set of contributors. |
| 464 | 40 | |
| @@ -475,12 +51,12 @@ | ||
| 475 | 51 | authors whose names included international characters. This |
| 476 | 52 | incompatability has now been fixed; hopefully, authors with |
| 477 | 53 | international characters in their names should now be handled properly. |
| 478 | 54 | |
| 479 | -* `<media:content>` BUG IN MAGPIERSS FIXED: A bug in MagpieRSS's handling | |
| 480 | - of namespaced elements has been fixed. Among other things, this bug | |
| 481 | - caused items containing a Yahoo MediaRSS `<media:content>` element (such | |
| 482 | - as many of the feeds produced by wordpress.com) to be represented | |
| 55 | +* media:content BUG IN MAGPIERSS FIXED: A bug in MagpieRSS's handling of | |
| 56 | + namespaced elements has been fixed. Among other things, this bug caused | |
| 57 | + items containing a Yahoo MediaRSS `<media:content>` element (such as | |
| 58 | + many of the feeds produced by wordpress.com) to be represented | |
| 483 | 59 | incorrectly, with only a capital "A" where the content of the post |
| 484 | 60 | should have been. Feeds containing `<media:content>` elements should now |
| 485 | 61 | be syndicated correctly. |
| 486 | 62 | |
| @@ -635,9 +211,9 @@ | ||
| 635 | 211 | * DATE BUG AFFECTING SOME PHP INSTALLATIONS RESOLVED: due to a subtle bug |
| 636 | 212 | in parse_w3cdtf(), some installations of PHP encountered problems with |
| 637 | 213 | FeedWordPress's attempt to date posts, which would cause some new posts |
| 638 | 214 | on Atom feeds to be dated as if they had apppeared in 1969 or 1970 |
| 639 | - (thus, effectively, never appearing on front page at all). This bug in | |
| 215 | + (thus, effectively, never appearing on front apge at all). This bug in | |
| 640 | 216 | the date handling should now be fixed. |
| 641 | 217 | |
| 642 | 218 | * PHP <?=...?> SHORT FORM ELIMINATED: some installations of PHP do not |
| 643 | 219 | allow the <?=...?> short form for printing PHP values, which was used |
| @@ -719,9 +295,9 @@ | ||
| 719 | 295 | regular expressions and careful matching of lowercasing functions |
| 720 | 296 | (comparing results from PHP only to other results from PHP, and results |
| 721 | 297 | from MySQL only to other results from MySQL). |
| 722 | 298 | |
| 723 | -* BUG FIX: Items dated December 31, 1969 should appear less often. The | |
| 299 | +* BUG FIX: Items dated Decembr 31, 1969 should appear less often. The | |
| 724 | 300 | function for parsing W3C date-time format dates that ships with |
| 725 | 301 | MagpieRSS can only correctly parse fully-specified dates with a |
| 726 | 302 | fully-specified time, but valid W3C date-time format dates may omit the |
| 727 | 303 | time, the day of the month, or even the month. Some feeds in the wild |
| @@ -746,9 +322,9 @@ | ||
| 746 | 322 | that all the examples of improper side-effects that I can find now |
| 747 | 323 | require an HTTP POST to take effect. I think I got pretty much |
| 748 | 324 | everything; if there's anything that I missed, let me know. |
| 749 | 325 | |
| 750 | - Further reading: [Sam Ruby 2005-05-06: This Stuff Matters](http://www.intertwingly.net/blog/2005/05/06/This-Stuff-Matters) | |
| 326 | + Further reading: [Sam Ruby 2005-05-06: This Stuff Matters] (http://www.intertwingly.net/blog/2005/05/06/This-Stuff-Matters) | |
| 751 | 327 | |
| 752 | 328 | * BUG FIX: Categories applied by `cats` setting should no longer prevent |
| 753 | 329 | category-based filtering from working. In FeedWordPress, you can (1) |
| 754 | 330 | apply certain categories to all syndicated posts, or all posts from |
| @@ -856,10 +432,9 @@ | ||
| 856 | 432 | into the WordPress database so that (among other things) that post |
| 857 | 433 | will have its enclosure listed in your blog's RSS 2 newsfeed. |
| 858 | 434 | |
| 859 | 435 | Note that enclosure support requires using the optional MagpieRSS |
| 860 | - upgrade (i.e., replacing your `wp-includes/rss-functions.php` with | |
| 861 | - `OPTIONAL/wp-includes/rss-functions.php` from the FWP archive) | |
| 436 | + upgrade (i.e., replacing your `wp-includes/rss-functions.php` with `OPTIONAL/wp-includes/rss-functions.php` from the FWP archive) | |
| 862 | 437 | |
| 863 | 438 | * FEATURE: for completeness's sake, there is now a feed setting, |
| 864 | 439 | `hardcode url`, that allows you to set the URI for the front page |
| 865 | 440 | of a contributor's website manually (that is, prevent it from being |
