feedwordpress / ChangeLog.text

ChangeLog.text in FeedWordPress 2009.0613, at ChangeLog.text

982 lines 54.6 KB

Raw Download Zip

1	FeedWordPress Change Log
2	========================
3	Changes from 2009.0612 to Trunk
4	-------------------------------
5	* INTERFACE/BUGFIX: WORDPRESS 2.8 CATEGORY BOX FIX. Thanks to a subtle
6	change in class names between the WordPress 2.7 and 2.8 stylesheets,
7	category boxes in the FeedWordPress settings interface tended to overflow
8	and have a lot of messy-looking overlapping text under WordPress 2.8.
9	This has now been fixed.
10
11	* FeedFinder FAILURE DIAGNOSTICS: When FWP's FeedFinder fails to find any
12	feeds at a given URL (for example, when you are trying to add a
13	subscription through the administrative interface and you run into an
14	error message), FeedWordPress now provides more diagnostic information
15	for the reasons behind the failure. If that helps you, great; if not,
16	it should help me respond more intelligently to your support request..
17
18	Changes from 2008.1214 to 2009.0612
19	-----------------------------------
20	* WORDPRESS 2.8 COMPATIBILITY: FeedWordPress 2009.0612 has been tested for
21	compatibility with the recent version 2.8 release of WordPress.
22
23	* INTERFACE RESTRUCTURING: In order to avoid settings posts from becoming
24	too crowded, and to modularize and better organize the user interface,
25	new "Posts" and "Categories & Tags" subpages have been created under the
26	"Syndication" menu. "Posts" controls settings for individal syndicated
27	posts (such as publication status, comment and ping status, whether or
28	not to use the original location of the post as the permalink, whether
29	or not to expose posts to formatting filters, and so on). "Categories &
30	Tags" controls settings for assigning new syndicated posts to categories
31	and tags, such as categories or tags to apply to all syndicated posts,
32	and how to handle categories that do not yet exist in the WordPress
33	database. These subpages, like the Authors subpage, handle settings for
34	the global default level and for individual syndicated feeds.
35
36	Corresponding to these new subpages, the old Syndication Settings and
37	Feed Settings subpages have been cleaned up and simplified, and now only
38	link to the appropriate subpages for options that can be set in the
39	Posts, Authors, or Categories & Tags subpages.
40
41	* FEATURE: ADD CUSTOM SETTINGS TO EACH SYNDICATED POST: FeedWordPress has
42	long had an interface for creating custom settings for each syndicated
43	feed which could be retrieved in templates using the `get_feed_meta()`
44	template function. But it had no feature for adding custom fields to
45	each individual syndicated post. In response to requests from users, I
46	have added the ability to apply custom fields to each individual
47	syndicated post, using the new Syndication --> Posts subpage. You can
48	set up custom fields to be applied to every syndicated post, or custom
49	fields to be applied to syndicated posts from a particular feed.
50
51	* FEATURE: MAGPIERSS VERSION CHECK AND UPGRADE: FeedWordPress will attempt
52	to determine whether or not you are using the upgraded version of
53	MagpieRSS that comes packaged with FeedWordPress. If not, it will throw
54	an error on admin pages, and, if you are a site administrator, it will
55	give you the option to ignore the error message, or to attempt an
56	automatic upgrade (using a native file copy). If the file copy fails,
57	FeedWordPress will offer some guidance on how to perform the upgrade
58	manually.
59
60	* BLANK POSTS PROBLEM NO LONGER OCCURS WITH OLD & BUSTED MAGPIERSS: Due
61	to the fact that I relied on a content normalization that occurs in my
62	upgraded version of MagpieRSS, but not in the old & busted version of
63	MagpieRSS that ships with WordPress, until this version, if you tried to
64	syndicate an Atom feed without having performed the (*strongly
65	recommended*) MagpieRSS upgrade, all of the posts would come up with
66	completely blank contents. That's not because MagpieRSS couldn't read
67	the data, but rather because the new Magpie version puts that data in a
68	location where the old version doesn't, and I was only looking in that
69	newer location. Now it checks for both, meaning that posts will continue
70	to display their contents even if you don't upgrade MagpieRSS. (But you
71	really should upgrade it, anyway.)
72
73	* BUGFIX: RELATIVE URI RESOLUTION FOR POST CONTENT RESTORED. Some time
74	back, I added support for resolving relative URIs against xml:base on
75	feeds that support it to the MagpieRSS upgrade in FeedWordPress. Then I
76	took out code that did the same thing from the main FeedWordPress code.
77	Of course, the problem is that some people, even though it is clearly
78	stupid or evil to do so, still include relative URIs for images or links
79	in posts on feed formats that do not adequately support xml:base
80	(notably, RSS 2.0 feeds). In response to a user request, I have added
81	this functionality back in, so that MagpieRSS will resolve any relative
82	URIs that it knows how to resolve using xml:base, and then FeedWordPress
83	will attempt to resolve any relative URIs that are left over afterwards.
84
85	* BUGFIX: INTERFACE OPTION FOR SETTING SYNDICATED POST PUBLICATION STATUS
86	ON A FEED-BY-FEED BASIS HAS BEEN RESTORED: Due to a version-checking
87	bug, users of WordPress 2.7.x lost an option from the "Edit a syndicated
88	feed" interface which allowed them to determine whether newly syndicated
89	posts should be published immediately, held as "Pending Review," saved
90	as drafts, or saved as private posts. (The option to change this
91	setting globally remained in place, but users could no longer set it on
92	a feed-by-feed basis.) The version-checking bug has been fixed, and the
93	option has been restored.
94
95	* BUGFIX: "ARE YOU SURE?" FATAL ERROR ELIMINATED AND SECURITY IMPROVED:
96	Under certain circumstances (for example, when users have configured
97	their browser or proxy not to send HTTP Referer headers, for privacy or
98	other reasons), many features in the FeedWordPress administrative
99	interface (such as adding new feeds or changing settings) would hit a
100	fatal error, displaying only a cryptic message reading "Are you sure?"
101	and a blank page following it. This problem has been eliminated by
102	taking advantage of WordPress's nonce functions, which allow the
103	security check which ran into this error to work properly even without
104	receiving an HTTP Referer header. (N.B.: WordPress's nonce functions
105	were first introduced in WordPress 2.0.3. If you're using FeedWordPress
106	with an older version of WordPress, there's no fix for this problem:
107	you'll just need to turn Referer headers back on. Sorry.)
108
109	* BUGFIX: MANUALLY-ALTERED POST STATUS, COMMENT STATUS, AND PING STATUS NO
110	LONGER REVERTED BY POST UPDATES: If you manually altered the post status,
111	comment status, or ping status of a syndicated post from what it was set
112	to when first syndicated -- for example, if you had a feed that was set
113	to bring in new posts as "Pending Review," and you then marked some of
114	the pending posts as "Published" and others as "Unpublished" -- then
115	in previous versions of FeedWordPress, these manual changes to the
116	status would be lost -- so that, for example, your Published or Unpublished
117	articles would revert to Pending Review -- if the source feed made any
118	upates to the item. This could make the Pending Review feature both
119	unreliable and also extremely frustrating to work with. The good news is
120	that this bug has since been fixed: if you manually update the status
121	of a post, it will no longer be reverted if or when the post is updated.
122
123	* BUGFIX: OCCASIONAL FATAL ERROR ON UPDATE ELIMINATED: Under certain
124	limited conditions (specifically, when both the title and the content of
125	a post to be updated are empty), an attempt to update the post would
126	result in a fatal error. This has been fixed.
127
128	* INTERFACE: "CONFIGURE SETTINGS" CONVENIENCE LINK ADDED TO CONFIRMATION
129	MESSAGE WHEN A NEW FEED IS ADDED: When you add a new subscription to
130	FeedWordPress, the message box that appears to confirm it now includes a
131	handy link to the feed's settings subpage, so that you can quickly set
132	up any special settings you may want to set up for the new feed, without
133	having to hunt through the list of all your other subscriptions to pick
134	out the new one.
135
136	* INTERFACE: SIMPLIFYING AND CLARIFYING AUTOMATIC UPDATES SETTINGS. I have
137	removed an interval setting for the cronless automatic updates which has
138	confused many FeedWordPress users. In past versions of FWP, when you
139	turned on automatic updates, you would be presented with a time interval
140	setting which controlled how often FeedWordPress would check for feeds
141	ready to be polled for updates. (That is, it DID NOT control how often
142	feeds would be polled; it controlled how often FeedWordPress would
143	check for feeds that had become ready to poll. The schedule on which
144	feeds became ready for polling was still controlled either by requests
145	encoded in elements within the feed itself, or else according to an
146	internal calculation within FeedWordPress, averaging out to about 1 hour,
147	if the feed did not include any scheduling request elements.) Since many
148	users very often (and understandably) confused the purpose of this
149	setting, and since the setting is for a feature that's actually very
150	unlikely to require any manual control by the user, I have removed the
151	setting; FeedWordPress now simply uses the default value of checking for
152	feeds to poll every 10 minutes.
153
154	* FEEDFINDER PERFORMANCE IMPROVEMENT: FeedWordPress's FeedFinder class
155	now uses `array_unique()` to make sure that it doesn't waste time
156	repeatedly iterating over and polling the same URI. Props to Camilo
157	(<http://projects.radgeek.com/2008/12/14/feedwordpress-20081214/#comment-20090122160414>).
158
159	Changes from 2008.1105 to 2008.1214
160	-----------------------------------
161
162	* WORDPRESS 2.7 COMPATIBILITY: FeedWordPress has been tested for
163	compatibility with the newly released WordPress 2.7. WordPress 2.7 has
164	deprecated the Snoopy library for HTTP requests, which caused a fatal
165	error for users who had not installed the MagpieRSS upgrade (or whose
166	installation of the MagpieRSS upgrade was overwritten by a recent update
167	of WordPress). FeedWordPress now handles things gracefully when Snoopy
168	is not immediately available.
169
170	* INTERFACE SPIFFED UP: Interface elements have been updated so that
171	FeedWordPress's management interface fits in more naturally with the
172	WordPress 2.7 interface (including a new logo and a number of small
173	interface tweaks).
174
175	* BUG WITH TAGS FOR SYNDICATED ARTICLES FIXED: Several users encountered a
176	bug with the option to add tags to all syndicated posts under
177	Syndication --> Settings -- if you told FeedWordPress to add more than
178	one tag to all syndicated posts, instead of doing so correctly, it would
179	add a single tag instead, whose name was composed of the names of all
180	the tags you asked it to add. This bug was the result of nothing more
181	dignified than a typographical error on my part. It has now been fixed.
182
183	* MORE INFORMATION AVAILABLE WHEN FEEDWORDPRESS CAN'T FIND A FEED: When
184	you enter a URL for a new syndication source, FeedWordPress uses a
185	simple feed-finding algorithm (originally based on Mark Pilgrim's
186	Universal Feed Finder) to try to determine whether the URL is the URL
187	for a feed, or, if the URL points to an ordinary website rather than to
188	a feed, whether there is a feed for that website. All well and good, but
189	if FeedWordPress failed to find a feed, for whatever reason, it would
190	typically return nothing more than a nasty little note to the effect of
191	"no feed found," without any explanation of what went wrong.
192	FeedWordPress now keeps track of error conditions from the HTTP
193	requests that it uses in the course of looking for the feed, and so may
194	be able to give you a bit more information about the nature of the
195	problem if something goes wrong.
196
197
198	Changes from 2008.1101 to 2008.1105
199	-----------------------------------
200
201	* INTERFACE RESTRUCTURING AND SYNDICATION --> AUTHORS PAGE: As a first
202	step towards modularizing and better organizing the user interface, a
203	new "Authors" subpage has been created under the Syndication menu, which
204	controls settings for syndicated authors, both at the global default
205	level and at level of individual syndicated feeds.
206
207	* BUG RELATED TO THE ATTRIBUTION OF POSTS TO THE WRONG AUTHOR FIXED: Some
208	users encountered an issue in which posts by different authors on
209	different blogs -- especially blogs generated by Blogger -- were
210	mistakenly attributed to a single author. The problem was caused by the
211	way in which FeedWordPress matches syndicated authors to user accounts
212	in the WordPress database: normally, if two feeds each list an author
213	with the same e-mail address, they are counted as being the same person.
214	Normally this works well, but it creates an issue in cases where
215	blogging software assigns a single anonymous e-mail address to users who
216	do not want their real e-mail address published. This is, for example,
217	what Blogger does (by giving all users a default e-mail address of
218	<noreply@blogger.com> if they don't want their own e-mail address
219	listed). FeedWordPress now allows the user to correct for this problem
220	with a couple of new settings under Syndication --> Authors, which
221	allow users to turn off e-mail based author matching for particular
222	addresses, or, if desired, to turn it off entirely. By default, e-mail
223	based author matching is still turned on, but disabled for a list of
224	known generic e-mail addresses. Right now, the "list" consists entirely
225	of <noreply@blogger.com>; if you know other addresses that should be
226	added, please [contact me](http://radgeek.com/contact) to let me know.
227
228	Please note that if you have already encountered this issue on your
229	blog, upgrading FeedWordPress will prevent it from re-occurring in the
230	future, but you still need to do two other things to fix the existing
231	problem on your blog.
232
233	First, for each feed where posts have been mis-attributed, you need to
234	change the existing author mapping rules to re-map a a syndicated
235	author's name to the proper target account. Go to **Syndication -->
236	Authors**, select the feed you want to change from the drop-down list,
237	and then change the settings under the "Syndicated Authors" section.
238	(You will probably need to select "will be assigned to a new user..." to
239	create a new user account with the appropriate name.)
240
241	Second, for each feed where posts have been mis-attributed, you need to
242	re-assign already-syndicated posts that were mis-attributed to the
243	correct author. You can do that from Syndication --> Authors by
244	using the author re-assignment feature, described below.
245
246	* AUTHOR RE-ASSIGNMENT FOR A PARTICULAR FEED: The author settings page
247	for each syndicated feed, under Syndication --> Authors, now
248	includes an section titled "Fixing mis-matched authors," which provides
249	an interface for re-assigning or deleting all posts attributed to a
250	particular author on a particular feed.
251
252	* SUPPORT FOR `<atom:source>` ELEMENT IN SYNDICATED FEEDS: Some feeds
253	(for example, those produced by FeedWordPress) aggregate content from
254	several different sources, and include information about the original
255	source of the post in an `<atom:source>` element. A new setting under
256	Syndication --> Options allows you to control what FeedWordPress
257	will report as the source of posts syndicated from aggregator feeds in
258	your templates and feeds: you can have FeedWordPress report that the
259	source of a post is the aggregator feed itself, or you can have it
260	report that the source of a post is the original source that the
261	aggregator originally syndicated the post from.
262
263	By default, FeedWordPress will report the aggregator, not the original
264	source, as the source of a syndicated item.
265
266	* LOAD BALANCING AND TIME LIMITING FEATURES FOR UPDATES: Some users have
267	encountered issues due to running up against PHP execution time limits
268	during the process of updating large syndicated feeds, or a very large
269	set of syndicated feeds. FeedWordPress now has a feature that allows you
270	to limit the total amount of time spent updating a feed, through the
271	"Time limit on updates" setting under Syndication --> Options. By
272	turning on this setting and adjusting the time limit to a low enough
273	figure to avoid your PHP installation's time-out setting. (PHP execution
274	time limits are usually in the vicinity of 30 seconds, so an update
275	time limit of 25 seconds or so should provide plenty of time for updates
276	while allowing a cushion of time for other, non-update-related functions
277	to do their work.)
278
279	If feed updates are interrupted by the time limit, FeedWordPress uses
280	some simple load balancing features to make sure that updates to other
281	feeds will not be blocked by the time-hogging feed, and will also make
282	sure that when the interrupted update is resumed, FeedWordPress will
283	skip ahead to resume processing items at the point at which it was
284	interrupted last time, so that posts further down in the feed will
285	eventually get processed, and not get blocked by the amount of time it
286	takes to process the items higher up in the feed.
287
288	* `guid` INDEX CREATION BUTTON: FeedWordPress frequently issues queries on
289	the `guid` column of the WordPress posts database (since it uses post
290	guid URIs to keep track of which posts it has syndicated). In very large
291	FeedWordPress installations, you can often significantly improve
292	performance by creating a database index on the `guid` column, but
293	normally you would need to poke around with MySQL or a tool like
294	phpMyAdmin to do this. FeedWordPress can now save you the trouble: to
295	create an index on the `guid` column, just go to
296	Syndication --> Options, and mash the button at the bottom of the
297	"Back End" section.
298
299	Changes from 2008.1030 to 2008.1101
300	-----------------------------------
301
302	* INTERFACE BUG THAT PREVENTED ADDING NEW SITES FIXED: The UI reforms in
303	FWP 2008.1030 unintentionally introduced a bug that prevents clean
304	installations of FeedWordPress from providing an input box for adding
305	new feeds to the list of syndicated feeds. This bug has been fixed.
306
307	Changes from 0.993 to 2008.1030
308	-------------------------------
309
310	* WORDPRESS 2.6 COMPATIBILITY: FeedWordPress should now be compatible with
311	WordPress 2.6, and should work more or less seamlessly with the new post
312	revision system. A bug which caused multiple new revisions to be created
313	for posts on certain feeds, regardless of whether or not the item had
314	been updated, has been fixed.
315
316	* INTERFACE IMPROVEMENTS: The user interface has been substantially
317	restyled to fit in better with the visual style of WordPress 2.5 and
318	2.6.
319
320	* YOUTUBE BUG FIXED: POSTS SYNDICATED THROUGH AN AUTOMATIC UPDATE ARE NO
321	LONGER STRIPPED OF `<OBJECT>` TAGS AND CERTAIN OTHER HTML ELEMENTS: Due
322	to the way that some versions of WordPress process posts that are
323	inserted into the database when no user is logged in, many users
324	experienced an issue where YouTube videos and other content using the
325	HTML `<object>` tag would be stripped out of posts that were syndicated
326	during an automatic update. (Posts that were syndicated through manual
327	updates from within the WordPress Dashboard were not affected, because
328	the issue does not arise when an update is executed under a logged-in
329	administrator's credentials.) This bug has now been fixed; YouTube
330	videos and other content using `<object>` tags should now appear
331	properly in syndicated posts, regardless of the way in which the post
332	was syndicated.
333
334	* AJAX BUGS FIXED: Bugs which blocked the normal operation of WordPress
335	2.5's AJAX interface elements when FeedWordPress was activated have been
336	fixed.
337
338	* TAG SUPPORT: A couple of features have been introduced to take advantage
339	of the tagging features in WordPress 2.3.x, 2.5.x, and 2.6.x. Now, when
340	unfamiliar categories are encountered for posts on a feed, you can
341	choose for FeedWordPress (1) to drop the category; (2) to drop the
342	category and to filter out any post that does not match at least one
343	familiar category; (3) to create a new category with that name, or,
344	now, you can also have FeedWordPress (4) create a new tag with that
345	name. This option can be set site-wide under Syndication --> Options,
346	or it can be set on a feed-by-feed basis in a feed's Edit screen.
347
348	In addition, you can now set particular tags to apply to all incoming
349	syndicated posts, under Syndication --> Options, or you can set tags
350	to apply to all incoming syndicated posts from a particular feed in that
351	feed's Edit screen.
352
353	* FORMATTING FILTERS: There is a new option available under Syndication ->
354	Options which allows users to choose whether or not to expose syndicated
355	posts to being altered by formatting filters. By default, FeedWordPress
356	has always protected syndicated posts (which are already in display-ready
357	HTML when they are syndicated) from being reformatted by formatting
358	filters. However, this approach means that certain plugins which depend
359	on formatting filters (for example, to add "Share This" bars or relevant
360	links to the end of a post) are blocked from working on any syndicated
361	posts. If you want to use one of these plugins together with
362	FeedWordPress, you can now do so by changing the "Formatting Filters"
363	setting from "Protect" to "Expose."
364
365	* `<atom:source>` ELEMENTS NOW INCLUDED IN ATOM FEED: Atom 1.0 provides
366	a standard method for aggregators to indicate information about the original source of
367	a syndicated post, using the `<atom:source>` element. FeedWordPress now
368	introduces standard `<atom:source>` elements including the title, homepage, and
369	feed URI of the source from which a syndicated post was syndicated. Cf.
370	<http://www.atomenabled.org/developers/syndication/atom-format-spec.php#element.source>
371
372	* MODULARIZATION OF CODE: The code for different elements of FeedWordPress
373	has been broken out into several modules for easier inspection,
374	documentation, and maintenance of the code.
375
376	* VERSIONING SCHEME CHANGED: FeedWordPress's feature set has proven stable
377	enough that it can now be removed from beta status; a good thing, since
378	I was very quickly running out of version numbers to use. New releases
379	of FeedWordPress will have version numbers based on the date of their
380	release.
381
382	Changes from 0.992 to 0.993
383	---------------------------
384
385	* WORDPRESS 2.5.1 COMPATIBILITY: FeedWordPress should now be compatible
386	with WordPress 2.5.1.
387
388	* WORDPRESS 2.5 INTERFACE IMPROVEMENTS: FeedWordPress's Dashboard
389	interface has undergone several cosmetic changes that should help it
390	integrate better with the WordPress Dashboard interface in WordPress
391	version 2.5.x.
392
393	* SYNDICATED POSTS CAN BE MARKED AS "PENDING REVIEW": WordPress 2.3 users
394	can now take advantage of WordPress's new "Pending Review" features for
395	incoming syndicated posts. Posts marked as "Pending Review" are not
396	published immediately, but are marked as ready to be reviewed by an
397	Administrator or Editor, who can then choose to publish the post or
398	hold it back. If you want to review syndicated posts from a particular
399	feed, or from all feeds, before they are posted, then use
400	Syndication --> Syndicated Sites --> Edit or Syndication --> Options to
401	change the settings for handling new posts.
402
403	* AWARE OF NEW URI FOR del.icio.us FEEDS: Previous releases of
404	FeedWordPress already automatically split del.icio.us tags up
405	appropriately appropriately when generating categories. (del.icio.us
406	feeds smoosh all the tags into a single `<dc:subject>` element,
407	separated by spaces; FeedWordPress un-smooshes them into multiple
408	categories by separating them at whitespace.) Unfortunately, del.icio.us
409	recently broke the existing behavior by changing host names for their
410	feeds from del.icio.us to feeds.delicious.com. Version 0.993 accounts
411	for the new host name and un-breaks the tag splitting.
412
413	Changes from 0.991 to 0.992
414	---------------------------
415	* AUTHOR RE-MAPPING: FeedWordPress now offers considerable control over
416	how author names on a feed are translated into usernames within the
417	WordPress database. When a post by an unrecognized author comes in,
418	Administrators can now specify any username as the default username to
419	assign the post to by setting the option in Syndication --> Options
420	(formerly FeedWordPress only allowed you to assign such posts to user
421	#1, the site administrator). Administrators can also create re-mapping
422	rules for particular feeds (under Syndication --> Syndicated Sites -->
423	Edit), so that (for example) any posts attributed to "Administrator"
424	on the feed <http://praxeology.net/blog/feed/> will be assigned to
425	a user named "Roderick T. Long," rather than a user named
426	"Administrator." These settings also allow administrators to filter out
427	posts by particular users, and to control what will happen when
428	FeedWordPress encounters a post by an unrecognized user on that
429	particular feed.
430
431	* BUG RELATED TO URIS CONTAINING AMPERSAND CHARACTERS FIXED: A bug in
432	WordPress 2.x's handling of URIs in Blogroll links created problems for
433	updating any feeds whose URIs included an ampersand character, such as
434	Google News RSS feeds and other feeds that have multiple parameters
435	passed through HTTP GET. If you experienced this bug, the most likely
436	effect was that FeedWordPress simply would not import new posts from a
437	feed when instructred to do so, returning a "0 new posts" response. In
438	other cases, it might lead to unpredictable results from feed updates,
439	such as importing posts which were not contained in the feed being
440	syndicated, but which did appear elsewhere on the same website. This bug
441	has, hopefully, been resolved, by correcting for the bug in WordPress.
442
443	Changes from 0.99 to 0.991
444	--------------------------
445	* WORDPRESS MU COMPATIBILITY: FeedWordPress should now be compatible with
446	recent releases of WordPress MU. Once FeedWordPress is made available
447	as a plugin, each individual blog can choose to activate FeedWordPress
448	and syndicate content from its own set of contributors.
449
450	* DISPLAY OF MAGPIE WARNINGS: A number of MagpieRSS warnings or error
451	messages that were displayed when performing an automatic update are
452	no longer displayed, unless debugging parameters have been explicitly
453	enabled.
454
455	* BUG RELATED TO INTERNATIONAL CHARACTERS IN AUTHOR NAMES FIXED: Due to a
456	subtle incompatability between the way that FeedWordPress generated new
457	user information, and the way that WordPress 2.0 and later added new
458	authors to the database, FeedWordPress might end up creating duplicate
459	authors, or throwing a critical error message, when it encountered
460	authors whose names included international characters. This
461	incompatability has now been fixed; hopefully, authors with
462	international characters in their names should now be handled properly.
463
464	* `<media:content>` BUG IN MAGPIERSS FIXED: A bug in MagpieRSS's handling
465	of namespaced elements has been fixed. Among other things, this bug
466	caused items containing a Yahoo MediaRSS `<media:content>` element (such
467	as many of the feeds produced by wordpress.com) to be represented
468	incorrectly, with only a capital "A" where the content of the post
469	should have been. Feeds containing `<media:content>` elements should now
470	be syndicated correctly.
471
472	* update_feedwordpress PARAMETER: You can now use an HTTP GET parameter
473	(`update_feedwordpress=1`) to request that FeedWordPress poll its feeds
474	for updates. When used together with a crontab or other means of
475	scheduling tasks, this means that you can keep your blog automatically
476	updated on a regular schedule, even if you do not choose to use the
477	cron-less automatic updates option.
478
479	* Some minor interface-related bugs were also fixed.
480
481
482	Changes from 0.981 to 0.99
483	--------------------------
484	Version 0.99 adds several significant new features, fixes some bugs, and
485	provides compatability with WordPress 2.2.x and 2.3.x.
486
487	* WORDPRESS 2.2 AND 2.3 COMPATIBILITY: FeedWordPress should now be
488	compatible with WordPress version 2.2 and the upcoming WordPress
489	version 2.3. In particular, it has been tested extensively against
490	WordPress 2.2.3 and WordPress 2.3 Release Candidate 1.
491
492	* AUTOMATIC UPDATES WITHOUT CRON: FeedWordPress now allows you to
493	automatically schedule checks for new posts without using external task
494	scheduling tools such as cron. In order to enable automatic updates, go
495	to Syndication --> Options and set "Check for new posts" to
496	"automatically." For details, see "Automatic Feed Updates" in
497	README.text.
498
499	An important side-effect of the changes to the update system is that if
500	you were previously using the cron job and the `update-feeds.php` script
501	to schedule updates, you need to change your cron set-up. The old
502	`update-feeds.php` script no longer exists. Instead, if you wish to use
503	a cron job to guarantee updates on a particular schedule, you should
504	have the cron job fetch the front page of your blog (for example, by
505	using `curl http://www.zyx.com/blog/ > /dev/null`) instead of activating
506	the `update-feeds.php` script. If automatic updates have been enabled,
507	fetching the front page will automatically trigger the update process.
508
509	* INTERFACE REORGANIZATION: All FeedWordPress functions are now located
510	under a top-level "Syndication" menu in the WordPress Dashboard. To
511	manage the list of syndicated sites, manually check for new posts on
512	one or more feeds, or syndicate a new site, you should use the main page
513	under Syndication. To change global settings for FeedWordPress,
514	you should use Syndication --> Options.
515
516	* FILE STRUCTURE REORGANIZATION: Due to a combination of changing styles
517	for FeedWordPress plugins and lingering bugs in the FeedWordPress admin
518	menu code, the code for FeedWordPress is now contained in two different
519	PHP files, which should be installed together in a subdirectory of your
520	plugins directory named `feedwordpress`. (See README.text for
521	installation and upgrade instructions relating to the change.)
522
523	* MULTIPLE CATEGORIES SETTING: Some feeds use non-standard methods to
524	indicate multiple categories within a single category element. (The most
525	popular site to do this is del.icio.us, which separates tags with a
526	space.) FeedWordPress now allows you to set an optional setting, for any
527	feed which does this, indicating the character or characters used to
528	divide multiple categories, using a Perl-compatible regular expression.
529	(In the case of del.icio.us feeds, FeedWordPress will automatically use
530	\s for the pattern without your having to do any further configuration.)
531	To turn this setting on, simply use the "Edit" link for the feed that
532	you want to turn it on for.
533
534	* REGULAR EXPRESSION BUG FIXED: Eliminated a minor bug in the regular
535	expressions for e-mail addresses (used in parsing RSS `author`
536	elements), which could produce unsightly error messages for some users
537	parsing RSS 2.0 feeds.
538
539	* DATE / UPDATE BUG FIXED: A bug in date handling was eliminated that may
540	have caused problems if any of (1) WordPress, or (2) PHP, or (3) your
541	web server, or (4) your MySQL server, has been set to use a different
542	time zone from the one that any of the others is set to use. If
543	FeedWordPress has not been properly updating updated posts, or has been
544	updating posts when there shouldn't be any changes for the update, this
545	release may solve that problem.
546
547	* GOOGLE READER BUGS FIXED: A couple of bugs that made it difficult for
548	FeedWordPress to interact with Google Reader public feeds have been
549	fixed. Firstly, if you encountered an error message reading "There was a
550	problem adding the newsfeed. [SQL: ]" when you tried to add the feed,
551	the cause of this error has been fixed. Secondly, if you succeeded in
552	getting FeedWordPress to check a Google Reader feed, only to find that
553	the title of posts had junk squashed on to the end of them, that bug
554	has been fixed too. To fix this bug, you must install the newest version
555	of the optional MagpieRSS upgrade.
556
557	* FILTER PARAMETERS: Due to an old, old bug in WordPress 1.5.0 (which was
558	what was available back when I first wrote the filter interface),
559	FeedWordPress has traditionally only passed one parameter to
560	syndicated_item and syndicated_post filters functions -- an array
561	containing either the Magpie representation of a syndicated item from
562	the feed, or the database representation of a post about to be inserted
563	into the WordPress database. If you needed information about the feed
564	that the item came from, this was accessible only through a pair of
565	global variables, $fwp_channel and $fwp_feedmeta.
566
567	Since it's been a pretty long time since WordPress 1.5.0 was in
568	widespread usage, I have gone ahead and added an optional second
569	parameter to the invocation of the syndicated_item and syndicated_post
570	filters. If you have written a filter for FeedWordPress that uses either
571	of these hooks, you can now register that filter to accept 2 parameters.
572	If you do so, the second parameter will be a SyndicatedPost object,
573	which, among other things, allows you to access information about the
574	feed from which an item is syndicated using the $post->feed and the
575	$post->feedmeta elements (where $post is the name of the second
576	parameter).
577
578	NOTE THAT THE OLD GLOBAL VARIABLES ARE STILL AVAILABLE, for the time
579	being at least, so existing filters will not break with the upgrade.
580	They should be considered deprecated, however, and may be eliminated in
581	the future.
582
583	* FILTER CHANGE / BUGFIX: the array that is passed as the first argument
584	syndicated_post filters no longer is no longer backslash-escaped for
585	MySQL when filters are called. This was originally a bug, or an
586	oversight; the contents of the array should only be escaped for the
587	database after they have gone through all filters. IF YOU HAVE WRITTEN
588	ANY syndicated_post FILTERS THAT PRESUME THE OLD BEHAVIOR OF PASSING IN
589	STRINGS THAT ARE ALREADY BACKSLASH-ESCAPED, UPDATE YOUR FILTERS
590	ACCORDINGLY.
591
592	* OTHER MINOR BUGFIXES AND INTERNAL CHANGES: The internal architecture of
593	FeedWordPress has been significantly changed to make the code more
594	modular and clean; hopefully this should help reduce the number of
595	compatibility updates that are needed, and make them easier and quicker
596	when they are needed.
597
598	Changes from 0.98 to 0.981
599	--------------------------
600	Version 0.981 is a narrowly targeted bugfix and compatibility release, whose
601	main purpose is to resolve a major outstanding problem: the incompatibility
602	between version 0.98 of WordPress and the recently released WordPress 2.1.
603
604	* WORDPRESS 2.1 COMPATIBILITY: FeedWordPress is now compatible with
605	WordPress 2.1, as well as retaining its existing support for WordPress
606	2.0 and 1.5. Incompatibilities that resulted in database warnings, fatal
607	errors, and which prevented FeedWordPress from syndicating new posts,
608	have been eliminated.
609
610	* RSS-FUNCTIONS.PHP RENAMED TO RSS.PHP: if you use the upgraded MagpieRSS
611	replacement that's included with FeedWordPress, be sure to note that
612	there are now two files to upload from the `OPTIONAL/wp-includes`
613	subdirectory in order to carry out the upgrade: rss-functions.php and
614	rss.php. It is necessary to upload both files, due to a change in
615	the file naming scheme in WordPress 2.1, and it is necessary to do so
616	whether you are using WordPress 2.1 or not. If you only upload the
617	`rss-functions.php` file as in previous installations you will not have
618	a working copy of MagpieRSS; the rss.php file contains the actual code.
619
620	* DATE BUG AFFECTING SOME PHP INSTALLATIONS RESOLVED: due to a subtle bug
621	in parse_w3cdtf(), some installations of PHP encountered problems with
622	FeedWordPress's attempt to date posts, which would cause some new posts
623	on Atom feeds to be dated as if they had apppeared in 1969 or 1970
624	(thus, effectively, never appearing on front page at all). This bug in
625	the date handling should now be fixed.
626
627	* PHP <?=...?> SHORT FORM ELIMINATED: some installations of PHP do not
628	allow the <?=...?> short form for printing PHP values, which was used
629	extensively in the FeedWordPress interface code. Since this could cause
630	fatal errors for users with the wrong installation of PHP, the short
631	form has been replaced with full PHP echo statements, and is no longer
632	used in FeedWordPress.
633
634	* BETTER USER INTERFACE INTEGRATION WITH WORDPRESS 2.x: Some minor changes
635	have been made to help the FeedWordPress interface pages blend in better
636	with the user interface when running under WordPress 2.x.
637
638	* GLOBAL CATEGORIES BUG RESOLVED: a bug that prevented some users from
639	setting one or more categories to apply to syndicated posts from all
640	feeds (using the checkbox interface under Options --> Syndication) has
641	been resolved.
642
643	Changes from 0.97 to 0.98
644	--------------------------
645
646	* WORDPRESS 2.0 COMPATIBILITY: This is a narrowly-targeted release to
647	solve a major outstanding problem. FeedWordPress is now compatible with
648	both WordPress 1.5 and WordPress 2.0. Incompatibilities that caused
649	fatal SQL errors, and a more subtle bug with off-kilter counts of posts
650	under a given category, have been resolved. FeedWordPress tests for
651	database schema using the global $wp_db_version variable (if null, then
652	we presume that we're dealing with WordPress 1.5).
653
654	NOTE: I have not fully tested FeedWordPress with WordPress 2.0.
655	Further testing may reveal more bugs. However, you should now be able
656	to get at least basic FeedWordPress functionality up and running.
657
658	* AUTHOR MATCHING: FeedWordPress tests several fields to see if it can
659	identify the author of the post as a user already in the WordPress user
660	database. In previous versions, it tested the user login, the nickname,
661	and tested for "aliases" listed in the Profile (see documentation). FWP
662	now also matches authors on the basis of e-mail address (if an e-mail
663	address is present). This is particularly helpful for formats such as
664	RSS 2.0, in which authors are primarily identified by e-mail addresses.
665
666	Changes from 0.96 to 0.97
667	-------------------------
668
669	* INSTALLATION PROCEDURE: Some of the changes between 0.96 and 0.97
670	require upgrades to the meta-data stored by FeedWordPress to work
671	properly. Thus, if you are upgrading from 0.96 or earlier to 0.97, most
672	FeedWordPress operations (including updates and template functions)
673	WILL BE DISABLED until you run the upgrade procedure. Fortunately,
674	running the upgrade procedure is easy: just go to either Options -->
675	Syndication or Links --> Syndicated in the WordPress Dashboard and press
676	the button.
677
678	* FEED FORMAT SUPPORT: Support has been added for the Atom 1.0 IETF
679	standard. Several other elements are also newly supported
680	(dcterms:created, dcterms:issued, dcterms:modified, dc:identifier,
681	proper support for the RSS 2.0 guid element, the RSS 2.0 author element,
682	the use of Atom author or Dublin Core dc:creator constructs at the feed
683	level to identify the author of individual items, etc.)
684
685	N.B.: full support of several Atom 1.0 features, such as categories
686	and enclosures, requires you to install the optional rss-functions.php
687	upgrade in your wp-includes directory.
688
689	* BUG FIX: Running `update-feeds.php` from command line or crontab
690	returned "I don't syndicate..." errors. It turns out that WordPress
691	sometimes tramples on the internal PHP superglobals that I depended on
692	to determine whether or not the script was being invoked from the
693	command line. This has been fixed (the variables are now checked
694	before WordPress can trample them). Note that `update-feeds.php` has
695	been thoroughly overhauled anyway; see below for details.
696
697	* BUG FIX: Duplicate categories or author names. Fixed two bugs that could
698	create duplicate author and/or category names when the name contained
699	either (a) certain international characters (causing a mismatch between
700	MySQL and PHP's handling of lowercasing text), or (b) characters that
701	have a special meaning in regular expressions (causing MySQL errors when
702	looking for the author or category due to regexp syntax errors). These
703	should now be fixed thanks to careful escaping of names that go into
704	regular expressions and careful matching of lowercasing functions
705	(comparing results from PHP only to other results from PHP, and results
706	from MySQL only to other results from MySQL).
707
708	* BUG FIX: Items dated December 31, 1969 should appear less often. The
709	function for parsing W3C date-time format dates that ships with
710	MagpieRSS can only correctly parse fully-specified dates with a
711	fully-specified time, but valid W3C date-time format dates may omit the
712	time, the day of the month, or even the month. Some feeds in the wild
713	date their items with coarse-grained dates, so the optional
714	`rss-functions.php` upgrade now includes a more flexible parse_w3cdtf()
715	function that will work with both coarse-grained and fully-specified
716	dates. (If parts of the date or the time are omitted, they are filled in
717	with values based on the current time, so '2005-09-10' will be dated to
718	the current time on that day; '2004' will be dated to this day and time
719	one year ago.
720
721	N.B.: This fix is only available in the optional `rss-functions.php`
722	upgrade.
723
724	* BUG FIX: Evil use of HTTP GET has been undone. The WordPress interface
725	is riddled with inappropriate (non-idempotent) uses of HTTP GET queries
726	(ordinary links that make the server do something with significant
727	side-effects, such as deleting a post or a link from the database).
728	FeedWordPress did some of this too, especially in places where it aped
729	the WordPress interface (e.g. the "Delete" links in Links -->
730	Syndicated). That's bad business, though. I've changed the interface so
731	that all the examples of improper side-effects that I can find now
732	require an HTTP POST to take effect. I think I got pretty much
733	everything; if there's anything that I missed, let me know.
734
735	Further reading: [Sam Ruby 2005-05-06: This Stuff Matters](http://www.intertwingly.net/blog/2005/05/06/This-Stuff-Matters)
736
737	* BUG FIX: Categories applied by `cats` setting should no longer prevent
738	category-based filtering from working. In FeedWordPress, you can (1)
739	apply certain categories to all syndicated posts, or all posts from
740	a particular feed; and (2) filter out all posts that don't match one
741	of the categories that are already in the WordPress database (allowing
742	for simple category-based filtering; just load up WordPress with the
743	categories you want to accept, and then tell FeedWordPress not to create
744	new ones). However, the way that (1) and (2) were implemented meant that
745	you couldn't effectively use them together; once you applied a known
746	category to all syndicated posts from a particular feed, it meant that
747	they'd have at least one familiar category (the category or categories
748	you were applying), and that would get all posts past the filter no
749	matter what categories they were originally from.
750
751	Well, no longer. You can still apply categories to all syndicated posts
752	(using either Syndication --> Options, or the feed-level settings under
753	Links --> Syndicated). But these categories are not applied to the post
754	until after it has already passed by the "familiar categories" filter.
755	So now, if you want, you can do category filtering and then apply as
756	many categories as you please to all and only posts that pass the filter.
757
758	* BUG FIX: Other minor typos and HTML gaffes were fixed along the way.
759
760	* PERFORMANCE: get_feed_meta() no longer hits the database for information
761	on every call; it now caches link data in memory, so FeedWordPress only
762	goes to the database once for each syndicated link. This may
763	substantially improve performance if your database server resources
764	are tight and your templates make a lot of use of custom settings from
765	get_feed_meta().
766
767	* API CHANGE: Link ID numbers, rather than RSS URIs, are now used to
768	identify the feed from which a post is syndicated when you use template
769	functions such as get_feed_meta(). The practical upshot of this is you
770	can switch feeds, or change the feed address for a particular syndicated
771	site, without breaking your templates for all the posts that were
772	syndicated from the earlier URI.
773
774	* API CHANGE: if you have plugins or templates that make use of the
775	get_feed_meta() function or the $fwp_feedmeta global, note that the
776	data formerly located under the `uri` and `name` fields is now located
777	under the `link/uri` field and the `link/name` field, respectively. Note
778	also that you can access the link ID number for any given feed under the
779	global $fwp_feedmeta['link/id'] (in plugins) or
780	get_feed_meta('link/id') (in a template in post contexts).
781
782	* FEATURE: the settings for individual feeds can now be edited using a
783	humane interface (where formerly you had to tweak key-value pairs in the
784	Link Notes section). To edit settings for a feed, pick the feed that you
785	want under Links --> Syndicated and click the Edit link.
786
787	* FEATURE: The "Unsubscribe" button (formerly "Delete") in Links -->
788	Syndicated now offers three options for unsubscribing from a feed: (1)
789	turning off the subscription without deleting the feed data or affecting
790	posts that were syndicated from the feed (this works by setting the Link
791	for the feed as "invisible"); (2) deleting the feed data and all of the
792	posts that were syndicated from the feed; or (3) deleting the feed data
793	and keeping the posts that were syndicated from the feed
794	setting the Link to "Invisible" (meaning that it will not be displayed
795	in lists of the site links on the front page, and it won't be checked
796	for updates; (2) deleting the Link and all of the posts that were
797	syndicated from its feed; or (3) deleting the feed data but keeping the
798	posts that were syndicated (which will henceforward be treated as if
799	they were local rather than syndicated posts). (Note that (1) is usually
800	the best option for aggregator sites, unless you want to clean up the
801	results of an error or a test.)
802
803	* FEATURE / BUG FIX: If you have been receiving mysterious "I don't
804	syndicate...", or "(local) HTTP status code was not 200", or "(local)
805	transport error - could not open socket", or "parse error - not well
806	formed" errors, then this update may solve your problems, and if it does
807	not solve them, it will at least make the reasons for the problems
808	easier to understand. That's because I've overhauled the way that
809	FeedWordPress goes about updating feeds.
810
811	If you use the command-line PHP scripting method to run scheduled
812	updates, then not much should change for you, except for fewer
813	mysterious errors. If you have done updates by sending periodic HTTP
814	requests to <http://your-blog.com/path/wp-content/update-feeds.php>,
815	then the details have changed somewhat; mostly in such a way as to make
816	things easier on you. See the README file or online documentation on
817	Staying Current for the details.
818
819	* FEATURE: FeedWordPress now features a more sophisticated system for
820	timed updates. Instead of polling every subscribed feed for updates
821	each time `update-feeds.php` is run, FeedWordPress now keeps track of
822	the last time it polled each feed, and only polls them again after a
823	certain period of time has passed. The amount of time is normally set
824	randomly for each feed, in a period between 30 minutes and 2 hours (so
825	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
826	directly by the feed, which brings us to ...
827
828	* FEATURE: FeedWordPress now respects the settings in the `ttl` and
829	Syndication Module RSS elements. Feeds with these elements set will not
830	be polled any more frequently than they indicate with these feeds unless
831	the user manually forces FeedWordPress to poll the feed (see Links -->
832	Syndicated --> Edit settings).
833
834	Changes from 0.95 to 0.96
835	-------------------------
836
837	* FEATURE: support has been added for enclosures in RSS 2.0 and Atom
838	0.6+ newsfeeds. WordPress already supports adding enclosures to an
839	item; FeedWordPress merely gets the information on the enclosure
840	from the feed it is syndicating and plugs that information directly
841	into the WordPress database so that (among other things) that post
842	will have its enclosure listed in your blog's RSS 2 newsfeed.
843
844	Note that enclosure support requires using the optional MagpieRSS
845	upgrade (i.e., replacing your `wp-includes/rss-functions.php` with
846	`OPTIONAL/wp-includes/rss-functions.php` from the FWP archive)
847
848	* FEATURE: for completeness's sake, there is now a feed setting,
849	`hardcode url`, that allows you to set the URI for the front page
850	of a contributor's website manually (that is, prevent it from being
851	automatically updated from the feed channel link on each update). To
852	set the URI manually, put a line like this in the Link Notes section
853	of a feed:
854
855	hardcode url: yes
856
857	You can also instruct FeedWordPress to use hardcoded URIs by default
858	on all feeds using Options --> Syndication
859
860	* FEATURE: by default, when FeedWordPress finds new syndicated posts,
861	it (1) publishes them immediately, (2) turns comments off, and (3)
862	turns trackback / pingback pings off. You can now alter all three
863	default behaviors (e.g., to allow pings on syndicated posts, or to
864	send newly-syndicated posts to the draft pile for moderation) using
865	Options --> Syndication
866
867
868	Changes from 0.91 to 0.95
869	-------------------------
870
871	* BUG FIX: Fixed an obscure bug in the handling of categories:
872	categories with trailing whitespace could cause categories with
873	duplicate names to be created. This no longer happens. While I was
874	at it I tightened up the operation of
875	FeedWordPress::lookup_categories() a bit in general.
876
877	* FEATURE DEPRECATED: the feed setting `hardcode categories` is now
878	deprecated in favor of `unknown categories` (see below), which
879	allows you to strip off any syndication categories not already in
880	your database using `unknown categories: default` or `unknown
881	categories: filter`. If you have `hardcode categories: yes` set on a
882	feed, this will be treated as `unknown categories: default` (i.e.,
883	no new categories will be added, but if a post doesn't match any of
884	the categories it will be added in the default category--usually
885	"Uncategorized" or "General").
886
887	* FEATURE: You can now set global defaults as to whether or not
888	FeedWordPress will update the Link Name and Link Description
889	settings for feeds automatically from the feed title and feed
890	tagline. (By default, it does, as it has in past versions.) Whether
891	this behavior is turned on or off, you can still override the
892	default behavior using feed settings of `hardcode name: yes`,
893	`hardcode name: no`, `hardcode description: yes`, or `hardcode
894	description: no`.
895
896	* FEATURE: Users can now provide one or several "aliases" for an
897	author, just as they can for a category. For example, to make
898	FeedWordPress treat posts by "Joseph Cardinal Ratzinger" and "Pope
899	Benedict XVI" as by the same author, edit the user profile for Pope
900	Benedict XVI and add a line like this to the "User profile" field:
901
902	a.k.a.: Joseph Cardinal Ratzinger
903
904	You can add several aliases, each on a line by itself. You can also
905	add any other text you like to the Profile without interfering with
906	the aliases.
907
908	* FEATURE: Users can now choose how to handle syndicated posts that
909	are in unfamiliar categories or by unfamiliar authors (i.e.,
910	categories or authors whose names are not yet in the WordPress
911	database). By default, FeedWordPress will (as before) create a new
912	category (or new author) and use it for the current post and any
913	future posts. This behavior can be changed, either for all feeds or
914	for one or another particular feed.
915
916	There are now three different options for an unfamiliar author: (1)
917	FeedWordPress can create a new author account and attribute the
918	syndicated post to the new account; (2) FeedWordPress can attribute
919	the post to an author if the author's name is familiar, and to a
920	default author (currently, this means the Site Administrator
921	account) if it is not; (3) FeedWordPress can drop posts by
922	unfamiliar authors and syndicate only posts by authors who are
923	already in the database.
924
925	There are, similarly, two different options for an unfamiliar
926	category: (1) FeedWordPress can create new categories and place the
927	syndicated post in them; (2) FeedWordPress can drop the unfamiliar
928	categories and place syndicated posts only in categories that it is
929	already familiar with. In addition, FeedWordPress 0.95 lets you
930	choose whether posts that are in no familiar categories should be
931	syndicated (and placed in the default category for the blog) or
932	simply dropped.
933
934	You can set the default behavior for both authors and categories
935	using the settings in Options --> Syndication. You can also set
936	different behavior for specific feeds by adding the `unfamiliar
937	author` and / or `unfamiliar categories` settings to the Link Notes
938	section of a feed:
939
940	unfamiliar author: (create\|default\|filter)
941	unfamiliar categories: (create\|default\|filter)
942
943	A setting of `unfamiliar author: create` will make FeedWordPress
944	create new authors to match unfamiliar author names *for this feed
945	alone*. A setting of `unfamiliar author: default` will make it
946	assign posts from unfamiliar authors to the default user account. A
947	setting of `unfamiliar author: filter` will cause all posts (from
948	this feed alone) to be dropped unless they are by an author already
949	listed in the database. Similiarly, `unfamiliar categories: create`
950	will make FeedWordPress create new categories to match unfamiliar
951	category names for this feed alone; `unfamiliar categories:
952	default` will cause it to drop any unfamiliar category names; and
953	`unfamiliar categories: filter` will cause it to both drop any
954	unfamiliar category names and to only syndicate posts that are
955	placed in one or more familiar categories.
956
957	These two new features allow users to do some coarse-grained
958	filtering without having to write a PHP filter. Specifically, they
959	offer an easy way for you to filter feeds by category or by author.
960	Suppose, for example, that you only wanted to syndicate posts that
961	your contributors place in the "Llamas" category. You could do so by
962	setting up your installation of WordPress so that the only category
963	in the database is "Llamas," and then use Options --> Syndication to
964	set "Unfamiliar categories" to "don't create new categories and
965	don't syndicate posts unless they match at least one familiar
966	category". Now, when you update, only posts in the "Llamas" category
967	will be syndicated by FeedWordPress.
968
969	Similarly, if you wanted to filter one particular feed so that only
970	posts by (for example) the author "Earl J. Llama" were syndicated to
971	your site, you could do so by creating a user account for Earl J.
972	Llama, then adding the following line to the settings for the feed
973	in Link Notes:
974
975	unfamiliar author: filter
976
977	This will cause any posts from this feed that are not authored by
978	Earl J. Llama to be discarded, and only the posts by Earl J. Llama
979	will be syndicated. (If the setting is used on one specific feed, it
980	will not affect how posts from other feeds are syndicated.)
981
982