| @@ -1,7 +1,107 @@ | ||
| 1 | 1 | FeedWordPress Change Log |
| 2 | 2 | ======================== |
| 3 | 3 | |
| 4 | +Changes from 0.992 to 0.993 | |
| 5 | +--------------------------- | |
| 6 | + | |
| 7 | +* WORDPRESS 2.5.1 COMPATIBILITY: FeedWordPress should now be compatible | |
| 8 | + with WordPress 2.5.1. | |
| 9 | + | |
| 10 | +* WORDPRESS 2.5 INTERFACE IMPROVEMENTS: FeedWordPress's Dashboard | |
| 11 | + interface has undergone several cosmetic changes that should help it | |
| 12 | + integrate better with the WordPress Dashboard interface in WordPress | |
| 13 | + version 2.5.x. | |
| 14 | + | |
| 15 | +* SYNDICATED POSTS CAN BE MARKED AS "PENDING REVIEW": WordPress 2.3 users | |
| 16 | + can now take advantage of WordPress's new "Pending Review" features for | |
| 17 | + incoming syndicated posts. Posts marked as "Pending Review" are not | |
| 18 | + published immediately, but are marked as ready to be reviewed by an | |
| 19 | + Administrator or Editor, who can then choose to publish the post or | |
| 20 | + hold it back. If you want to review syndicated posts from a particular | |
| 21 | + feed, or from all feeds, before they are posted, then use | |
| 22 | + Syndication --> Syndicated Sites --> Edit or Syndication --> Options to | |
| 23 | + change the settings for handling new posts. | |
| 24 | + | |
| 25 | +* AWARE OF NEW URI FOR del.icio.us FEEDS: Previous releases of | |
| 26 | + FeedWordPress already automatically split del.icio.us tags up | |
| 27 | + appropriately appropriately when generating categories. (del.icio.us | |
| 28 | + feeds smoosh all the tags into a single `<dc:subject>` element, | |
| 29 | + separated by spaces; FeedWordPress un-smooshes them into multiple | |
| 30 | + categories by separating them at whitespace.) Unfortunately, del.icio.us | |
| 31 | + recently broke the existing behavior by changing host names for their | |
| 32 | + feeds from del.icio.us to feeds.delicious.com. Version 0.993 accounts | |
| 33 | + for the new host name and un-breaks the tag splitting. | |
| 34 | + | |
| 35 | +Changes from 0.991 to 0.992 | |
| 36 | +--------------------------- | |
| 37 | +* AUTHOR RE-MAPPING: FeedWordPress now offers considerable control over | |
| 38 | + how author names on a feed are translated into usernames within the | |
| 39 | + WordPress database. When a post by an unrecognized author comes in, | |
| 40 | + Administrators can now specify any username as the default username to | |
| 41 | + assign the post to by setting the option in Syndication --> Options | |
| 42 | + (formerly FeedWordPress only allowed you to assign such posts to user | |
| 43 | + #1, the site administrator). Administrators can also create re-mapping | |
| 44 | + rules for particular feeds (under Syndication --> Syndicated Sites --> | |
| 45 | + Edit), so that (for example) any posts attributed to "Administrator" | |
| 46 | + on the feed <http://praxeology.net/blog/feed/> will be assigned to | |
| 47 | + a user named "Roderick T. Long," rather than a user named | |
| 48 | + "Administrator." These settings also allow administrators to filter out | |
| 49 | + posts by particular users, and to control what will happen when | |
| 50 | + FeedWordPress encounters a post by an unrecognized user on that | |
| 51 | + particular feed. | |
| 52 | + | |
| 53 | +* BUG RELATED TO URIS CONTAINING AMPERSAND CHARACTERS FIXED: A bug in | |
| 54 | + WordPress 2.x's handling of URIs in Blogroll links created problems for | |
| 55 | + updating any feeds whose URIs included an ampersand character, such as | |
| 56 | + Google News RSS feeds and other feeds that have multiple parameters | |
| 57 | + passed through HTTP GET. If you experienced this bug, the most likely | |
| 58 | + effect was that FeedWordPress simply would not import new posts from a | |
| 59 | + feed when instructred to do so, returning a "0 new posts" response. In | |
| 60 | + other cases, it might lead to unpredictable results from feed updates, | |
| 61 | + such as importing posts which were not contained in the feed being | |
| 62 | + syndicated, but which did appear elsewhere on the same website. This bug | |
| 63 | + has, hopefully, been resolved, by correcting for the bug in WordPress. | |
| 64 | + | |
| 65 | +Changes from 0.99 to 0.991 | |
| 66 | +-------------------------- | |
| 67 | +* WORDPRESS MU COMPATABILITY: FeedWordPress should now be compatible with | |
| 68 | + recent releases of WordPress MU. Once FeedWordPress is made available | |
| 69 | + as a plugin, each individual blog can choose to activate FeedWordPress | |
| 70 | + and syndicate content from its own set of contributors. | |
| 71 | + | |
| 72 | +* DISPLAY OF MAGPIE WARNINGS: A number of MagpieRSS warnings or error | |
| 73 | + messages that were displayed when performing an automatic update are | |
| 74 | + no longer displayed, unless debugging parameters have been explicitly | |
| 75 | + enabled. | |
| 76 | + | |
| 77 | +* BUG RELATED TO INTERNATIONAL CHARACTERS IN AUTHOR NAMES FIXED: Due to a | |
| 78 | + subtle incompatability between the way that FeedWordPress generated new | |
| 79 | + user information, and the way that WordPress 2.0 and later added new | |
| 80 | + authors to the database, FeedWordPress might end up creating duplicate | |
| 81 | + authors, or throwing a critical error message, when it encountered | |
| 82 | + authors whose names included international characters. This | |
| 83 | + incompatability has now been fixed; hopefully, authors with | |
| 84 | + international characters in their names should now be handled properly. | |
| 85 | + | |
| 86 | +* media:content BUG IN MAGPIERSS FIXED: A bug in MagpieRSS's handling of | |
| 87 | + namespaced elements has been fixed. Among other things, this bug caused | |
| 88 | + items containing a Yahoo MediaRSS `<media:content>` element (such as | |
| 89 | + many of the feeds produced by wordpress.com) to be represented | |
| 90 | + incorrectly, with only a capital "A" where the content of the post | |
| 91 | + should have been. Feeds containing `<media:content>` elements should now | |
| 92 | + be syndicated correctly. | |
| 93 | + | |
| 94 | +* update_feedwordpress PARAMETER: You can now use an HTTP GET parameter | |
| 95 | + (`update_feedwordpress=1`) to request that FeedWordPress poll its feeds | |
| 96 | + for updates. When used together with a crontab or other means of | |
| 97 | + scheduling tasks, this means that you can keep your blog automatically | |
| 98 | + updated on a regular schedule, even if you do not choose to use the | |
| 99 | + cron-less automatic updates option. | |
| 100 | + | |
| 101 | +* Some minor interface-related bugs were also fixed. | |
| 102 | + | |
| 103 | + | |
| 4 | 104 | Changes from 0.981 to 0.99 |
| 5 | 105 | -------------------------- |
| 6 | 106 | Version 0.99 adds several significant new features, fixes some bugs, and |
| 7 | 107 | provides compatability with WordPress 2.2.x and 2.3.x. |
