| @@ -1,190 +1,7 @@ | ||
| 1 | 1 | FeedWordPress Change Log |
| 2 | 2 | ======================== |
| 3 | 3 | |
| 4 | -Changes from 2008.1030 to 2008.1101 | |
| 5 | - | |
| 6 | -* INTERFACE BUG THAT PREVENTED ADDING NEW SITES FIXED: The UI reforms in | |
| 7 | - FWP 2008.1030 unintentionally introduced a bug that prevents clean | |
| 8 | - installations of FeedWordPress from providing an input box for adding | |
| 9 | - new feeds to the list of syndicated feeds. This bug has been fixed. | |
| 10 | - | |
| 11 | -Changes from 0.993 to 2008.1030 | |
| 12 | - | |
| 13 | -* WORDPRESS 2.6 COMPATABILITY: FeedWordPress should now be compatible with | |
| 14 | - WordPress 2.6, and should work more or less seamlessly with the new post | |
| 15 | - revision system. A bug which caused multiple new revisions to be created | |
| 16 | - for posts on certain feeds, regardless of whether or not the item had | |
| 17 | - been updated, has been fixed. | |
| 18 | - | |
| 19 | -* INTERFACE IMPROVEMENTS: The user interface has been substantially | |
| 20 | - restyled to fit in better with the visual style of WordPress 2.5 and | |
| 21 | - 2.6. | |
| 22 | - | |
| 23 | -* YOUTUBE BUG FIXED: POSTS SYNDICATED THROUGH AN AUTOMATIC UPDATE ARE NO | |
| 24 | - LONGER STRIPPED OF `<OBJECT>` TAGS AND CERTAIN OTHER HTML ELEMENTS: Due | |
| 25 | - to the way that some versions of WordPress process posts that are | |
| 26 | - inserted into the database when no user is logged in, many users | |
| 27 | - experienced an issue where YouTube videos and other content using the | |
| 28 | - HTML `<object>` tag would be stripped out of posts that were syndicated | |
| 29 | - during an automatic update. (Posts that were syndicated through manual | |
| 30 | - updates from within the WordPress Dashboard were not affected, because | |
| 31 | - the issue does not arise when an update is executed under a logged-in | |
| 32 | - administrator's credentials.) This bug has now been fixed; YouTube | |
| 33 | - videos and other content using `<object>` tags should now appear | |
| 34 | - properly in syndicated posts, regardless of the way in which the post | |
| 35 | - was syndicated. | |
| 36 | - | |
| 37 | -* AJAX BUGS FIXED: Bugs which blocked the normal operation of WordPress | |
| 38 | - 2.5's AJAX interface elements when FeedWordPress was activated have been | |
| 39 | - fixed. | |
| 40 | - | |
| 41 | -* TAG SUPPORT: A couple of features have been introduced to take advantage | |
| 42 | - of the tagging features in WordPress 2.3.x, 2.5.x, and 2.6.x. Now, when | |
| 43 | - unfamiliar categories are encountered for posts on a feed, you can | |
| 44 | - choose for FeedWordPress (1) to drop the category; (2) to drop the | |
| 45 | - category and to filter out any post that does not match at least one | |
| 46 | - familiar category; (3) to create a new category with that name, or, | |
| 47 | - now, you can also have FeedWordPress (4) create a new *tag* with that | |
| 48 | - name. This option can be set site-wide under Syndication --> Options, | |
| 49 | - or it can be set on a feed-by-feed basis in a feed's Edit screen. | |
| 50 | - | |
| 51 | - In addition, you can now set particular tags to apply to all incoming | |
| 52 | - syndicated posts, under Syndication --> Options, or you can set tags | |
| 53 | - to apply to all incoming syndicated posts from a particular feed in that | |
| 54 | - feed's Edit screen. | |
| 55 | - | |
| 56 | -* FORMATTING FILTERS: There is a new option available under Syndication -> | |
| 57 | - Options which allows users to choose whether or not to expose syndicated | |
| 58 | - posts to being altered by formatting filters. By default, FeedWordPress | |
| 59 | - has always protected syndicated posts (which are already in display-ready | |
| 60 | - HTML when they are syndicated) from being reformatted by formatting | |
| 61 | - filters. However, this approach means that certain plugins which depend | |
| 62 | - on formatting filters (for example, to add "Share This" bars or relevant | |
| 63 | - links to the end of a post) are blocked from working on any syndicated | |
| 64 | - posts. If you want to use one of these plugins together with | |
| 65 | - FeedWordPress, you can now do so by changing the "Formatting Filters" | |
| 66 | - setting from "Protect" to "Expose." | |
| 67 | - | |
| 68 | -* **`<atom:source>` ELEMENTS NOW INCLUDED IN ATOM FEED:** Atom 1.0 provides | |
| 69 | - a standard method for aggregators to indicate information about the original source of | |
| 70 | - a syndicated post, using the `<atom:source>` element. FeedWordPress now | |
| 71 | - introduces standard `<atom:source>` elements including the title, homepage, and | |
| 72 | - feed URI of the source from which a syndicated post was syndicated. Cf. | |
| 73 | - <http://www.atomenabled.org/developers/syndication/atom-format-spec.php#element.source> | |
| 74 | - | |
| 75 | -* MODULARIZATION OF CODE: The code for different elements of FeedWordPress | |
| 76 | - has been broken out into several modules for easier inspection, | |
| 77 | - documentation, and maintenance of the code. | |
| 78 | - | |
| 79 | -* VERSIONING SCHEME CHANGED: FeedWordPress's feature set has proven stable | |
| 80 | - enough that it can now be removed from beta status; a good thing, since | |
| 81 | - I was very quickly running out of version numbers to use. New releases | |
| 82 | - of FeedWordPress will have version numbers based on the date of their | |
| 83 | - release. | |
| 84 | - | |
| 85 | -Changes from 0.992 to 0.993 | |
| 86 | - | |
| 87 | -* WORDPRESS 2.5.1 COMPATIBILITY: FeedWordPress should now be compatible | |
| 88 | - with WordPress 2.5.1. | |
| 89 | - | |
| 90 | -* WORDPRESS 2.5 INTERFACE IMPROVEMENTS: FeedWordPress's Dashboard | |
| 91 | - interface has undergone several cosmetic changes that should help it | |
| 92 | - integrate better with the WordPress Dashboard interface in WordPress | |
| 93 | - version 2.5.x. | |
| 94 | - | |
| 95 | -* SYNDICATED POSTS CAN BE MARKED AS "PENDING REVIEW": WordPress 2.3 users | |
| 96 | - can now take advantage of WordPress's new "Pending Review" features for | |
| 97 | - incoming syndicated posts. Posts marked as "Pending Review" are not | |
| 98 | - published immediately, but are marked as ready to be reviewed by an | |
| 99 | - Administrator or Editor, who can then choose to publish the post or | |
| 100 | - hold it back. If you want to review syndicated posts from a particular | |
| 101 | - feed, or from all feeds, before they are posted, then use | |
| 102 | - Syndication --> Syndicated Sites --> Edit or Syndication --> Options to | |
| 103 | - change the settings for handling new posts. | |
| 104 | - | |
| 105 | -* AWARE OF NEW URI FOR del.icio.us FEEDS: Previous releases of | |
| 106 | - FeedWordPress already automatically split del.icio.us tags up | |
| 107 | - appropriately appropriately when generating categories. (del.icio.us | |
| 108 | - feeds smoosh all the tags into a single `<dc:subject>` element, | |
| 109 | - separated by spaces; FeedWordPress un-smooshes them into multiple | |
| 110 | - categories by separating them at whitespace.) Unfortunately, del.icio.us | |
| 111 | - recently broke the existing behavior by changing host names for their | |
| 112 | - feeds from del.icio.us to feeds.delicious.com. Version 0.993 accounts | |
| 113 | - for the new host name and un-breaks the tag splitting. | |
| 114 | - | |
| 115 | -Changes from 0.991 to 0.992 | |
| 116 | -* AUTHOR RE-MAPPING: FeedWordPress now offers considerable control over | |
| 117 | - how author names on a feed are translated into usernames within the | |
| 118 | - WordPress database. When a post by an unrecognized author comes in, | |
| 119 | - Administrators can now specify any username as the default username to | |
| 120 | - assign the post to by setting the option in Syndication --> Options | |
| 121 | - (formerly FeedWordPress only allowed you to assign such posts to user | |
| 122 | - #1, the site administrator). Administrators can also create re-mapping | |
| 123 | - rules for particular feeds (under Syndication --> Syndicated Sites --> | |
| 124 | - Edit), so that (for example) any posts attributed to "Administrator" | |
| 125 | - on the feed <http://praxeology.net/blog/feed/> will be assigned to | |
| 126 | - a user named "Roderick T. Long," rather than a user named | |
| 127 | - "Administrator." These settings also allow administrators to filter out | |
| 128 | - posts by particular users, and to control what will happen when | |
| 129 | - FeedWordPress encounters a post by an unrecognized user on that | |
| 130 | - particular feed. | |
| 131 | - | |
| 132 | -* BUG RELATED TO URIS CONTAINING AMPERSAND CHARACTERS FIXED: A bug in | |
| 133 | - WordPress 2.x's handling of URIs in Blogroll links created problems for | |
| 134 | - updating any feeds whose URIs included an ampersand character, such as | |
| 135 | - Google News RSS feeds and other feeds that have multiple parameters | |
| 136 | - passed through HTTP GET. If you experienced this bug, the most likely | |
| 137 | - effect was that FeedWordPress simply would not import new posts from a | |
| 138 | - feed when instructred to do so, returning a "0 new posts" response. In | |
| 139 | - other cases, it might lead to unpredictable results from feed updates, | |
| 140 | - such as importing posts which were not contained in the feed being | |
| 141 | - syndicated, but which did appear elsewhere on the same website. This bug | |
| 142 | - has, hopefully, been resolved, by correcting for the bug in WordPress. | |
| 143 | - | |
| 144 | -Changes from 0.99 to 0.991 | |
| 145 | -* WORDPRESS MU COMPATABILITY: FeedWordPress should now be compatible with | |
| 146 | - recent releases of WordPress MU. Once FeedWordPress is made available | |
| 147 | - as a plugin, each individual blog can choose to activate FeedWordPress | |
| 148 | - and syndicate content from its own set of contributors. | |
| 149 | - | |
| 150 | -* DISPLAY OF MAGPIE WARNINGS: A number of MagpieRSS warnings or error | |
| 151 | - messages that were displayed when performing an automatic update are | |
| 152 | - no longer displayed, unless debugging parameters have been explicitly | |
| 153 | - enabled. | |
| 154 | - | |
| 155 | -* BUG RELATED TO INTERNATIONAL CHARACTERS IN AUTHOR NAMES FIXED: Due to a | |
| 156 | - subtle incompatability between the way that FeedWordPress generated new | |
| 157 | - user information, and the way that WordPress 2.0 and later added new | |
| 158 | - authors to the database, FeedWordPress might end up creating duplicate | |
| 159 | - authors, or throwing a critical error message, when it encountered | |
| 160 | - authors whose names included international characters. This | |
| 161 | - incompatability has now been fixed; hopefully, authors with | |
| 162 | - international characters in their names should now be handled properly. | |
| 163 | - | |
| 164 | -* media:content BUG IN MAGPIERSS FIXED: A bug in MagpieRSS's handling of | |
| 165 | - namespaced elements has been fixed. Among other things, this bug caused | |
| 166 | - items containing a Yahoo MediaRSS `<media:content>` element (such as | |
| 167 | - many of the feeds produced by wordpress.com) to be represented | |
| 168 | - incorrectly, with only a capital "A" where the content of the post | |
| 169 | - should have been. Feeds containing `<media:content>` elements should now | |
| 170 | - be syndicated correctly. | |
| 171 | - | |
| 172 | -* update_feedwordpress PARAMETER: You can now use an HTTP GET parameter | |
| 173 | - (`update_feedwordpress=1`) to request that FeedWordPress poll its feeds | |
| 174 | - for updates. When used together with a crontab or other means of | |
| 175 | - scheduling tasks, this means that you can keep your blog automatically | |
| 176 | - updated on a regular schedule, even if you do not choose to use the | |
| 177 | - cron-less automatic updates option. | |
| 178 | - | |
| 179 | -* Some minor interface-related bugs were also fixed. | |
| 180 | - | |
| 181 | - | |
| 182 | 4 | Changes from 0.981 to 0.99 |
| 183 | 5 | -------------------------- |
| 184 | 6 | Version 0.99 adds several significant new features, fixes some bugs, and |
| 185 | 7 | provides compatability with WordPress 2.2.x and 2.3.x. |
