| @@ -1,11 +1,120 @@ | ||
| 1 | 1 | FeedWordPress Change Log |
| 2 | 2 | ======================== |
| 3 | 3 | |
| 4 | +Changes from 2008.1101 to 2008.1105 | |
| 5 | +----------------------------------- | |
| 6 | + | |
| 7 | +* INTERFACE RESTRUCTURING AND SYNDICATION --> AUTHORS PAGE: As a first | |
| 8 | + step towards modularizing and better organizing the user interface, a | |
| 9 | + new "Authors" subpage has been created under the Syndication menu, which | |
| 10 | + controls settings for syndicated authors, both at the global default | |
| 11 | + level and at level of individual syndicated feeds. | |
| 12 | + | |
| 13 | +* BUG RELATED TO THE ATTRIBUTION OF POSTS TO THE WRONG AUTHOR FIXED: Some | |
| 14 | + users encountered an issue in which posts by different authors on | |
| 15 | + different blogs -- especially blogs generated by Blogger -- were | |
| 16 | + mistakenly attributed to a single author. The problem was caused by the | |
| 17 | + way in which FeedWordPress matches syndicated authors to user accounts | |
| 18 | + in the WordPress database: normally, if two feeds each list an author | |
| 19 | + with the same e-mail address, they are counted as being the same person. | |
| 20 | + Normally this works well, but it creates an issue in cases where | |
| 21 | + blogging software assigns a single anonymous e-mail address to users who | |
| 22 | + do not want their real e-mail address published. This is, for example, | |
| 23 | + what Blogger does (by giving all users a default e-mail address of | |
| 24 | + <noreply@blogger.com> if they don't want their own e-mail address | |
| 25 | + listed). FeedWordPress now allows the user to correct for this problem | |
| 26 | + with a couple of new settings under **Syndication --> Authors**, which | |
| 27 | + allow users to turn off e-mail based author matching for particular | |
| 28 | + addresses, or, if desired, to turn it off entirely. By default, e-mail | |
| 29 | + based author matching is still turned on, but disabled for a list of | |
| 30 | + known generic e-mail addresses. Right now, the "list" consists entirely | |
| 31 | + of <noreply@blogger.com>; if you know other addresses that should be | |
| 32 | + added, please [contact me](http://radgeek.com/contact) to let me know. | |
| 33 | + | |
| 34 | + Please note that if you have already encountered this issue on your | |
| 35 | + blog, upgrading FeedWordPress will prevent it from re-occurring in the | |
| 36 | + future, but you still need to do two other things to fix the existing | |
| 37 | + problem on your blog. | |
| 38 | + | |
| 39 | + First, for each feed where posts have been mis-attributed, you need to | |
| 40 | + change the existing author mapping rules to re-map a a syndicated | |
| 41 | + author's name to the proper target account. Go to **Syndication --> | |
| 42 | + Authors**, select the feed you want to change from the drop-down list, | |
| 43 | + and then change the settings under the "Syndicated Authors" section. | |
| 44 | + (You will probably need to select "will be assigned to a new user..." to | |
| 45 | + create a new user account with the appropriate name.) | |
| 46 | + | |
| 47 | + Second, for each feed where posts have been mis-attributed, you need to | |
| 48 | + re-assign already-syndicated posts that were mis-attributed to the | |
| 49 | + correct author. You can do that from **Syndication --> Authors** by | |
| 50 | + using the author re-assignment feature, described below. | |
| 51 | + | |
| 52 | +* AUTHOR RE-ASSIGNMENT FOR A PARTICULAR FEED: The author settings page | |
| 53 | + for each syndicated feed, under **Syndication --> Authors**, now | |
| 54 | + includes an section titled "Fixing mis-matched authors," which provides | |
| 55 | + an interface for re-assigning or deleting all posts attributed to a | |
| 56 | + particular author on a particular feed. | |
| 57 | + | |
| 58 | +* SUPPORT FOR `<atom:source>` ELEMENT IN SYNDICATED FEEDS: Some feeds | |
| 59 | + (for example, those produced by FeedWordPress) aggregate content from | |
| 60 | + several different sources, and include information about the original | |
| 61 | + source of the post in an `<atom:source>` element. A new setting under | |
| 62 | + **Syndication --> Options** allows you to control what FeedWordPress | |
| 63 | + will report as the source of posts syndicated from aggregator feeds in | |
| 64 | + your templates and feeds: you can have FeedWordPress report that the | |
| 65 | + source of a post is the aggregator feed itself, or you can have it | |
| 66 | + report that the source of a post is the original source that the | |
| 67 | + aggregator originally syndicated the post from. | |
| 68 | + | |
| 69 | + By default, FeedWordPress will report the aggregator, not the original | |
| 70 | + source, as the source of a syndicated item. | |
| 71 | + | |
| 72 | +* LOAD BALANCING AND TIME LIMITING FEATURES FOR UPDATES: Some users have | |
| 73 | + encountered issues due to running up against PHP execution time limits | |
| 74 | + during the process of updating large syndicated feeds, or a very large | |
| 75 | + set of syndicated feeds. FeedWordPress now has a feature that allows you | |
| 76 | + to limit the total amount of time spent updating a feed, through the | |
| 77 | + "Time limit on updates" setting under **Syndication --> Options**. By | |
| 78 | + turning on this setting and adjusting the time limit to a low enough | |
| 79 | + figure to avoid your PHP installation's time-out setting. (PHP execution | |
| 80 | + time limits are usually in the vicinity of 30 seconds, so an update | |
| 81 | + time limit of 25 seconds or so should provide plenty of time for updates | |
| 82 | + while allowing a cushion of time for other, non-update-related functions | |
| 83 | + to do their work.) | |
| 84 | + | |
| 85 | + If feed updates are interrupted by the time limit, FeedWordPress uses | |
| 86 | + some simple load balancing features to make sure that updates to other | |
| 87 | + feeds will not be blocked by the time-hogging feed, and will also make | |
| 88 | + sure that when the interrupted update is resumed, FeedWordPress will | |
| 89 | + skip ahead to resume processing items at the point at which it was | |
| 90 | + interrupted last time, so that posts further down in the feed will | |
| 91 | + eventually get processed, and not get blocked by the amount of time it | |
| 92 | + takes to process the items higher up in the feed. | |
| 93 | + | |
| 94 | +* `guid` INDEX CREATION BUTTON: FeedWordPress frequently issues queries on | |
| 95 | + the `guid` column of the WordPress posts database (since it uses post | |
| 96 | + guid URIs to keep track of which posts it has syndicated). In very large | |
| 97 | + FeedWordPress installations, you can often significantly improve | |
| 98 | + performance by creating a database index on the `guid` column, but | |
| 99 | + normally you would need to poke around with MySQL or a tool like | |
| 100 | + phpMyAdmin to do this. FeedWordPress can now save you the trouble: to | |
| 101 | + create an index on the `guid` column, just go to | |
| 102 | + **Syndication --> Options**, and mash the button at the bottom of the | |
| 103 | + "Back End" section. | |
| 104 | + | |
| 105 | +Changes from 2008.1030 to 2008.1101 | |
| 106 | +----------------------------------- | |
| 107 | + | |
| 108 | +* INTERFACE BUG THAT PREVENTED ADDING NEW SITES FIXED: The UI reforms in | |
| 109 | + FWP 2008.1030 unintentionally introduced a bug that prevents clean | |
| 110 | + installations of FeedWordPress from providing an input box for adding | |
| 111 | + new feeds to the list of syndicated feeds. This bug has been fixed. | |
| 112 | + | |
| 4 | 113 | Changes from 0.993 to 2008.1030 |
| 5 | 114 | ------------------------------- |
| 6 | 115 | |
| 7 | -* WORDPRESS 2.6 COMPATABILITY: FeedWordPress should now be compatible with | |
| 116 | +* WORDPRESS 2.6 COMPATIBILITY: FeedWordPress should now be compatible with | |
| 8 | 117 | WordPress 2.6, and should work more or less seamlessly with the new post |
| 9 | 118 | revision system. A bug which caused multiple new revisions to be created |
| 10 | 119 | for posts on certain feeds, regardless of whether or not the item had |
| 11 | 120 | been updated, has been fixed. |
| @@ -58,9 +167,9 @@ | ||
| 58 | 167 | posts. If you want to use one of these plugins together with |
| 59 | 168 | FeedWordPress, you can now do so by changing the "Formatting Filters" |
| 60 | 169 | setting from "Protect" to "Expose." |
| 61 | 170 | |
| 62 | -* **`<atom:source>` ELEMENTS NOW INCLUDED IN ATOM FEED:** Atom 1.0 provides | |
| 171 | +* `<atom:source>` ELEMENTS NOW INCLUDED IN ATOM FEED: Atom 1.0 provides | |
| 63 | 172 | a standard method for aggregators to indicate information about the original source of |
| 64 | 173 | a syndicated post, using the `<atom:source>` element. FeedWordPress now |
| 65 | 174 | introduces standard `<atom:source>` elements including the title, homepage, and |
| 66 | 175 | feed URI of the source from which a syndicated post was syndicated. Cf. |
| @@ -138,9 +247,9 @@ | ||
| 138 | 247 | has, hopefully, been resolved, by correcting for the bug in WordPress. |
| 139 | 248 | |
| 140 | 249 | Changes from 0.99 to 0.991 |
| 141 | 250 | -------------------------- |
| 142 | -* WORDPRESS MU COMPATABILITY: FeedWordPress should now be compatible with | |
| 251 | +* WORDPRESS MU COMPATIBILITY: FeedWordPress should now be compatible with | |
| 143 | 252 | recent releases of WordPress MU. Once FeedWordPress is made available |
| 144 | 253 | as a plugin, each individual blog can choose to activate FeedWordPress |
| 145 | 254 | and syndicate content from its own set of contributors. |
| 146 | 255 | |
| @@ -157,12 +266,12 @@ | ||
| 157 | 266 | authors whose names included international characters. This |
| 158 | 267 | incompatability has now been fixed; hopefully, authors with |
| 159 | 268 | international characters in their names should now be handled properly. |
| 160 | 269 | |
| 161 | -* media:content BUG IN MAGPIERSS FIXED: A bug in MagpieRSS's handling of | |
| 162 | - namespaced elements has been fixed. Among other things, this bug caused | |
| 163 | - items containing a Yahoo MediaRSS `<media:content>` element (such as | |
| 164 | - many of the feeds produced by wordpress.com) to be represented | |
| 270 | +* `<media:content>` BUG IN MAGPIERSS FIXED: A bug in MagpieRSS's handling | |
| 271 | + of namespaced elements has been fixed. Among other things, this bug | |
| 272 | + caused items containing a Yahoo MediaRSS `<media:content>` element (such | |
| 273 | + as many of the feeds produced by wordpress.com) to be represented | |
| 165 | 274 | incorrectly, with only a capital "A" where the content of the post |
| 166 | 275 | should have been. Feeds containing `<media:content>` elements should now |
| 167 | 276 | be syndicated correctly. |
| 168 | 277 | |
| @@ -538,9 +647,10 @@ | ||
| 538 | 647 | into the WordPress database so that (among other things) that post |
| 539 | 648 | will have its enclosure listed in your blog's RSS 2 newsfeed. |
| 540 | 649 | |
| 541 | 650 | Note that enclosure support requires using the optional MagpieRSS |
| 542 | - upgrade (i.e., replacing your `wp-includes/rss-functions.php` with `OPTIONAL/wp-includes/rss-functions.php` from the FWP archive) | |
| 651 | + upgrade (i.e., replacing your `wp-includes/rss-functions.php` with | |
| 652 | + `OPTIONAL/wp-includes/rss-functions.php` from the FWP archive) | |
| 543 | 653 | |
| 544 | 654 | * FEATURE: for completeness's sake, there is now a feed setting, |
| 545 | 655 | `hardcode url`, that allows you to set the URI for the front page |
| 546 | 656 | of a contributor's website manually (that is, prevent it from being |
