| @@ -1,387 +1,109 @@ | ||
| 1 | -FeedWordPress Change Log | |
| 2 | -======================== | |
| 1 | +Change Log | |
| 2 | +========== | |
| 3 | 3 | |
| 4 | -Changes from 0.98 to 0.981 | |
| 5 | - | |
| 6 | -Version 0.981 is a narrowly targeted bugfix and compatibility release, whose | |
| 7 | -main purpose is to resolve a major outstanding problem: the incompatibility | |
| 8 | -between version 0.98 of WordPress and the recently released WordPress 2.1. | |
| 9 | - | |
| 10 | -* WORDPRESS 2.1 COMPATIBILITY: FeedWordPress is now compatible with | |
| 11 | - WordPress 2.1, as well as retaining its existing support for WordPress | |
| 12 | - 2.0 and 1.5. Incompatibilities that resulted in database warnings, fatal | |
| 13 | - errors, and which prevented FeedWordPress from syndicating new posts, | |
| 14 | - have been eliminated. | |
| 15 | - | |
| 16 | -* RSS-FUNCTIONS.PHP RENAMED TO RSS.PHP: if you use the upgraded MagpieRSS | |
| 17 | - replacement that's included with FeedWordPress, be sure to note that | |
| 18 | - there are now *two* files to upload from the `OPTIONAL/wp-includes` | |
| 19 | - subdirectory in order to carry out the upgrade: rss-functions.php and | |
| 20 | - rss.php. **It is necessary to upload both files**, due to a change in | |
| 21 | - the file naming scheme in WordPress 2.1, and it is necessary to do so | |
| 22 | - whether you are using WordPress 2.1 or not. If you only upload the | |
| 23 | - `rss-functions.php` file as in previous installations you will not have | |
| 24 | - a working copy of MagpieRSS; the rss.php file contains the actual code. | |
| 25 | - | |
| 26 | -* DATE BUG AFFECTING SOME PHP INSTALLATIONS RESOLVED: due to a subtle bug | |
| 27 | - in parse_w3cdtf(), some installations of PHP encountered problems with | |
| 28 | - FeedWordPress's attempt to date posts, which would cause some new posts | |
| 29 | - on Atom feeds to be dated as if they had apppeared in 1969 or 1970 | |
| 30 | - (thus, effectively, never appearing on front apge at all). This bug in | |
| 31 | - the date handling should now be fixed. | |
| 32 | - | |
| 33 | -* PHP <?=...?> SHORT FORM ELIMINATED: some installations of PHP do not | |
| 34 | - allow the <?=...?> short form for printing PHP values, which was used | |
| 35 | - extensively in the FeedWordPress interface code. Since this could cause | |
| 36 | - fatal errors for users with the wrong installation of PHP, the short | |
| 37 | - form has been replaced with full PHP echo statements, and is no longer | |
| 38 | - used in FeedWordPress. | |
| 39 | - | |
| 40 | -* BETTER USER INTERFACE INTEGRATION WITH WORDPRESS 2.x: Some minor changes | |
| 41 | - have been made to help the FeedWordPress interface pages blend in better | |
| 42 | - with the user interface when running under WordPress 2.x. | |
| 43 | - | |
| 44 | -* GLOBAL CATEGORIES BUG RESOLVED: a bug that prevented some users from | |
| 45 | - setting one or more categories to apply to syndicated posts from all | |
| 46 | - feeds (using the checkbox interface under Options --> Syndication) has | |
| 47 | - been resolved. | |
| 48 | - | |
| 49 | -Changes from 0.97 to 0.98 | |
| 50 | - | |
| 51 | -* WORDPRESS 2.0 COMPATIBILITY: This is a narrowly-targeted release to | |
| 52 | - solve a major outstanding problem. FeedWordPress is now compatible with | |
| 53 | - both WordPress 1.5 and WordPress 2.0. Incompatibilities that caused | |
| 54 | - fatal SQL errors, and a more subtle bug with off-kilter counts of posts | |
| 55 | - under a given category, have been resolved. FeedWordPress tests for | |
| 56 | - database schema using the global $wp_db_version variable (if null, then | |
| 57 | - we presume that we're dealing with WordPress 1.5). | |
| 58 | - | |
| 59 | - NOTE: I have **not** fully tested FeedWordPress with WordPress 2.0. | |
| 60 | - Further testing may reveal more bugs. However, you should now be able | |
| 61 | - to get at least basic FeedWordPress functionality up and running. | |
| 62 | - | |
| 63 | -* AUTHOR MATCHING: FeedWordPress tests several fields to see if it can | |
| 64 | - identify the author of the post as a user already in the WordPress user | |
| 65 | - database. In previous versions, it tested the user login, the nickname, | |
| 66 | - and tested for "aliases" listed in the Profile (see documentation). FWP | |
| 67 | - now also matches authors on the basis of e-mail address (*if* an e-mail | |
| 68 | - address is present). This is particularly helpful for formats such as | |
| 69 | - RSS 2.0, in which authors are primarily identified by e-mail addresses. | |
| 70 | - | |
| 71 | -Changes from 0.96 to 0.97 | |
| 72 | - | |
| 73 | -* INSTALLATION PROCEDURE: Some of the changes between 0.96 and 0.97 | |
| 74 | - require upgrades to the meta-data stored by FeedWordPress to work | |
| 75 | - properly. Thus, if you are upgrading from 0.96 or earlier to 0.97, most | |
| 76 | - FeedWordPress operations (including updates and template functions) | |
| 77 | - WILL BE DISABLED until you run the upgrade procedure. Fortunately, | |
| 78 | - running the upgrade procedure is easy: just go to either Options --> | |
| 79 | - Syndication or Links --> Syndicated in the WordPress Dashboard and press | |
| 80 | - the button. | |
| 81 | - | |
| 82 | -* FEED FORMAT SUPPORT: Support has been added for the Atom 1.0 IETF | |
| 83 | - standard. Several other elements are also newly supported | |
| 84 | - (dcterms:created, dcterms:issued, dcterms:modified, dc:identifier, | |
| 85 | - proper support for the RSS 2.0 guid element, the RSS 2.0 author element, | |
| 86 | - the use of Atom author or Dublin Core dc:creator constructs at the feed | |
| 87 | - level to identify the author of individual items, etc.) | |
| 88 | - | |
| 89 | - N.B.: full support of several Atom 1.0 features, such as categories | |
| 90 | - and enclosures, requires you to install the optional rss-functions.php | |
| 91 | - upgrade in your wp-includes directory. | |
| 92 | - | |
| 93 | -* BUG FIX: Running `update-feeds.php` from command line or crontab | |
| 94 | - returned "I don't syndicate..." errors. It turns out that WordPress | |
| 95 | - sometimes tramples on the internal PHP superglobals that I depended on | |
| 96 | - to determine whether or not the script was being invoked from the | |
| 97 | - command line. This has been fixed (the variables are now checked | |
| 98 | - *before* WordPress can trample them). Note that `update-feeds.php` has | |
| 99 | - been thoroughly overhauled anyway; see below for details. | |
| 100 | - | |
| 101 | -* BUG FIX: Duplicate categories or author names. Fixed two bugs that could | |
| 102 | - create duplicate author and/or category names when the name contained | |
| 103 | - either (a) certain international characters (causing a mismatch between | |
| 104 | - MySQL and PHP's handling of lowercasing text), or (b) characters that | |
| 105 | - have a special meaning in regular expressions (causing MySQL errors when | |
| 106 | - looking for the author or category due to regexp syntax errors). These | |
| 107 | - should now be fixed thanks to careful escaping of names that go into | |
| 108 | - regular expressions and careful matching of lowercasing functions | |
| 109 | - (comparing results from PHP only to other results from PHP, and results | |
| 110 | - from MySQL only to other results from MySQL). | |
| 111 | - | |
| 112 | -* BUG FIX: Items dated Decembr 31, 1969 should appear less often. The | |
| 113 | - function for parsing W3C date-time format dates that ships with | |
| 114 | - MagpieRSS can only correctly parse fully-specified dates with a | |
| 115 | - fully-specified time, but valid W3C date-time format dates may omit the | |
| 116 | - time, the day of the month, or even the month. Some feeds in the wild | |
| 117 | - date their items with coarse-grained dates, so the optional | |
| 118 | - `rss-functions.php` upgrade now includes a more flexible parse_w3cdtf() | |
| 119 | - function that will work with both coarse-grained and fully-specified | |
| 120 | - dates. (If parts of the date or the time are omitted, they are filled in | |
| 121 | - with values based on the current time, so '2005-09-10' will be dated to | |
| 122 | - the current time on that day; '2004' will be dated to this day and time | |
| 123 | - one year ago. | |
| 124 | - | |
| 125 | - N.B.: This fix is only available in the optional `rss-functions.php` | |
| 126 | - upgrade. | |
| 127 | - | |
| 128 | -* BUG FIX: Evil use of HTTP GET has been undone. The WordPress interface | |
| 129 | - is riddled with inappropriate (non-idempotent) uses of HTTP GET queries | |
| 130 | - (ordinary links that make the server do something with significant | |
| 131 | - side-effects, such as deleting a post or a link from the database). | |
| 132 | - FeedWordPress did some of this too, especially in places where it aped | |
| 133 | - the WordPress interface (e.g. the "Delete" links in Links --> | |
| 134 | - Syndicated). That's bad business, though. I've changed the interface so | |
| 135 | - that all the examples of improper side-effects that I can find now | |
| 136 | - require an HTTP POST to take effect. I think I got pretty much | |
| 137 | - everything; if there's anything that I missed, let me know. | |
| 138 | - | |
| 139 | - Further reading: [Sam Ruby 2005-05-06: This Stuff Matters] (http://www.intertwingly.net/blog/2005/05/06/This-Stuff-Matters) | |
| 140 | - | |
| 141 | -* BUG FIX: Categories applied by `cats` setting should no longer prevent | |
| 142 | - category-based filtering from working. In FeedWordPress, you can (1) | |
| 143 | - apply certain categories to all syndicated posts, or all posts from | |
| 144 | - a particular feed; and (2) filter out all posts that don't match one | |
| 145 | - of the categories that are already in the WordPress database (allowing | |
| 146 | - for simple category-based filtering; just load up WordPress with the | |
| 147 | - categories you want to accept, and then tell FeedWordPress not to create | |
| 148 | - new ones). However, the way that (1) and (2) were implemented meant that | |
| 149 | - you couldn't effectively use them together; once you applied a known | |
| 150 | - category to all syndicated posts from a particular feed, it meant that | |
| 151 | - they'd have at least one familiar category (the category or categories | |
| 152 | - you were applying), and that would get all posts past the filter no | |
| 153 | - matter what categories they were originally from. | |
| 154 | - | |
| 155 | - Well, no longer. You can still apply categories to all syndicated posts | |
| 156 | - (using either Syndication --> Options, or the feed-level settings under | |
| 157 | - Links --> Syndicated). But these categories are not applied to the post | |
| 158 | - until *after* it has already passed by the "familiar categories" filter. | |
| 159 | - So now, if you want, you can do category filtering and *then* apply as | |
| 160 | - many categories as you please to all and only posts that pass the filter. | |
| 161 | - | |
| 162 | -* BUG FIX: Other minor typos and HTML gaffes were fixed along the way. | |
| 163 | - | |
| 164 | -* PERFORMANCE: get_feed_meta() no longer hits the database for information | |
| 165 | - on every call; it now caches link data in memory, so FeedWordPress only | |
| 166 | - goes to the database once for each syndicated link. This may | |
| 167 | - substantially improve performance if your database server resources | |
| 168 | - are tight and your templates make a lot of use of custom settings from | |
| 169 | - get_feed_meta(). | |
| 170 | - | |
| 171 | -* API CHANGE: Link ID numbers, rather than RSS URIs, are now used to | |
| 172 | - identify the feed from which a post is syndicated when you use template | |
| 173 | - functions such as get_feed_meta(). The practical upshot of this is you | |
| 174 | - can switch feeds, or change the feed address for a particular syndicated | |
| 175 | - site, without breaking your templates for all the posts that were | |
| 176 | - syndicated from the earlier URI. | |
| 177 | - | |
| 178 | -* API CHANGE: if you have plugins or templates that make use of the | |
| 179 | - get_feed_meta() function or the $fwp_feedmeta global, note that the | |
| 180 | - data formerly located under the `uri` and `name` fields is now located | |
| 181 | - under the `link/uri` field and the `link/name` field, respectively. Note | |
| 182 | - also that you can access the link ID number for any given feed under the | |
| 183 | - global $fwp_feedmeta['link/id'] (in plugins) or | |
| 184 | - get_feed_meta('link/id') (in a template in post contexts). | |
| 185 | - | |
| 186 | -* FEATURE: the settings for individual feeds can now be edited using a | |
| 187 | - humane interface (where formerly you had to tweak key-value pairs in the | |
| 188 | - Link Notes section). To edit settings for a feed, pick the feed that you | |
| 189 | - want under Links --> Syndicated and click the Edit link. | |
| 190 | - | |
| 191 | -* FEATURE: The "Unsubscribe" button (formerly "Delete") in Links --> | |
| 192 | - Syndicated now offers three options for unsubscribing from a feed: (1) | |
| 193 | - turning off the subscription without deleting the feed data or affecting | |
| 194 | - posts that were syndicated from the feed (this works by setting the Link | |
| 195 | - for the feed as "invisible"); (2) deleting the feed data and all of the | |
| 196 | - posts that were syndicated from the feed; or (3) deleting the feed data | |
| 197 | - and *keeping* the posts that were syndicated from the feed | |
| 198 | - setting the Link to "Invisible" (meaning that it will not be displayed | |
| 199 | - in lists of the site links on the front page, and it won't be checked | |
| 200 | - for updates; (2) deleting the Link and all of the posts that were | |
| 201 | - syndicated from its feed; or (3) deleting the feed data but keeping the | |
| 202 | - posts that were syndicated (which will henceforward be treated as if | |
| 203 | - they were local rather than syndicated posts). (Note that (1) is usually | |
| 204 | - the best option for aggregator sites, unless you want to clean up the | |
| 205 | - results of an error or a test.) | |
| 206 | - | |
| 207 | -* FEATURE / BUG FIX: If you have been receiving mysterious "I don't | |
| 208 | - syndicate...", or "(local) HTTP status code was not 200", or "(local) | |
| 209 | - transport error - could not open socket", or "parse error - not well | |
| 210 | - formed" errors, then this update may solve your problems, and if it does | |
| 211 | - *not* solve them, it will at least make the reasons for the problems | |
| 212 | - easier to understand. That's because I've overhauled the way that | |
| 213 | - FeedWordPress goes about updating feeds. | |
| 214 | - | |
| 215 | - If you use the command-line PHP scripting method to run scheduled | |
| 216 | - updates, then not much should change for you, except for fewer | |
| 217 | - mysterious errors. If you have done updates by sending periodic HTTP | |
| 218 | - requests to <http://your-blog.com/path/wp-content/update-feeds.php>, | |
| 219 | - then the details have changed somewhat; mostly in such a way as to make | |
| 220 | - things easier on you. See the README file or online documentation on | |
| 221 | - Staying Current for the details. | |
| 222 | - | |
| 223 | -* FEATURE: FeedWordPress now features a more sophisticated system for | |
| 224 | - timed updates. Instead of polling *every* subscribed feed for updates | |
| 225 | - *each* time `update-feeds.php` is run, FeedWordPress now keeps track of | |
| 226 | - the last time it polled each feed, and only polls them again after a | |
| 227 | - certain period of time has passed. The amount of time is normally set | |
| 228 | - randomly for each feed, in a period between 30 minutes and 2 hours (so | |
| 229 | - as to stagger updates over time rather than polling all of the feeds at once. However, the length of time between updates can also be set | |
| 230 | - directly by the feed, which brings us to ... | |
| 231 | - | |
| 232 | -* FEATURE: FeedWordPress now respects the settings in the `ttl` and | |
| 233 | - Syndication Module RSS elements. Feeds with these elements set will not | |
| 234 | - be polled any more frequently than they indicate with these feeds unless | |
| 235 | - the user manually forces FeedWordPress to poll the feed (see Links --> | |
| 236 | - Syndicated --> Edit settings). | |
| 237 | - | |
| 238 | -Changes from 0.95 to 0.96 | |
| 239 | - | |
| 240 | -* FEATURE: support has been added for enclosures in RSS 2.0 and Atom | |
| 241 | - 0.6+ newsfeeds. WordPress already supports adding enclosures to an | |
| 242 | - item; FeedWordPress merely gets the information on the enclosure | |
| 243 | - from the feed it is syndicating and plugs that information directly | |
| 244 | - into the WordPress database so that (among other things) that post | |
| 245 | - will have its enclosure listed in your blog's RSS 2 newsfeed. | |
| 246 | - | |
| 247 | - Note that enclosure support requires using the optional MagpieRSS | |
| 248 | - upgrade (i.e., replacing your `wp-includes/rss-functions.php` with `OPTIONAL/wp-includes/rss-functions.php` from the FWP archive) | |
| 249 | - | |
| 250 | -* FEATURE: for completeness's sake, there is now a feed setting, | |
| 251 | - `hardcode url`, that allows you to set the URI for the front page | |
| 252 | - of a contributor's website manually (that is, prevent it from being | |
| 253 | - automatically updated from the feed channel link on each update). To | |
| 254 | - set the URI manually, put a line like this in the Link Notes section | |
| 255 | - of a feed: | |
| 256 | - | |
| 257 | - hardcode url: yes | |
| 258 | - | |
| 259 | - You can also instruct FeedWordPress to use hardcoded URIs by default | |
| 260 | - on all feeds using Options --> Syndication | |
| 261 | - | |
| 262 | -* FEATURE: by default, when FeedWordPress finds new syndicated posts, | |
| 263 | - it (1) publishes them immediately, (2) turns comments off, and (3) | |
| 264 | - turns trackback / pingback pings off. You can now alter all three | |
| 265 | - default behaviors (e.g., to allow pings on syndicated posts, or to | |
| 266 | - send newly-syndicated posts to the draft pile for moderation) using | |
| 267 | - Options --> Syndication | |
| 268 | - | |
| 269 | - | |
| 270 | 4 | Changes from 0.91 to 0.95 |
| 271 | 5 | ------------------------- |
| 272 | 6 | |
| 273 | -* BUG FIX: Fixed an obscure bug in the handling of categories: | |
| 274 | - categories with trailing whitespace could cause categories with | |
| 275 | - duplicate names to be created. This no longer happens. While I was | |
| 276 | - at it I tightened up the operation of | |
| 277 | - FeedWordPress::lookup_categories() a bit in general. | |
| 7 | +* BUG FIX: Fixed an obscure bug in the handling of categories: categories | |
| 8 | + with trailing whitespace could cause categories with duplicate names to | |
| 9 | + be created. This no longer happens. While I was at it I tightened up the | |
| 10 | + operation of FeedWordPress::lookup_categories() a bit in general. | |
| 278 | 11 | |
| 279 | 12 | * FEATURE DEPRECATED: the feed setting `hardcode categories` is now |
| 280 | - deprecated in favor of `unknown categories` (see below), which | |
| 281 | - allows you to strip off any syndication categories not already in | |
| 282 | - your database using `unknown categories: default` or `unknown | |
| 283 | - categories: filter`. If you have `hardcode categories: yes` set on a | |
| 284 | - feed, this will be treated as `unknown categories: default` (i.e., | |
| 285 | - no new categories will be added, but if a post doesn't match any of | |
| 286 | - the categories it will be added in the default category--usually | |
| 287 | - "Uncategorized" or "General"). | |
| 13 | + deprecated in favor of `unknown categories` (see below), which allows | |
| 14 | + you to strip off any syndication categories not already in your database | |
| 15 | + using `unknown categories: default` or `unknown categories: filter`. If | |
| 16 | + you have `hardcode categories: yes` set on a feed, this will be treated | |
| 17 | + as `unknown categories: default` (i.e., no new categories will be added, | |
| 18 | + but if a post doesn't match any of the categories it will be added in | |
| 19 | + the default category--usually "Uncategorized" or "General"). | |
| 288 | 20 | |
| 289 | 21 | * FEATURE: You can now set global defaults as to whether or not |
| 290 | - FeedWordPress will update the Link Name and Link Description | |
| 291 | - settings for feeds automatically from the feed title and feed | |
| 292 | - tagline. (By default, it does, as it has in past versions.) Whether | |
| 293 | - this behavior is turned on or off, you can still override the | |
| 294 | - default behavior using feed settings of `hardcode name: yes`, | |
| 295 | - `hardcode name: no`, `hardcode description: yes`, or `hardcode | |
| 296 | - description: no`. | |
| 22 | + FeedWordPress will update the Link Name and Link Description settings | |
| 23 | + for feeds automatically from the feed title and feed tagline. (By | |
| 24 | + default, it does, as it has in past versions.) Whether this behavior is | |
| 25 | + turned on or off, you can still override the default behavior using | |
| 26 | + feed settings of `hardcode name: yes`, `hardcode name: no`, | |
| 27 | + `hardcode description: yes`, or `hardcode description: no`. | |
| 297 | 28 | |
| 298 | -* FEATURE: Users can now provide one or several "aliases" for an | |
| 299 | - author, just as they can for a category. For example, to make | |
| 300 | - FeedWordPress treat posts by "Joseph Cardinal Ratzinger" and "Pope | |
| 301 | - Benedict XVI" as by the same author, edit the user profile for Pope | |
| 302 | - Benedict XVI and add a line like this to the "User profile" field: | |
| 29 | +* FEATURE: Users can now provide one or several "aliases" for an author, | |
| 30 | + just as they can for a category. For example, to make FeedWordPress | |
| 31 | + treat posts by "Joseph Cardinal Ratzinger" and "Pope Benedict XVI" as | |
| 32 | + by the same author, edit the user profile for Pope Benedict XVI and add | |
| 33 | + a line like this to the "User profile" field: | |
| 303 | 34 | |
| 304 | 35 | a.k.a.: Joseph Cardinal Ratzinger |
| 305 | 36 | |
| 306 | - You can add several aliases, each on a line by itself. You can also | |
| 307 | - add any other text you like to the Profile without interfering with | |
| 308 | - the aliases. | |
| 37 | + You can add several aliases, each on a line by itself. You can also add | |
| 38 | + any other text you like to the Profile without interfering with the | |
| 39 | + aliases. | |
| 309 | 40 | |
| 310 | -* FEATURE: Users can now choose how to handle syndicated posts that | |
| 311 | - are in unfamiliar categories or by unfamiliar authors (i.e., | |
| 312 | - categories or authors whose names are not yet in the WordPress | |
| 313 | - database). By default, FeedWordPress will (as before) create a new | |
| 314 | - category (or new author) and use it for the current post and any | |
| 315 | - future posts. This behavior can be changed, either for all feeds or | |
| 316 | - for one or another particular feed. | |
| 41 | +* FEATURE: Users can now choose how to handle syndicated posts that are | |
| 42 | + in unfamiliar categories or by unfamiliar authors (i.e., categories or | |
| 43 | + authors whose names are not yet in the WordPress database). By default, | |
| 44 | + FeedWordPress will (as before) create a new category (or new author) and | |
| 45 | + use it for the current post and any future posts. This behavior can be | |
| 46 | + changed, either for all feeds or for one or another particular feed. | |
| 317 | 47 | |
| 318 | 48 | There are now three different options for an unfamiliar author: (1) |
| 319 | 49 | FeedWordPress can create a new author account and attribute the |
| 320 | - syndicated post to the new account; (2) FeedWordPress can attribute | |
| 321 | - the post to an author if the author's name is familiar, and to a | |
| 322 | - default author (currently, this means the Site Administrator | |
| 323 | - account) if it is not; (3) FeedWordPress can drop posts by | |
| 324 | - unfamiliar authors and syndicate only posts by authors who are | |
| 325 | - already in the database. | |
| 50 | + syndicated post to the new account; (2) FeedWordPress can attribute the | |
| 51 | + post to an author if the author's name is familiar, and to a default | |
| 52 | + author (currently, this means the Site Administrator account) if it is | |
| 53 | + not; (3) FeedWordPress can drop posts by unfamiliar authors and | |
| 54 | + syndicate only posts by authors who are already in the database. | |
| 326 | 55 | |
| 327 | - There are, similarly, two different options for an unfamiliar | |
| 328 | - category: (1) FeedWordPress can create new categories and place the | |
| 329 | - syndicated post in them; (2) FeedWordPress can drop the unfamiliar | |
| 330 | - categories and place syndicated posts only in categories that it is | |
| 331 | - already familiar with. In addition, FeedWordPress 0.95 lets you | |
| 332 | - choose whether posts that are in *no* familiar categories should be | |
| 333 | - syndicated (and placed in the default category for the blog) or | |
| 334 | - simply dropped. | |
| 56 | + There are, similarly, two different options for an unfamiliar category: | |
| 57 | + (1) FeedWordPress can create new categories and place the syndicated | |
| 58 | + post in them; (2) FeedWordPress can drop the unfamiliar categories and | |
| 59 | + place syndicated posts only in categories that it is already familiar | |
| 60 | + with. In addition, FeedWordPress 0.95 lets you choose whether posts that | |
| 61 | + are in *no* familiar categories should be syndicated (and placed in the | |
| 62 | + default category for the blog) or simply dropped. | |
| 335 | 63 | |
| 336 | - You can set the default behavior for both authors and categories | |
| 337 | - using the settings in Options --> Syndication. You can also set | |
| 338 | - different behavior for specific feeds by adding the `unfamiliar | |
| 339 | - author` and / or `unfamiliar categories` settings to the Link Notes | |
| 340 | - section of a feed: | |
| 64 | + You can set the default behavior for both authors and categories using | |
| 65 | + the settings in Options --> Syndication. You can also set different | |
| 66 | + behavior for specific feeds by adding the `unfamiliar author` and / or | |
| 67 | + `unfamiliar categories` settings to the Link Notes section of a feed: | |
| 341 | 68 | |
| 342 | 69 | unfamiliar author: (create|default|filter) |
| 343 | 70 | unfamiliar categories: (create|default|filter) |
| 344 | 71 | |
| 345 | - A setting of `unfamiliar author: create` will make FeedWordPress | |
| 346 | - create new authors to match unfamiliar author names *for this feed | |
| 347 | - alone*. A setting of `unfamiliar author: default` will make it | |
| 348 | - assign posts from unfamiliar authors to the default user account. A | |
| 349 | - setting of `unfamiliar author: filter` will cause all posts (from | |
| 350 | - this feed alone) to be dropped unless they are by an author already | |
| 351 | - listed in the database. Similiarly, `unfamiliar categories: create` | |
| 352 | - will make FeedWordPress create new categories to match unfamiliar | |
| 353 | - category names *for this feed alone*; `unfamiliar categories: | |
| 354 | - default` will cause it to drop any unfamiliar category names; and | |
| 72 | + A setting of `unfamiliar author: create` will make FeedWordPress create | |
| 73 | + new authors to match unfamiliar author names *for this feed alone*. A | |
| 74 | + setting of `unfamiliar author: default` will make it assign posts from | |
| 75 | + unfamiliar authors to the default user account. A setting of | |
| 76 | + `unfamiliar author: filter` will cause all posts (from this feed alone) | |
| 77 | + to be dropped unless they are by an author already listed in the | |
| 78 | + database. Similiarly, `unfamiliar categories: create` will make | |
| 79 | + FeedWordPress create new categories to match unfamiliar category names | |
| 80 | + *for this feed alone*; `unfamiliar categories: default` will cause it | |
| 81 | + to drop any unfamiliar category names; and | |
| 355 | 82 | `unfamiliar categories: filter` will cause it to *both* drop any |
| 356 | - unfamiliar category names *and* to only syndicate posts that are | |
| 357 | - placed in one or more familiar categories. | |
| 83 | + unfamiliar category names *and* to only syndicate posts that are placed | |
| 84 | + in one or more familiar categories. | |
| 358 | 85 | |
| 359 | - These two new features allow users to do some coarse-grained | |
| 360 | - filtering without having to write a PHP filter. Specifically, they | |
| 361 | - offer an easy way for you to filter feeds by category or by author. | |
| 362 | - Suppose, for example, that you only wanted to syndicate posts that | |
| 363 | - your contributors place in the "Llamas" category. You could do so by | |
| 364 | - setting up your installation of WordPress so that the only category | |
| 365 | - in the database is "Llamas," and then use Options --> Syndication to | |
| 366 | - set "Unfamiliar categories" to "don't create new categories and | |
| 367 | - don't syndicate posts unless they match at least one familiar | |
| 368 | - category". Now, when you update, only posts in the "Llamas" category | |
| 369 | - will be syndicated by FeedWordPress. | |
| 86 | + These two new features allow users to do some coarse-grained filtering | |
| 87 | + without having to write a PHP filter. Specifically, they offer an easy | |
| 88 | + way for you to filter feeds by category or by author. Suppose, for | |
| 89 | + example, that you only wanted to syndicate posts that your contributors | |
| 90 | + place in the "Llamas" category. You could do so by setting up your | |
| 91 | + installation of WordPress so that the only category in the database is | |
| 92 | + "Llamas," and then use Options --> Syndication to set "Unfamiliar | |
| 93 | + categories" to "don't create new categories and don't syndicate posts | |
| 94 | + unless they match at least one familiar category". Now, when you update, | |
| 95 | + only posts in the "Llamas" category will be syndicated by FeedWordPress. | |
| 370 | 96 | |
| 371 | 97 | Similarly, if you wanted to filter one particular feed so that only |
| 372 | 98 | posts by (for example) the author "Earl J. Llama" were syndicated to |
| 373 | - your site, you could do so by creating a user account for Earl J. | |
| 374 | - Llama, then adding the following line to the settings for the feed | |
| 375 | - in Link Notes: | |
| 99 | + your site, you could do so by creating a user account for Earl J. Llama, | |
| 100 | + then adding the following line to the settings for the feed in Link | |
| 101 | + Notes: | |
| 376 | 102 | |
| 377 | 103 | unfamiliar author: filter |
| 378 | 104 | |
| 379 | - This will cause any posts from this feed that are not authored by | |
| 380 | - Earl J. Llama to be discarded, and only the posts by Earl J. Llama | |
| 381 | - will be syndicated. (If the setting is used on one specific feed, it | |
| 382 | - will not affect how posts from other feeds are syndicated.) | |
| 105 | + This will cause any posts from this feed that are not authored by Earl | |
| 106 | + J. Llama to be discarded, and only the posts by Earl J. Llama will be | |
| 107 | + syndicated. (If the setting is used on one specific feed, it will not | |
| 108 | + affect how posts from other feeds are syndicated.) | |
| 383 | 109 | |
