| @@ -1,261 +1,7 @@ | ||
| 1 | 1 | FeedWordPress Change Log |
| 2 | 2 | ======================== |
| 3 | 3 | |
| 4 | -Changes from 2008.1105 to 2008.1214 | |
| 5 | - | |
| 6 | -* WORDPRESS 2.7 COMPATIBILITY: FeedWordPress has been tested for | |
| 7 | - compatibility with the newly released WordPress 2.7. WordPress 2.7 has | |
| 8 | - deprecated the Snoopy library for HTTP requests, which caused a fatal | |
| 9 | - error for users who had not installed the MagpieRSS upgrade (or whose | |
| 10 | - installation of the MagpieRSS upgrade was overwritten by a recent update | |
| 11 | - of WordPress). FeedWordPress now handles things gracefully when Snoopy | |
| 12 | - is not immediately available. | |
| 13 | - | |
| 14 | -* INTERFACE SPIFFED UP: Interface elements have been updated so that | |
| 15 | - FeedWordPress's management interface fits in more naturally with the | |
| 16 | - WordPress 2.7 interface (including a new logo and a number of small | |
| 17 | - interface tweaks). | |
| 18 | - | |
| 19 | -* BUG WITH TAGS FOR SYNDICATED ARTICLES FIXED: Several users encountered a | |
| 20 | - bug with the option to add tags to all syndicated posts under | |
| 21 | - Syndication --> Settings -- if you told FeedWordPress to add more than | |
| 22 | - one tag to all syndicated posts, instead of doing so correctly, it would | |
| 23 | - add a *single* tag instead, whose name was composed of the names of all | |
| 24 | - the tags you asked it to add. This bug was the result of nothing more | |
| 25 | - dignified than a typographical error on my part. It has now been fixed. | |
| 26 | - | |
| 27 | -* MORE INFORMATION AVAILABLE WHEN FEEDWORDPRESS CAN'T FIND A FEED: When | |
| 28 | - you enter a URL for a new syndication source, FeedWordPress uses a | |
| 29 | - simple feed-finding algorithm (originally based on Mark Pilgrim's | |
| 30 | - Universal Feed Finder) to try to determine whether the URL is the URL | |
| 31 | - for a feed, or, if the URL points to an ordinary website rather than to | |
| 32 | - a feed, whether there is a feed for that website. All well and good, but | |
| 33 | - if FeedWordPress failed to find a feed, for whatever reason, it would | |
| 34 | - typically return nothing more than a nasty little note to the effect of | |
| 35 | - "no feed found," without any explanation of what went wrong. | |
| 36 | - FeedWordPress now keeps track of error conditions from the HTTP | |
| 37 | - requests that it uses in the course of looking for the feed, and so may | |
| 38 | - be able to give you a bit more information about the nature of the | |
| 39 | - problem if something goes wrong. | |
| 40 | - | |
| 41 | - | |
| 42 | -Changes from 2008.1101 to 2008.1105 | |
| 43 | - | |
| 44 | -* INTERFACE RESTRUCTURING AND SYNDICATION --> AUTHORS PAGE: As a first | |
| 45 | - step towards modularizing and better organizing the user interface, a | |
| 46 | - new "Authors" subpage has been created under the Syndication menu, which | |
| 47 | - controls settings for syndicated authors, both at the global default | |
| 48 | - level and at level of individual syndicated feeds. | |
| 49 | - | |
| 50 | -* BUG RELATED TO THE ATTRIBUTION OF POSTS TO THE WRONG AUTHOR FIXED: Some | |
| 51 | - users encountered an issue in which posts by different authors on | |
| 52 | - different blogs -- especially blogs generated by Blogger -- were | |
| 53 | - mistakenly attributed to a single author. The problem was caused by the | |
| 54 | - way in which FeedWordPress matches syndicated authors to user accounts | |
| 55 | - in the WordPress database: normally, if two feeds each list an author | |
| 56 | - with the same e-mail address, they are counted as being the same person. | |
| 57 | - Normally this works well, but it creates an issue in cases where | |
| 58 | - blogging software assigns a single anonymous e-mail address to users who | |
| 59 | - do not want their real e-mail address published. This is, for example, | |
| 60 | - what Blogger does (by giving all users a default e-mail address of | |
| 61 | - <noreply@blogger.com> if they don't want their own e-mail address | |
| 62 | - listed). FeedWordPress now allows the user to correct for this problem | |
| 63 | - with a couple of new settings under **Syndication --> Authors**, which | |
| 64 | - allow users to turn off e-mail based author matching for particular | |
| 65 | - addresses, or, if desired, to turn it off entirely. By default, e-mail | |
| 66 | - based author matching is still turned on, but disabled for a list of | |
| 67 | - known generic e-mail addresses. Right now, the "list" consists entirely | |
| 68 | - of <noreply@blogger.com>; if you know other addresses that should be | |
| 69 | - added, please [contact me](http://radgeek.com/contact) to let me know. | |
| 70 | - | |
| 71 | - Please note that if you have already encountered this issue on your | |
| 72 | - blog, upgrading FeedWordPress will prevent it from re-occurring in the | |
| 73 | - future, but you still need to do two other things to fix the existing | |
| 74 | - problem on your blog. | |
| 75 | - | |
| 76 | - First, for each feed where posts have been mis-attributed, you need to | |
| 77 | - change the existing author mapping rules to re-map a a syndicated | |
| 78 | - author's name to the proper target account. Go to **Syndication --> | |
| 79 | - Authors**, select the feed you want to change from the drop-down list, | |
| 80 | - and then change the settings under the "Syndicated Authors" section. | |
| 81 | - (You will probably need to select "will be assigned to a new user..." to | |
| 82 | - create a new user account with the appropriate name.) | |
| 83 | - | |
| 84 | - Second, for each feed where posts have been mis-attributed, you need to | |
| 85 | - re-assign already-syndicated posts that were mis-attributed to the | |
| 86 | - correct author. You can do that from **Syndication --> Authors** by | |
| 87 | - using the author re-assignment feature, described below. | |
| 88 | - | |
| 89 | -* AUTHOR RE-ASSIGNMENT FOR A PARTICULAR FEED: The author settings page | |
| 90 | - for each syndicated feed, under **Syndication --> Authors**, now | |
| 91 | - includes an section titled "Fixing mis-matched authors," which provides | |
| 92 | - an interface for re-assigning or deleting all posts attributed to a | |
| 93 | - particular author on a particular feed. | |
| 94 | - | |
| 95 | -* SUPPORT FOR `<atom:source>` ELEMENT IN SYNDICATED FEEDS: Some feeds | |
| 96 | - (for example, those produced by FeedWordPress) aggregate content from | |
| 97 | - several different sources, and include information about the original | |
| 98 | - source of the post in an `<atom:source>` element. A new setting under | |
| 99 | - **Syndication --> Options** allows you to control what FeedWordPress | |
| 100 | - will report as the source of posts syndicated from aggregator feeds in | |
| 101 | - your templates and feeds: you can have FeedWordPress report that the | |
| 102 | - source of a post is the aggregator feed itself, or you can have it | |
| 103 | - report that the source of a post is the original source that the | |
| 104 | - aggregator originally syndicated the post from. | |
| 105 | - | |
| 106 | - By default, FeedWordPress will report the aggregator, not the original | |
| 107 | - source, as the source of a syndicated item. | |
| 108 | - | |
| 109 | -* LOAD BALANCING AND TIME LIMITING FEATURES FOR UPDATES: Some users have | |
| 110 | - encountered issues due to running up against PHP execution time limits | |
| 111 | - during the process of updating large syndicated feeds, or a very large | |
| 112 | - set of syndicated feeds. FeedWordPress now has a feature that allows you | |
| 113 | - to limit the total amount of time spent updating a feed, through the | |
| 114 | - "Time limit on updates" setting under **Syndication --> Options**. By | |
| 115 | - turning on this setting and adjusting the time limit to a low enough | |
| 116 | - figure to avoid your PHP installation's time-out setting. (PHP execution | |
| 117 | - time limits are usually in the vicinity of 30 seconds, so an update | |
| 118 | - time limit of 25 seconds or so should provide plenty of time for updates | |
| 119 | - while allowing a cushion of time for other, non-update-related functions | |
| 120 | - to do their work.) | |
| 121 | - | |
| 122 | - If feed updates are interrupted by the time limit, FeedWordPress uses | |
| 123 | - some simple load balancing features to make sure that updates to other | |
| 124 | - feeds will not be blocked by the time-hogging feed, and will also make | |
| 125 | - sure that when the interrupted update is resumed, FeedWordPress will | |
| 126 | - skip ahead to resume processing items at the point at which it was | |
| 127 | - interrupted last time, so that posts further down in the feed will | |
| 128 | - eventually get processed, and not get blocked by the amount of time it | |
| 129 | - takes to process the items higher up in the feed. | |
| 130 | - | |
| 131 | -* `guid` INDEX CREATION BUTTON: FeedWordPress frequently issues queries on | |
| 132 | - the `guid` column of the WordPress posts database (since it uses post | |
| 133 | - guid URIs to keep track of which posts it has syndicated). In very large | |
| 134 | - FeedWordPress installations, you can often significantly improve | |
| 135 | - performance by creating a database index on the `guid` column, but | |
| 136 | - normally you would need to poke around with MySQL or a tool like | |
| 137 | - phpMyAdmin to do this. FeedWordPress can now save you the trouble: to | |
| 138 | - create an index on the `guid` column, just go to | |
| 139 | - **Syndication --> Options**, and mash the button at the bottom of the | |
| 140 | - "Back End" section. | |
| 141 | - | |
| 142 | -Changes from 2008.1030 to 2008.1101 | |
| 143 | - | |
| 144 | -* INTERFACE BUG THAT PREVENTED ADDING NEW SITES FIXED: The UI reforms in | |
| 145 | - FWP 2008.1030 unintentionally introduced a bug that prevents clean | |
| 146 | - installations of FeedWordPress from providing an input box for adding | |
| 147 | - new feeds to the list of syndicated feeds. This bug has been fixed. | |
| 148 | - | |
| 149 | -Changes from 0.993 to 2008.1030 | |
| 150 | - | |
| 151 | -* WORDPRESS 2.6 COMPATIBILITY: FeedWordPress should now be compatible with | |
| 152 | - WordPress 2.6, and should work more or less seamlessly with the new post | |
| 153 | - revision system. A bug which caused multiple new revisions to be created | |
| 154 | - for posts on certain feeds, regardless of whether or not the item had | |
| 155 | - been updated, has been fixed. | |
| 156 | - | |
| 157 | -* INTERFACE IMPROVEMENTS: The user interface has been substantially | |
| 158 | - restyled to fit in better with the visual style of WordPress 2.5 and | |
| 159 | - 2.6. | |
| 160 | - | |
| 161 | -* YOUTUBE BUG FIXED: POSTS SYNDICATED THROUGH AN AUTOMATIC UPDATE ARE NO | |
| 162 | - LONGER STRIPPED OF `<OBJECT>` TAGS AND CERTAIN OTHER HTML ELEMENTS: Due | |
| 163 | - to the way that some versions of WordPress process posts that are | |
| 164 | - inserted into the database when no user is logged in, many users | |
| 165 | - experienced an issue where YouTube videos and other content using the | |
| 166 | - HTML `<object>` tag would be stripped out of posts that were syndicated | |
| 167 | - during an automatic update. (Posts that were syndicated through manual | |
| 168 | - updates from within the WordPress Dashboard were not affected, because | |
| 169 | - the issue does not arise when an update is executed under a logged-in | |
| 170 | - administrator's credentials.) This bug has now been fixed; YouTube | |
| 171 | - videos and other content using `<object>` tags should now appear | |
| 172 | - properly in syndicated posts, regardless of the way in which the post | |
| 173 | - was syndicated. | |
| 174 | - | |
| 175 | -* AJAX BUGS FIXED: Bugs which blocked the normal operation of WordPress | |
| 176 | - 2.5's AJAX interface elements when FeedWordPress was activated have been | |
| 177 | - fixed. | |
| 178 | - | |
| 179 | -* TAG SUPPORT: A couple of features have been introduced to take advantage | |
| 180 | - of the tagging features in WordPress 2.3.x, 2.5.x, and 2.6.x. Now, when | |
| 181 | - unfamiliar categories are encountered for posts on a feed, you can | |
| 182 | - choose for FeedWordPress (1) to drop the category; (2) to drop the | |
| 183 | - category and to filter out any post that does not match at least one | |
| 184 | - familiar category; (3) to create a new category with that name, or, | |
| 185 | - now, you can also have FeedWordPress (4) create a new *tag* with that | |
| 186 | - name. This option can be set site-wide under Syndication --> Options, | |
| 187 | - or it can be set on a feed-by-feed basis in a feed's Edit screen. | |
| 188 | - | |
| 189 | - In addition, you can now set particular tags to apply to all incoming | |
| 190 | - syndicated posts, under Syndication --> Options, or you can set tags | |
| 191 | - to apply to all incoming syndicated posts from a particular feed in that | |
| 192 | - feed's Edit screen. | |
| 193 | - | |
| 194 | -* FORMATTING FILTERS: There is a new option available under Syndication -> | |
| 195 | - Options which allows users to choose whether or not to expose syndicated | |
| 196 | - posts to being altered by formatting filters. By default, FeedWordPress | |
| 197 | - has always protected syndicated posts (which are already in display-ready | |
| 198 | - HTML when they are syndicated) from being reformatted by formatting | |
| 199 | - filters. However, this approach means that certain plugins which depend | |
| 200 | - on formatting filters (for example, to add "Share This" bars or relevant | |
| 201 | - links to the end of a post) are blocked from working on any syndicated | |
| 202 | - posts. If you want to use one of these plugins together with | |
| 203 | - FeedWordPress, you can now do so by changing the "Formatting Filters" | |
| 204 | - setting from "Protect" to "Expose." | |
| 205 | - | |
| 206 | -* `<atom:source>` ELEMENTS NOW INCLUDED IN ATOM FEED: Atom 1.0 provides | |
| 207 | - a standard method for aggregators to indicate information about the original source of | |
| 208 | - a syndicated post, using the `<atom:source>` element. FeedWordPress now | |
| 209 | - introduces standard `<atom:source>` elements including the title, homepage, and | |
| 210 | - feed URI of the source from which a syndicated post was syndicated. Cf. | |
| 211 | - <http://www.atomenabled.org/developers/syndication/atom-format-spec.php#element.source> | |
| 212 | - | |
| 213 | -* MODULARIZATION OF CODE: The code for different elements of FeedWordPress | |
| 214 | - has been broken out into several modules for easier inspection, | |
| 215 | - documentation, and maintenance of the code. | |
| 216 | - | |
| 217 | -* VERSIONING SCHEME CHANGED: FeedWordPress's feature set has proven stable | |
| 218 | - enough that it can now be removed from beta status; a good thing, since | |
| 219 | - I was very quickly running out of version numbers to use. New releases | |
| 220 | - of FeedWordPress will have version numbers based on the date of their | |
| 221 | - release. | |
| 222 | - | |
| 223 | -Changes from 0.992 to 0.993 | |
| 224 | - | |
| 225 | -* WORDPRESS 2.5.1 COMPATIBILITY: FeedWordPress should now be compatible | |
| 226 | - with WordPress 2.5.1. | |
| 227 | - | |
| 228 | -* WORDPRESS 2.5 INTERFACE IMPROVEMENTS: FeedWordPress's Dashboard | |
| 229 | - interface has undergone several cosmetic changes that should help it | |
| 230 | - integrate better with the WordPress Dashboard interface in WordPress | |
| 231 | - version 2.5.x. | |
| 232 | - | |
| 233 | -* SYNDICATED POSTS CAN BE MARKED AS "PENDING REVIEW": WordPress 2.3 users | |
| 234 | - can now take advantage of WordPress's new "Pending Review" features for | |
| 235 | - incoming syndicated posts. Posts marked as "Pending Review" are not | |
| 236 | - published immediately, but are marked as ready to be reviewed by an | |
| 237 | - Administrator or Editor, who can then choose to publish the post or | |
| 238 | - hold it back. If you want to review syndicated posts from a particular | |
| 239 | - feed, or from all feeds, before they are posted, then use | |
| 240 | - Syndication --> Syndicated Sites --> Edit or Syndication --> Options to | |
| 241 | - change the settings for handling new posts. | |
| 242 | - | |
| 243 | -* AWARE OF NEW URI FOR del.icio.us FEEDS: Previous releases of | |
| 244 | - FeedWordPress already automatically split del.icio.us tags up | |
| 245 | - appropriately appropriately when generating categories. (del.icio.us | |
| 246 | - feeds smoosh all the tags into a single `<dc:subject>` element, | |
| 247 | - separated by spaces; FeedWordPress un-smooshes them into multiple | |
| 248 | - categories by separating them at whitespace.) Unfortunately, del.icio.us | |
| 249 | - recently broke the existing behavior by changing host names for their | |
| 250 | - feeds from del.icio.us to feeds.delicious.com. Version 0.993 accounts | |
| 251 | - for the new host name and un-breaks the tag splitting. | |
| 252 | - | |
| 253 | 4 | Changes from 0.991 to 0.992 |
| 254 | 5 | --------------------------- |
| 255 | 6 | * AUTHOR RE-MAPPING: FeedWordPress now offers considerable control over |
| 256 | 7 | how author names on a feed are translated into usernames within the |
| @@ -286,9 +32,9 @@ | ||
| 286 | 32 | has, hopefully, been resolved, by correcting for the bug in WordPress. |
| 287 | 33 | |
| 288 | 34 | Changes from 0.99 to 0.991 |
| 289 | 35 | -------------------------- |
| 290 | -* WORDPRESS MU COMPATIBILITY: FeedWordPress should now be compatible with | |
| 36 | +* WORDPRESS MU COMPATABILITY: FeedWordPress should now be compatible with | |
| 291 | 37 | recent releases of WordPress MU. Once FeedWordPress is made available |
| 292 | 38 | as a plugin, each individual blog can choose to activate FeedWordPress |
| 293 | 39 | and syndicate content from its own set of contributors. |
| 294 | 40 | |
| @@ -305,12 +51,12 @@ | ||
| 305 | 51 | authors whose names included international characters. This |
| 306 | 52 | incompatability has now been fixed; hopefully, authors with |
| 307 | 53 | international characters in their names should now be handled properly. |
| 308 | 54 | |
| 309 | -* `<media:content>` BUG IN MAGPIERSS FIXED: A bug in MagpieRSS's handling | |
| 310 | - of namespaced elements has been fixed. Among other things, this bug | |
| 311 | - caused items containing a Yahoo MediaRSS `<media:content>` element (such | |
| 312 | - 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 | |
| 313 | 59 | incorrectly, with only a capital "A" where the content of the post |
| 314 | 60 | should have been. Feeds containing `<media:content>` elements should now |
| 315 | 61 | be syndicated correctly. |
| 316 | 62 | |
| @@ -686,10 +432,9 @@ | ||
| 686 | 432 | into the WordPress database so that (among other things) that post |
| 687 | 433 | will have its enclosure listed in your blog's RSS 2 newsfeed. |
| 688 | 434 | |
| 689 | 435 | Note that enclosure support requires using the optional MagpieRSS |
| 690 | - upgrade (i.e., replacing your `wp-includes/rss-functions.php` with | |
| 691 | - `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) | |
| 692 | 437 | |
| 693 | 438 | * FEATURE: for completeness's sake, there is now a feed setting, |
| 694 | 439 | `hardcode url`, that allows you to set the URI for the front page |
| 695 | 440 | of a contributor's website manually (that is, prevent it from being |
