feedwordpress / ChangeLog.text

ChangeLog.text in FeedWordPress 2009.1112, at ChangeLog.text

1,031 lines 57.1 KB

Raw Download Zip

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