feedwordpress / readme.txt

readme.txt in FeedWordPress 2011.0602, at readme.txt

1,725 lines 93.8 KB

Raw Download Zip

1	=== FeedWordPress ===
2	Contributors: Charles Johnson
3	Donate link: http://feedwordpress.radgeek.com/
4	Tags: syndication, aggregation, feed, atom, rss
5	Requires at least: 3.0
6	Tested up to: 3.1.3
7	Stable tag: 2011.0602
8
9	FeedWordPress syndicates content from feeds you choose into your WordPress weblog.
10
11	== Description ==
12
13	* Author: [Charles Johnson](http://radgeek.com/contact)
14	* Project URI: <http://projects.radgeek.com/feedwordpress>
15	* License: GPL 2. See License below for copyright jots and tittles.
16
17	FeedWordPress is an Atom/RSS aggregator for WordPress. It syndicates content
18	from feeds that you choose into your WordPress weblog; if you syndicate several
19	feeds then you can use WordPress's posts database and templating engine as the
20	back-end of an aggregation ("planet") website. It was developed, originally,
21	because I needed a more flexible replacement for [Planet][]
22	to use at [Feminist Blogs][].
23
24	[Planet]: http://www.planetplanet.org/
25	[Feminist Blogs]: http://feministblogs.org/
26
27	FeedWordPress is designed with flexibility, ease of use, and ease of
28	configuration in mind. You'll need a working installation of WordPress or
29	WordPress MU (version [3.0] or later), and also FTP or SFTP access to your web
30	host. The ability to create cron jobs on your web host is helpful but not
31	required. You don't need to tweak any plain-text configuration files and you
32	don't need shell access to your web host to make it work. (Although, I should
33	point out, web hosts that don't offer shell access are bad web hosts.)
34
35	[WordPress]: http://wordpress.org/
36	[WordPress MU]: http://mu.wordpress.org/
37	[3.0]: http://codex.wordpress.org/Version_3.0
38
39	== Installation ==
40
41	To use FeedWordPress, you will need:
42
43	* an installed and configured copy of [WordPress][] or [WordPress MU][]
44	(version 3.0 or later).
45
46	* FTP, SFTP or shell access to your web host
47
48	= New Installations =
49
50	1. Download the FeedWordPress installation package and extract the files on
51	your computer.
52
53	2. Create a new directory named `feedwordpress` in the `wp-content/plugins`
54	directory of your WordPress installation. Use an FTP or SFTP client to
55	upload the contents of your FeedWordPress archive to the new directory
56	that you just created on your web host.
57
58	3. Log in to the WordPress Dashboard and activate the FeedWordPress plugin.
59
60	4. Once the plugin is activated, a new Syndication section should
61	appear in your WordPress admin menu. Click here to add new syndicated
62	feeds, set up configuration options, and determine how FeedWordPress
63	will check for updates. For help, see the [FeedWordPress Quick Start][]
64	page.
65
66	[FeedWordPress Quick Start]: http://feedwordpress.radgeek.com/wiki/quick-start
67
68	= Upgrades =
69
70	To upgrade an existing installation of FeedWordPress to the most recent
71	release:
72
73	1. Download the FeedWordPress installation package and extract the files on
74	your computer.
75
76	2. Upload the new PHP files to `wp-content/plugins/feedwordpress`,
77	overwriting any existing FeedWordPress files that are there.
78
79	3. Log in to your WordPress administrative interface immediately in order
80	to see whether there are any further tasks that you need to perform
81	to complete the upgrade.
82
83	4. Enjoy your newer and hotter installation of FeedWordPress
84
85	== Using and Customizing FeedWordPress ==
86
87	FeedWordPress has many options which can be accessed through the WordPress
88	Dashboard, and a lot of functionality accessible programmatically through
89	WordPress templates or plugins. For further documentation of the ins and
90	outs, see the documentation at the [FeedWordPress project homepage][].
91
92	[FeedWordPress project homepage]: http://feedwordpress.radgeek.com/
93
94	== Changelog ==
95
96	= 2011.0602 =
97
98	* WP 3.1.3 COMPAT / BUGFIX: WHITESPACE IN GUIDS NO LONGER PRODUCES DUPLICATE
99	POSTS. The work-around for handling filtered URIs in guid elements has now
100	been extended to handle URIs that were filtered because of leading or
101	trailing whitespace, in addition to URIs that were filtered because of
102	unapproved schemes.
103
104	* WP 3.1.3 COMPAT / BUGFIX: RELATIVE URLS IN GUIDS NO LONGER PRODUCE DUPLICATE
105	POSTS. The work-around for handling filtered URIs in guid elements has now
106	been extended to handle URIs that were altered without being filtered out
107	entirely (most commonly because a scheme was added to a relative URL).
108
109	* BUGFIX: UPDATES TO POST NO LONGER CAUSE DUPLICATE DRAFT VERSION TO APPEAR.
110	Under certain conditions in 2011.0531, an update to an existing post would
111	not be properly applied to the post itself, but rather would appear as a
112	duplicate post with Draft status. This bug has been eliminated, and updates
113	will now be properly inserted as revisions to the existing post.
114
115	= 2011.0531 =
116
117	* WORDPRESS 3.1.3 COMPATIBILITY: DUPLICATE POSTS ISSUE FIXED. Due to
118	internal changes in the way that WordPress handles post guids in the
119	most recent release (3.1.3), many users experienced problems with many
120	duplicate posts appearing in rapid succession. (Specifically, this would
121	happen with any posts using tag: URL guids -- such as all the posts
122	coming from Blogger feeds or feeds from other Google services.) This
123	compatibility release of FeedWordPress eliminates the issue by working
124	around the new restrictions on tag: URLs.
125
126	* NEW AND IMPROVED DIAGNOSTICS: Syndication --> Diagnostics now contains some
127	new diagnostics settings useful for debugging problems with duplicate posts
128	(allowing you to easily view the guid of posts in the WordPress posts
129	database and allowing you to track the SQL used to check for existing
130	versions of a syndicated post).
131
132	= 2011.0512 =
133
134	* DIAGNOSTICS IMPROVEMENTS; "THERE MAY BE A BUG IN FEEDWORDPRESS" CRITICAL
135	ERROR NOTICES ELIMINATED: This version includes some major improvements
136	to the Syndication --> Diagnostics section, which should aid in
137	troubleshooting difficulties with items failing to be imported, posts
138	failing to be properly inserted into the database, or updates failing to
139	be recorded. If you have been encountering critical error / bug notices
140	with a white screen and the message "THERE MAY BE A BUG IN
141	FEEDWORDPRESS," followed by an extraordinarily long dump of mostly
142	incomprehensible diagnostic information, you'll be happy to know that
143	the condition causing these notices has been eliminated. In the few
144	cases where errors may still crop up with database insertions,
145	FeedWordPress will now produce a significantly more manageable and more
146	useful diagnostic message.
147
148	* BUGFIX: NEW POSTS FAILING TO APPEAR IN A CLEANLY-INSTALLED FEEDWORDPRESS
149	SYSTEM. If you encountered a recurring problem with FeedWordPress
150	failing to import new posts, after a clean install of FeedWordPress
151	(i.e., not an upgrade from a previous version), this problem may have
152	been the result of a bug with author-handling which has now been fixed
153	in the 2011.0512 release. (If the problem does not go away with the
154	upgrade, this version also includes significant improvements to the
155	Diagnostics system, which will help track down what is causing it
156	in your particular case.)
157
158	* PERFORMANCE: New handling of update hashes allows FeedWordPress to avoid
159	a certain kind of infinite loop, caused when two more more different
160	syndicated feeds each carried a version of the same item (for example,
161	because it appeared on two different aggregator feeds that you're
162	syndicating). In previous versions, when this kind of loop cropped up,
163	syndicated posts could pile up an indefinitely large number of revisions
164	-- each revision alternating between the version from each of the two
165	feeds where it appeared -- which would, over time, dramatically inflate
166	the size of the database, and kill the performance of queries on the
167	post table. This issue has been resolved: revisions of the post that
168	have been syndicated once will not be re-syndicated over and over again.
169
170	* AUTHOR LISTS: Lists of authors presented on the Author settings pages
171	should now be easier to scan through, with author names arranged in
172	alphabetical order.
173
174	* FEED ITEM DATE PARSING: More tweaks to make date-time handling more
175	resilient when feeds provide broken or weird values for the timestamps
176	on syndicated items. FWP will now attempt to work around unparseable
177	timezone values.
178
179	* AUTHOR MATCHING: Now attempts to match author names against the WP login
180	name in addition to display_name; when creating user record, also fills
181	in some best-guess values for nickname, firstname and lastname. Also
182	properly picks up Atom 1.0 author/uri data from feed.
183
184	* COMPATIBILITY: FeedWordPress has been successfully tested for
185	compatibility with recent releases of WordPress, up to version 3.1.2.
186
187	= 2011.0211 =
188
189	* BUGFIX: DUPLICATE POSTS WHEN GUIDS ARE TOO LONG: When feeds included
190	exceptionally long GUIDs, FeedWordPress could occasionally get into
191	a situation where posts with the long GUIDs would be duplicated over
192	and over again with each update (because FWP failed to store the full
193	GUID, due to length constraints in the relevant database tables).
194	Without the full GUID, FWP would not know that the post had already
195	been syndicated once. This bug has been fixed, and should no longer
196	produce duplicate posts.
197
198	* HTTP TIMEOUT SETTING: If you are frequently running into timeout
199	problems with one or more of the feeds you syndicate, FWP now allows you
200	to adjust the timeout for HTTP requests using a global or feed-by-feed
201	setting.
202
203	* HTTP GET PARAMETERS: You can now temporarily or permanently add HTTP
204	GET parameters to a subscription using an interface in Syndication -->
205	Feeds & Updates. This is especially helpful for making quick, short-term
206	changes to a subscription (for example, to pull in all the previous
207	items from a web service, before settling down to pulling in only newly
208	updated items).
209
210	* DIAGNOSTICS SYSTEM: Added several new diagnostics which are useful in
211	troubleshooting, and established a framework for add-on modules to hook
212	in with their own diagnostic messages.
213
214	* UI: Adjusted some internal coding, which should allow for settings
215	pages and add-ons to properly display multiple category pickers on a
216	single settings page.
217
218	* PHP4 COMPATIBILITY TWEAKS: This version makes some tweaks to the handling
219	of object references which should improve compatibility with older
220	versions of PHP. (Although, I should note, web hosts that still force
221	you to run under PHP 4 -- in 2011! -- are bad web hosts.)
222
223	* IMPROVED PERFORMANCE: This version eliminates a major performance drag
224	that shows up on sites with large numbers of users (due to some poor
225	decisions about where to place a user query, which caused the user table
226	to be scanned frequently when it did not need to be). If you experienced
227	serious problems with CPU load or slow database performance under
228	2010.0905, which kicked in immediately when FWP was loaded and tended
229	to disappear immediately if FWP was de-activated, it is likely that
230	upgrading away from 2010.0905 to the most recent version will resolve
231	your problem.
232
233
234	= 2010.0905 =
235
236	* BUGFIX: CATEGORIES AND TAGS CORRECTLY ASSIGNED IN AUTOMATIC UPDATES.
237	Version 2010.0903 switched over to a new way of assigning categories and
238	tags as part of its support for handling custom taxonomies.
239	Unfortunately, the method that it uses is subjected to some checks of
240	the current user's capabilities, which creates problems for posts that
241	are being inserted into the WordPress database when there is no
242	current user logged in (as, for example, when an update is being carried
243	out from a cron job or automatic update). The result was that posts
244	from cron jobs and automatic updates ended up with no Categories and no
245	Tags being assigned. This bug has now been fixed: in 2010.0905, Tags and
246	Categories should be correctly assigned to all posts, regardless of
247	whether they were added from manual updates, cron jobs, or automatic
248	updates.
249
250	= 2010.0903 =
251
252	* WORDPRESS 3 REQUIRED: Please note that this release of FeedWordPress
253	requires WordPress 3.0 or later. If you are currently using a 2.x
254	branch of WordPress, you will need to upgrade to WordPress 3 before you
255	can successfully upgrade FeedWordPress.
256
257	* BUGFIX: NO MORE DISAPPEARING "SYNDICATED SOURCES" PANEL; INTERNET
258	EXPLORER UI GLITCH APPARENTLY FIXED: Several users independently
259	reported a problem with FWP 2010.0623 and various versions of IE. A
260	problem with the HTML markup caused IE (but not Firefox or
261	Chrome) to completely hide the Syndicated Sources administration panel
262	(the main list of currently-syndicated sources, and the main location
263	for adding new sources, under the Syndication menu item) when a user
264	added their first syndicated feed. Maddeningly, the glitch seemed to
265	affect some IE users and not others: I was never able to reproduce the
266	problem for myself on my own machines. However, the markup of Syndicated
267	Sources has undergone significant changes and corrections since
268	2010.0623, and two independent sources who had been having this problem
269	confirm that they no longer encounter it with the updated version. For
270	the time being, I am going to declare this bug squashed.
271
272	* BUGFIX: MORE PROTECTION AGAINST FATAL ERRORS FROM PLUGGABLE VERSIONS OF
273	SimplePie: FeedWordPress now takes some precautions that should help to
274	better avoid conflicts for users who have installed pluggable versions
275	of SimplePie for another plugin or theme. (You may not know that you have
276	done this; but if you've been encountering fatal errors indicating that
277	you cannot redeclare class SimplePie, or something along those lines,
278	there is now a better chance that those fatal errors will be eliminated.
279
280	* PERFORMANCE: SIGNIFICANTLY REDUCED MEMORY CONSUMPTION FOR LARGE UPDATES:
281	FeedWordPress is still a memory-hungry little module, especially when
282	you are dealing with very large feeds. However, users should notice a
283	significant reduction in memory overloads, especially if they update a
284	large number of feeds at once.
285
286	* USER INTERFACE IMPROVEMENTS: Nothing is radically different, but there's
287	been a fair amount of extra spit and polish added, including a convenient
288	new Dashboard widget that may save you a trip to the Syndication menu,
289	a lot of effort to make the relationship between global and feed-by-feed
290	settings more obvious to the user and more easily controllable, to make
291	navigation between settings pages easier, to sand off a few rough edges,
292	and to make other improvements on the margins. I hope you'll like how
293	it looks.
294
295	* ADDING MULTIPLE FEEDS: FeedWordPress now provides a convenient mode for
296	adding multiple feeds at once, using either a copy-and-pasted list, or
297	else an OPML file. Go to Syndication --> Syndicated Sources and check
298	out the two new buttons underneath the New Source input box. When you
299	have to add a number of feeds at once, this can save you considerable
300	time and trouble.
301
302	* IMPROVED HANDLING OF AUTHORS WITH DUPLICATE E-MAIL ADDRESS AND AUTHORS
303	WITH NAMES WRITTEN IN FOREIGN SCRIPTS: WordPress 3 is increasingly picky
304	about what it will accept for new author accounts, and some of the
305	conditions it imposes can cause error conditions that prevent posts from
306	being properly syndicated, or properly attributed, if authors happen to
307	have identical e-mail addresses, or if users are given usernames that are
308	written in non-Western scripts. FeedWordPress now handles these much
309	better, and systematically works to avoid clashes between syndicated
310	authors' account names or in their e-mail addresses, which should result
311	in significantly better results in mapping author names to WordPress
312	user accounts.
313
314	* MAPPING CATEGORIES ON SYNDICATED POSTS TO TAGS NOW BETTER SUPPORTED:
315	In previous versions, the only way for the Categories provided by a
316	syndicated feed to be mapped into Post Tags was to instruct FWP to
317	create new tags, rather than new categories, for unfamiliar categories
318	from the feed. This works fine if you want tags to be the default; but
319	if you want only a specific set of tags, there was no way to get them
320	without getting most or all other categories imported as tags. You can
321	now do this by creating a tag (under Posts ==> Post Tags) before
322	importing the post; when the syndicated category matches a pre-existing
323	tag, the incoming post will be tagged with that tag, without creating
324	a local Post Category.
325
326	* REL-TAG MICROFORMAT SUPPORT FOR INLINE TAGS: Syndicated posts that
327	contain inline tags, marked up using the Rel-Tag microformat
328	<http://microformats.org/wiki/rel-tag>, are now tagged with the tags
329	provided by Rel-Tag format links.
330
331	* MUCH GREATER CONTROL OVER CATEGORY AND TAG MAPPING: This is partly the
332	result of building in support for a potentially endless set of custom
333	taxonomies (see below), but in general there has been a great deal of
334	effort towards giving you more control over how categories and tags
335	provided by the feed are mapped into terms on the local blog. In
336	particular, you can now force FeedWordPress to create only categories
337	from categories and tags provided by the feed; or to create only tags;
338	or to search both categories and tags for a match; or you can simply
339	force it to drop all of the categories provided by the feed and use
340	only categories or tags that you explicitly provide. In addition, you
341	can now also choose whether to override global categories settings with
342	a local, feed-specific setting; or whether to add together both the
343	global categories and the local feed-specific categories -- depending
344	on whatever your use-case may demand.
345
346	* CUSTOM POST TYPES AND TAXONOMY SUPPORTS: This is mainly for the
347	super-geeky, but if you use other plugins or themes that make
348	significant use of WordPress's support for custom post types and custom
349	taxonomies, you may be pleased to find that FeedWordPress now allows you
350	to feed incoming posts into any custom feed type that you wish, and to
351	map categories and tags from the feed to custom taxonomies as well as
352	to the standard Category and Tag taxonomies.
353
354	* STORING NAMESPACED CUSTOM FEED ELEMENTS IN POST CUSTOM FIELDS: If you
355	would like to use FeedWordPress's support for storing custom meta-data
356	from feed elements in the custom fields for a post (for example, to
357	store geolocation data or iTunes media meta-data), you'll find that it's
358	now much easier for you to access these namespaced elements. You always
359	could access them, but in previous versions you might have to write
360	something ugly like $(/{http://www.w3.org/2003/01/geo/wgs84_pos#}lat)
361	just to get at the value of a `<geo:lat>` tag. Now, as long as you use
362	the same mnemonic codes that the feed producer used, you should always
363	be able to write a nice, simple expression like $(/geo:lat) to get the
364	value of a <geo:lat> tag.
365
366	* CUSTOM DIRECTORY STRUCTURE SUPPORT: if you poke at it enough, WordPress
367	is relatively flexible about where it should store admin interface code,
368	uploaded content, plugins, and a number of other things that occupy an
369	important place in the WordPress directory structure. Previous versions
370	of FeedWordPress encountered serious errors or broke entirely when used
371	with directory structures other than the default. This should now be
372	fixed: FWP now supports custom directory structures wherever WordPress
373	allows them to be customized, rather than depending on the default
374	locations. Enjoy your freedom!
375
376	* MANY NEW FILTERS AND API UTILITY FUNCTIONS FOR ADD-ON PROGRAMMERS: There
377	have been too many improvements to list them all in this ChangeLog, but
378	it means that much more power and ease for folks who are customizing
379	FeedWordPress through PHP filters or add-on modules. Fuller
380	documentation will be put up at the Wiki at feedwordpress.radgeek.org
381	soon.
382
383	= 2010.0623 =
384
385	* WORDPRESS 3.0 COMPATIBILITY / AUTHOR MAPPING INTERFACE ISSUES: I
386	resolved a couple of outstanding issues with the author mapping
387	interface (Syndication --> Authors), which were preventing new users
388	from being created correctly and author mapping rules from being set up
389	correctly. These partly had to do with new restrictions on user account
390	creation introduced in WordPress 3.0; anyway, they should now be fixed.
391
392	* MORE EFFICIENT SYNDICATED URL LOOKUPS: Several users noticed that the
393	bug fix introduced in 2010.0528 for compatibility with post-listing
394	plugins caused a lot more queries to the database in order to look up
395	numerical post IDs from the URL provided to the filter. This shouldn't
396	cause any major problems, but it is not as efficient as it could be; the
397	code now takes advantage of a more efficient way of doing things,
398	which usually will not require any additional database queries.
399
400	* SIMPLEPIE FEED UPDATE ISSUES: If you have been having significant
401	problems with getting feeds to update correctly, this may be the result
402	of some bugs in the implementation of SimplePie caching that ships with
403	WordPress (as of version 3.0). (You would most commonly experience this
404	error if you continually saw errors such as "No feed found at <...>" in
405	your updates.) Fortunately, SimplePie allows for a great deal of
406	extensibility and this allows me to work around the problem; these
407	error conditions should now be mostly eliminated when the underlying
408	feed is valid.
409
410	* UI: SHOW INACTIVE SOURCES: When you use the default unsubscribe option
411	-- which turns off the subscription to a feed while preserving the posts
412	from it and the syndication-related meta-data for the feed -- the
413	unsubscribed feed can now easily be viewed in a special "Inactive"
414	section of the Syndicated Sources page. (As a side benefit, if you've
415	accidentally, or only temporarily, turned off the subscription to a
416	feed, it is now much easier to restore the feed to being active, or to
417	delete it permanently, if you prefer.
418
419	* UI: FEED FINDER / SWITCH FEED INTERFACE IMPROVEMENTS: changes to styling
420	and options for the feed finder / switch feed, which should now make it
421	easier, in some cases, to find alternative feeds, and make interface
422	options more clearly visible.
423
424	* FILTERS: `syndicated_item_published` and `syndicated_item_updated` NOW
425	PROPERLY AFFECT THE DATING OF POSTS. These filters used to affect some
426	date-related settings, but not others -- and, most importantly, not the
427	final date that is set for a post's publication or last-modified date
428	in the WordPress database. Now, they do affect that, as they should.
429	(Filters should receive, and return, a long integer, representing a Unix
430	epoch relative timestamp.)
431
432	* MAGIC URL TO CLEAR THE CACHE: Suppose that you need to clear the feed
433	cache, for whatever reason; suppose, even, that you need to clear it on
434	a regular basis. One way you might do this is by logging into the
435	FeedWordPress administrative interface and going to Syndication -->
436	Performance. Another way you might do it, now, is to simply send an
437	HTTP request to a magic URL provided by FeedWordPress: if your blog is
438	at example.com, the URL would be <http://example.com/?clear_cache=1>
439
440	= 2010.0602 =
441
442	* CATEGORY BOX INTERFACE ELEMENT FIXED FOR WP 3.0: Stylesheet changes
443	between WordPress 2.9.x and the WordPress 3.0 RC caused the Categories
444	box under Syndication --> Categories & Tags to malfunction. This
445	has been fixed.
446
447	* LINK CATEGORY SELECTION BOX IN SYNDICATION ==> FEEDS FIXED FOR WP 2.8
448	AND 2.9: A WP 3.0 compatibility change introduced in 2010.0531
449	inadvertently broke the Syndicated Link Category selector under
450	Syndication --> Feeds & Updates in WP 2.8 and WP 2.9, causing the post
451	categories to be displayed in the selector rather than the link
452	categories. This should now be fixed so that the selector will work
453	correctly under both the current versions of WordPress and the 3.0 RC.
454
455	* MORE PERMISSIVE HANDLING OF FEEDS WITH BAD CONTENT-TYPE HEADERS: One of
456	the small advantages that MagpieRSS had over SimplePie is that it was
457	more tolerant about parsing well-formed feeds that the remote web server
458	happened to deliver with weird or incorrect HTTP Content-type headers.
459	In feeds affected by this problem, the new SimplePie parser would simply
460	fail to find a feed, due to its being led astray by the contents of the
461	Content-type header. This version includes an extension to SimplePie's
462	content-type sniffer that offers more permissive handling of the HTTP
463	headers.
464
465	* MORE FULL-TEXT "EXCERPTS" NOW PROPERLY SHORTENED. Version 2010.0528
466	introduced code to control for cases in which elements intended for
467	item summaries are (ill-advisedly) used to carry the full text of posts;
468	past versions of FeedWordPress would simply include the full text of the
469	post in the excerpt field, but newer versions now attempt to detect
470	this condition when it arises and to head it off, by blanking out the
471	excerpt field and filling it with an automatically generated short,
472	plain text excerpt from the full content. This release broadens the
473	test conditions that indicate when an excerpt field is treated as
474	identical to the full text of the post, and should therefore improve
475	the handling of some feeds (such as Google Reader feeds) where the full
476	text of each post was still appearing in the excerpt field.
477
478	* FILTERS: `syndicated_item_published` AND `syndicated_item_updated`
479	FILTERS NOW ALLOW FILTER AUTHORS TO CHANGE POST TIMESTAMPS. You can now
480	use the `syndicated_item_published` and `syndicated_item_updated` filter
481	hooks to write filters or add-ons which directly change the post date
482	and most-recently-updated timestamps on incoming syndicated posts. Props
483	to niska for pointing out where the filters needed to be applied in
484	order to change WordPress's internal timestamps for incoming posts.
485
486	= 2010.0531 =
487
488	* PERMALINK / CUSTOM FIELDS PROBLEM RESOLVED: An issue in 2010.0528 caused
489	some posts to be imported without the proper syndication-related
490	meta-data being attached (thus causing permalinks to point back to the
491	aggregator website rather than to the source website, among other
492	problems). This problem has been resolved (and a fix has been applied
493	which will resolve the problem for any posts affected by this problem,
494	if the original post is recent enough to still be available on the feed).
495
496	* UI: The "Back End" section has been split into two separate sections --
497	"Performance" (dealing with caching, database index, and other
498	performance tweaks), and "Diagnostics" (dealing with debug mode,
499	update logging, and a number of new diagnostic tests which I will be
500	rolling out over the next few releases).
501
502	* Several minor interface bug fixes and PHP warning notices eliminated.
503
504	= 2010.0528 =
505
506	#### Compatibility ####
507
508	* SIMPLEPIE IS NOW USED TO PARSE FEEDS; NO MORE MAGPIERSS UPGRADES NEEDED:
509	One of the biggest changes in this release is that FeedWordPress no
510	longer depends on MagpieRSS to parse feeds, and has switched to the much
511	more up-to-date and flexible SimplePie feed parser, which is included as
512	a standard part of WordPress versions 2.8 and later. Using SimplePie will
513	hopefully allow for better handling of feeds going further, and will
514	allow me greater flexibility in determining how exactly the feed parser
515	will operate. It also means that FeedWordPress no longer requires
516	special upgrades to the WordPress core MagpieRSS files, and should
517	eliminate quite a bit of complexity.
518
519	* MAGPIERSS COMPATIBILITY LAYER FOR EXISTING FILTERS AND ADD-ONS: However,
520	I have also implemented a compatibility layer to ensure that existing
521	filters and add-ons for FeedWordPress which depended on the MagpieRSS
522	data format should not be broken by the switch to SimplePie. Going
523	forward, I recommend that new filters and add-ons be written to take
524	advantage of the SimplePie object representations of items, feeds, etc.,
525	rather than the MagpieRSS arrays, but the MagpieRSS arrays will still
526	be available and older filters should continue to work as they have in
527	the past.
528
529	* COMPATIBILITY WITH WORDPRESS 2.9.x and 3.0: This release has been tested
530	for the existing WordPress 2.9.x branch and with the upcoming release of
531	WordPress 3.0. Changes in the user interface JavaScript between WordPress
532	2.8.x and WordPress 2.9 caused the tag box interface element to break in
533	the Syndication --> Categories & Tags settings page; changes in the API
534	functions for adding new authors caused fatal errors under certain
535	conditions in WordPress 3.0. These breakages have been fixed.
536
537	* DROPPED LEGACY SUPPORT FOR WORDPRESS PRIOR TO 2.8: Because SimplePie is
538	not included with versions of WordPress prior to 2.8, I have chosen to
539	drop legacy support for WordPress versions 1.5 through 2.7. If you are
540	using FeedWordPress with a version of WordPress before 2.8, you will
541	have to upgrade your installation of WordPress in order to take
542	advantage of this release.
543
544	* PHP 5.3 COMPATIBILITY: A couple of compatibility issues, which were
545	causing fatal errors amd ugly warnings for users of PHP 5.3,
546	have been eliminated.
547
548	#### Features and Processing ####
549
550	* INTERFACE REORGANIZATION: The interface restructuring, began with
551	Version 2009.0612, has been completed. Catch-all settings pages have
552	been eliminated entirely for pages that cover each aspect of handling
553	a feed: Feeds & Updates, Posts & Links, Authors, Categories & Tags,
554	and Back End handling of the database and diagnostic information.
555	Extensive new interface hooks allow add-on modules to significantly
556	change or extend the FeedWordPress admin interface and workflow.
557
558	* STORING INFORMATION FROM THE FEED IN CUSTOM FIELDS: Many users
559	have written to request the ability to store information from elements
560	in the feed in a custom field on each post. (So that, for example, if
561	post includes a `itunes:duration` element, you could store the contents
562	in a Custom Field called `duration` on the post (for a Theme to access
563	later). The Custom Post Settings under Syndication --> Posts & Links now
564	allow you to access any item or feed tag, using a syntax similar to
565	a much-simplified version of XPath. See Posts & Links settings for
566	details.
567
568	* UPDATE-FREEZING ON MANUALLY EDITED POSTS: FeedWordPress now allows you
569	to mark posts that have been manually edited, so that the changes you
570	make will not be overwritten by later updates from the feed. If you make
571	manual edits to a particular post, just check the "Manual editing"
572	checkbox in order to protect your changes from being overwritten. If you
573	want to block all posts from being updated after they are imported
574	for the first time, a new "Updated Posts" setting in Posts & Links
575	allows you to freeze all posts from a particular feed, or all syndicated
576	posts.
577
578	* SETTING: FEED-BY-FEED SETTINGS FOR WHERE PERMALINKS POINT TO: You've
579	always been able to tell FeedWordPress whether permalinks for posts
580	should point to the original source of the story or the local copy. Now
581	you can choose different policies for different feeds, instead of one
582	global policy for all feeds. (Of course, you can still use a global
583	default if you prefer.)
584
585	* SETTING: USER CONTROL OVER TIMING BASIS. You can now determine the
586	schedule on which feeds are considered ready to poll for updates --
587	by default feeds become ready for polling after about 1 hour. You can
588	now increase or decrease the time window under Syndication --> Feeds &
589	Updates. (However, please pay CAREFUL ATTENTION to the recommendations
590	and DO NOT set the scheduling lower than 60 minutes unless you are
591	ABSOLUTELY SURE that you have specific permission from webmaster who
592	provides that specific feed to poll more frequently than that. If you
593	set this too low (and about 60 minutes is the polite minimum if you
594	haven't been given a different figure), most webmasters will consider
595	the frequent hits on their server as rude, or even downright abusive.
596
597	* OTHER SETTINGS: New settings also include the ability to stop FWP from
598	resolving relative URLs within syndicated content, and the ability to
599	choose whether FeedWordPress should indicate the comment feed from the
600	original source, or the local comment feed, when providing the comment
601	feed URL for a syndicated post.
602
603	#### Parsing ####
604
605	* BETTER DATE HANDLING -- FEWER FLASHBACKS TO 1969 and 1970: FeedWordPress
606	has made some bugfixes and some improvements in the logic for parsing
607	dates. This should allow FeedWordPress to correctly parse more dates in
608	more feeds; and, in the last resort, when FeedWordPress fails to
609	correctly parse a date, to fall back to a more intelligent default. This
610	should hopefully avoid most or all error conditions that have resulted
611	in articles being erroneously dated to the dawn of the Unix epoch
612	(31 December 1969 or 1 January 1970).
613
614	* FULL-TEXT "EXCERPTS" NOW PROPERLY SHORTENED. Based on a straightforward
615	reading of the existing RSS specs, it's reasonable for the
616	rss:description element to be read as a plaintext summary or excerpt for
617	the item containing the description -- with the full text of the item,
618	if available, in another, better-suited element, such as the de facto
619	standard content:encoded extension element. The problem is that uses of
620	RSS rarely have much to do with anything like a straightforward reading
621	of the specs. As a result, many actual RSS producers in the wild put the
622	full text of the article in a description element. But since
623	FeedWordPress has treated this text as a summary, this produces
624	aggregated posts with lengthy "excerpts" containing the full text of the
625	article. This release of FeedWordPress fixes the problem by doing a
626	little digging before treating rss:description as a summary: if the
627	description element is used properly as a plain text summary, then
628	FeedWordPress will take the summary provided by the feed, rather than
629	recreating its own excerpt from the full text; but if an RSS item has no
630	full-text element other than description, FeedWordPress will treat the
631	description element as the full text of the article, and generate a
632	shortened excerpt automatically from that text.
633
634	#### API ####
635
636	* TEMPLATE API: new template tags `get_local_permalink()` and
637	`the_local_permalink()` allow you to access the permalink for a post on
638	your aggregator site, even when FeedWordPress is rewriting permalinks to
639	point to the original source site.
640
641	* NEW HOOKS FOR ADD-ONS AND FILTERS: I have added a number of new hooks
642	which allow add-on modules to filter more precisely, gather information
643	at more points, and to enhance the FeedWordPress admin interface. For
644	a list of new hooks and documentation, see the FeedWordPress
645	documentation wiki at
646	<http://feedwordpress.radgeek.com/wiki/add-ons-and-filters>
647
648	* FILTER API: A number of new utility methods have been added to the
649	SyndicatedPost class to make it easier for filters and add-ons to
650
651	* FILTER API: Globals $fwp_channel and $fwp_feedmeta DEPRECATED. These
652	global variables, originally introduced to allow filters access to
653	information about the source feed in `syndicated_item` filters (which
654	were passed in through global variables rather than as parameters
655	because of a bug in WP 1.5 which was then fixed in 1.5.1) have been
656	DEPRECATED. If you have any filters or add-ons which still depend on
657	these global variables, you should see about fixing them to access data
658	about the source feed using the SyndicatedPost::link element instead.
659	For documentation, see the FeedWordPress documentation wiki at
660	<http://feedwordpress.radgeek.com/wiki/syndicatedpost> and
661	<http://feedwordpress.radgeek.com/wiki/syndicatedlink>.
662
663	* DIAGNOSTICS: I've included a number of new diagnostic options and
664	messages, which should allow an experienced user to better investigate
665	any problems that may crop up.
666
667	#### Bug Fixes ####
668
669	* BUGFIX: & IN PERMALINKS NO LONGER CAUSING ATOM OR HTML VALIDATION
670	EFFORTS: Many users reported an issue in which syndicating a feed with
671	special XML characters in the URLs (& was the most common, since it is
672	used to separate HTTP GET parameters) would cause the aggregator's
673	feeds to produce invalid (malformed) XML. This update addresses the
674	issue in Atom feeds. Unfortunately, it has not been technically possible
675	to address the problem in RSS 2.0 feeds, due to limitations on
676	WordPress's internal templates for RSS feeds.
677
678	* BUGFIX: BROKEN URLS IN "POPULAR POSTS" AND SIMILAR PLUGINS SHOULD NO
679	LONGER BE BROKEN. A number of users noticed an issue where plugins and
680	templates that listed posts in locations outside of the post loop
681	(for example, "Popular Posts"-style plugins that listed posts in the
682	sidebar), often produced the wrong URL for post links. (Typically, all
683	the posts listed would get the same wrong URL.) This should now be
684	fixed. Thanks to Björn for sending in a quick fix!
685
686	* MINOR BUGFIXES: This release includes a number of fixes to minor bugs
687	and compatibility issues, including: silent failures of the "Syndicate"
688	button, "Illegal Offset Type" error messages from MagpieRSS, and others.
689
690	= 2009.0707 =
691
692	* BUGFIX: WORDPRESS 2.8 AJAX COMPATIBILITY ISSUES RESOLVED (blank or
693	truncated "Syndicated Sites" administration page): Due to changes in the
694	AJAX interface elements between WordPress 2.7 and WordPress 2.8, several
695	FeedWordPress users encountered an issue where the front "Syndication"
696	page in the FeedWordPress administrative interface would come up blank,
697	without the normal "Syndicated Sites" list and "Update" control, or
698	sometimes wth the boxes visible but one or both of them truncated, with
699	only the title bar. This issue should now be resolved: with the new
700	version of FeedWordPress, the compatibility issue that caused the
701	disappearance should be eliminated, and if boxes are shown with only
702	their handle visible, you should once again be able to drop down the
703	rest of the box by clicking once on its title bar.
704
705	* BUGFIX: TAG SETTING WIDGET FIXED. Due to changes in interface elements
706	between WordPress 2.7 and WordPress 2.8, people using FeedWordPress with
707	WordPress 2.8 found that the widget for setting tags to be applied to
708	all syndicated posts, or all syndicated posts from a particular feed,
709	no longer displayed "Add" and "Remove" buttons for individual tags. This
710	issue has now been fixed, and the tagging widget should once again work
711	more or less exactly like the tagging widget for individual posts in the
712	normal WordPress admin interface.
713
714	= 2009.0618 =
715
716	* BUGFIX: MYSTERY ERRORS WITH WITH WP_Http_Fsockopen HTTP TRANSPORT
717	ELIMINATED: Thanks to a combination of a subtle bug in FeedWordPress,
718	and changes to the HTTP transport code in WordPress, a number of users
719	encountered an error in which any time they attempted to add a new feed
720	through the FeedFinder interface, FeedWordPress would fail and display
721	an HTTP request failure diagnostic message. The subtle bug has been
722	fixed, and with it, most of these errors should now be eliminated.
723
724	Be sure to upgrade your MagpieRSS to the most recent MagpieRSS version
725	after you have insalled FeedWordPress 2009.0618, or this bug fix will
726	not take effect.
727
728	= 2009.0613 =
729
730	* INTERFACE/BUGFIX: WORDPRESS 2.8 CATEGORY BOX FIX. Thanks to a subtle
731	change in class names between the WordPress 2.7 and 2.8 stylesheets,
732	category boxes in the FeedWordPress settings interface tended to overflow
733	and have a lot of messy-looking overlapping text under WordPress 2.8.
734	This has now been fixed.
735
736	* FeedFinder FAILURE DIAGNOSTICS: When FWP's FeedFinder fails to find any
737	feeds at a given URL (for example, when you are trying to add a
738	subscription through the administrative interface and you run into an
739	error message), FeedWordPress now provides more diagnostic information
740	for the reasons behind the failure. If that helps you, great; if not,
741	it should help me respond more intelligently to your support request..
742
743	= 2009.0612 =
744
745	* WORDPRESS 2.8 COMPATIBILITY: FeedWordPress 2009.0612 has been tested for
746	compatibility with the recent version 2.8 release of WordPress.
747
748	* INTERFACE RESTRUCTURING: In order to avoid settings posts from becoming
749	too crowded, and to modularize and better organize the user interface,
750	new "Posts" and "Categories & Tags" subpages have been created under the
751	"Syndication" menu. "Posts" controls settings for individal syndicated
752	posts (such as publication status, comment and ping status, whether or
753	not to use the original location of the post as the permalink, whether
754	or not to expose posts to formatting filters, and so on). "Categories &
755	Tags" controls settings for assigning new syndicated posts to categories
756	and tags, such as categories or tags to apply to all syndicated posts,
757	and how to handle categories that do not yet exist in the WordPress
758	database. These subpages, like the Authors subpage, handle settings for
759	the global default level and for individual syndicated feeds.
760
761	Corresponding to these new subpages, the old Syndication Settings and
762	Feed Settings subpages have been cleaned up and simplified, and now only
763	link to the appropriate subpages for options that can be set in the
764	Posts, Authors, or Categories & Tags subpages.
765
766	* FEATURE: ADD CUSTOM SETTINGS TO EACH SYNDICATED POST: FeedWordPress has
767	long had an interface for creating custom settings for each syndicated
768	feed which could be retrieved in templates using the `get_feed_meta()`
769	template function. But it had no feature for adding custom fields to
770	each individual syndicated post. In response to requests from users, I
771	have added the ability to apply custom fields to each individual
772	syndicated post, using the new Syndication --> Posts subpage. You can
773	set up custom fields to be applied to every syndicated post, or custom
774	fields to be applied to syndicated posts from a particular feed.
775
776	* FEATURE: MAGPIERSS VERSION CHECK AND UPGRADE: FeedWordPress will attempt
777	to determine whether or not you are using the upgraded version of
778	MagpieRSS that comes packaged with FeedWordPress. If not, it will throw
779	an error on admin pages, and, if you are a site administrator, it will
780	give you the option to ignore the error message, or to attempt an
781	automatic upgrade (using a native file copy). If the file copy fails,
782	FeedWordPress will offer some guidance on how to perform the upgrade
783	manually.
784
785	* BLANK POSTS PROBLEM NO LONGER OCCURS WITH OLD & BUSTED MAGPIERSS: Due
786	to the fact that I relied on a content normalization that occurs in my
787	upgraded version of MagpieRSS, but not in the old & busted version of
788	MagpieRSS that ships with WordPress, until this version, if you tried to
789	syndicate an Atom feed without having performed the (*strongly
790	recommended*) MagpieRSS upgrade, all of the posts would come up with
791	completely blank contents. That's not because MagpieRSS couldn't read
792	the data, but rather because the new Magpie version puts that data in a
793	location where the old version doesn't, and I was only looking in that
794	newer location. Now it checks for both, meaning that posts will continue
795	to display their contents even if you don't upgrade MagpieRSS. (But you
796	really should upgrade it, anyway.)
797
798	* BUGFIX: RELATIVE URI RESOLUTION FOR POST CONTENT RESTORED. Some time
799	back, I added support for resolving relative URIs against xml:base on
800	feeds that support it to the MagpieRSS upgrade in FeedWordPress. Then I
801	took out code that did the same thing from the main FeedWordPress code.
802	Of course, the problem is that some people, even though it is clearly
803	stupid or evil to do so, still include relative URIs for images or links
804	in posts on feed formats that do not adequately support xml:base
805	(notably, RSS 2.0 feeds). In response to a user request, I have added
806	this functionality back in, so that MagpieRSS will resolve any relative
807	URIs that it knows how to resolve using xml:base, and then FeedWordPress
808	will attempt to resolve any relative URIs that are left over afterwards.
809
810	* BUGFIX: INTERFACE OPTION FOR SETTING SYNDICATED POST PUBLICATION STATUS
811	ON A FEED-BY-FEED BASIS HAS BEEN RESTORED: Due to a version-checking
812	bug, users of WordPress 2.7.x lost an option from the "Edit a syndicated
813	feed" interface which allowed them to determine whether newly syndicated
814	posts should be published immediately, held as "Pending Review," saved
815	as drafts, or saved as private posts. (The option to change this
816	setting globally remained in place, but users could no longer set it on
817	a feed-by-feed basis.) The version-checking bug has been fixed, and the
818	option has been restored.
819
820	* BUGFIX: "ARE YOU SURE?" FATAL ERROR ELIMINATED AND SECURITY IMPROVED:
821	Under certain circumstances (for example, when users have configured
822	their browser or proxy not to send HTTP Referer headers, for privacy or
823	other reasons), many features in the FeedWordPress administrative
824	interface (such as adding new feeds or changing settings) would hit a
825	fatal error, displaying only a cryptic message reading "Are you sure?"
826	and a blank page following it. This problem has been eliminated by
827	taking advantage of WordPress's nonce functions, which allow the
828	security check which ran into this error to work properly even without
829	receiving an HTTP Referer header. (N.B.: WordPress's nonce functions
830	were first introduced in WordPress 2.0.3. If you're using FeedWordPress
831	with an older version of WordPress, there's no fix for this problem:
832	you'll just need to turn Referer headers back on. Sorry.)
833
834	* BUGFIX: MANUALLY-ALTERED POST STATUS, COMMENT STATUS, AND PING STATUS NO
835	LONGER REVERTED BY POST UPDATES: If you manually altered the post status,
836	comment status, or ping status of a syndicated post from what it was set
837	to when first syndicated -- for example, if you had a feed that was set
838	to bring in new posts as "Pending Review," and you then marked some of
839	the pending posts as "Published" and others as "Unpublished" -- then
840	in previous versions of FeedWordPress, these manual changes to the
841	status would be lost -- so that, for example, your Published or Unpublished
842	articles would revert to Pending Review -- if the source feed made any
843	upates to the item. This could make the Pending Review feature both
844	unreliable and also extremely frustrating to work with. The good news is
845	that this bug has since been fixed: if you manually update the status
846	of a post, it will no longer be reverted if or when the post is updated.
847
848	* BUGFIX: OCCASIONAL FATAL ERROR ON UPDATE ELIMINATED: Under certain
849	limited conditions (specifically, when both the title and the content of
850	a post to be updated are empty), an attempt to update the post would
851	result in a fatal error. This has been fixed.
852
853	* INTERFACE: "CONFIGURE SETTINGS" CONVENIENCE LINK ADDED TO CONFIRMATION
854	MESSAGE WHEN A NEW FEED IS ADDED: When you add a new subscription to
855	FeedWordPress, the message box that appears to confirm it now includes a
856	handy link to the feed's settings subpage, so that you can quickly set
857	up any special settings you may want to set up for the new feed, without
858	having to hunt through the list of all your other subscriptions to pick
859	out the new one.
860
861	* INTERFACE: SIMPLIFYING AND CLARIFYING AUTOMATIC UPDATES SETTINGS. I have
862	removed an interval setting for the cronless automatic updates which has
863	confused many FeedWordPress users. In past versions of FWP, when you
864	turned on automatic updates, you would be presented with a time interval
865	setting which controlled how often FeedWordPress would check for feeds
866	ready to be polled for updates. (That is, it DID NOT control how often
867	feeds would be polled; it controlled how often FeedWordPress would
868	check for feeds that had become ready to poll. The schedule on which
869	feeds became ready for polling was still controlled either by requests
870	encoded in elements within the feed itself, or else according to an
871	internal calculation within FeedWordPress, averaging out to about 1 hour,
872	if the feed did not include any scheduling request elements.) Since many
873	users very often (and understandably) confused the purpose of this
874	setting, and since the setting is for a feature that's actually very
875	unlikely to require any manual control by the user, I have removed the
876	setting; FeedWordPress now simply uses the default value of checking for
877	feeds to poll every 10 minutes.
878
879	* FEEDFINDER PERFORMANCE IMPROVEMENT: FeedWordPress's FeedFinder class
880	now uses `array_unique()` to make sure that it doesn't waste time
881	repeatedly iterating over and polling the same URI. Props to Camilo
882	(<http://projects.radgeek.com/2008/12/14/feedwordpress-20081214/#comment-20090122160414>).
883
884	= 2008.1214 =
885
886	* WORDPRESS 2.7 COMPATIBILITY: FeedWordPress has been tested for
887	compatibility with the newly released WordPress 2.7. WordPress 2.7 has
888	deprecated the Snoopy library for HTTP requests, which caused a fatal
889	error for users who had not installed the MagpieRSS upgrade (or whose
890	installation of the MagpieRSS upgrade was overwritten by a recent update
891	of WordPress). FeedWordPress now handles things gracefully when Snoopy
892	is not immediately available.
893
894	* INTERFACE SPIFFED UP: Interface elements have been updated so that
895	FeedWordPress's management interface fits in more naturally with the
896	WordPress 2.7 interface (including a new logo and a number of small
897	interface tweaks).
898
899	* BUG WITH TAGS FOR SYNDICATED ARTICLES FIXED: Several users encountered a
900	bug with the option to add tags to all syndicated posts under
901	Syndication --> Settings -- if you told FeedWordPress to add more than
902	one tag to all syndicated posts, instead of doing so correctly, it would
903	add a single tag instead, whose name was composed of the names of all
904	the tags you asked it to add. This bug was the result of nothing more
905	dignified than a typographical error on my part. It has now been fixed.
906
907	* MORE INFORMATION AVAILABLE WHEN FEEDWORDPRESS CAN'T FIND A FEED: When
908	you enter a URL for a new syndication source, FeedWordPress uses a
909	simple feed-finding algorithm (originally based on Mark Pilgrim's
910	Universal Feed Finder) to try to determine whether the URL is the URL
911	for a feed, or, if the URL points to an ordinary website rather than to
912	a feed, whether there is a feed for that website. All well and good, but
913	if FeedWordPress failed to find a feed, for whatever reason, it would
914	typically return nothing more than a nasty little note to the effect of
915	"no feed found," without any explanation of what went wrong.
916	FeedWordPress now keeps track of error conditions from the HTTP
917	requests that it uses in the course of looking for the feed, and so may
918	be able to give you a bit more information about the nature of the
919	problem if something goes wrong.
920
921
922	= 2008.1105 =
923
924	* INTERFACE RESTRUCTURING AND SYNDICATION --> AUTHORS PAGE: As a first
925	step towards modularizing and better organizing the user interface, a
926	new "Authors" subpage has been created under the Syndication menu, which
927	controls settings for syndicated authors, both at the global default
928	level and at level of individual syndicated feeds.
929
930	* BUG RELATED TO THE ATTRIBUTION OF POSTS TO THE WRONG AUTHOR FIXED: Some
931	users encountered an issue in which posts by different authors on
932	different blogs -- especially blogs generated by Blogger -- were
933	mistakenly attributed to a single author. The problem was caused by the
934	way in which FeedWordPress matches syndicated authors to user accounts
935	in the WordPress database: normally, if two feeds each list an author
936	with the same e-mail address, they are counted as being the same person.
937	Normally this works well, but it creates an issue in cases where
938	blogging software assigns a single anonymous e-mail address to users who
939	do not want their real e-mail address published. This is, for example,
940	what Blogger does (by giving all users a default e-mail address of
941	<noreply@blogger.com> if they don't want their own e-mail address
942	listed). FeedWordPress now allows the user to correct for this problem
943	with a couple of new settings under Syndication --> Authors, which
944	allow users to turn off e-mail based author matching for particular
945	addresses, or, if desired, to turn it off entirely. By default, e-mail
946	based author matching is still turned on, but disabled for a list of
947	known generic e-mail addresses. Right now, the "list" consists entirely
948	of <noreply@blogger.com>; if you know other addresses that should be
949	added, please [contact me](http://radgeek.com/contact) to let me know.
950
951	Please note that if you have already encountered this issue on your
952	blog, upgrading FeedWordPress will prevent it from re-occurring in the
953	future, but you still need to do two other things to fix the existing
954	problem on your blog.
955
956	First, for each feed where posts have been mis-attributed, you need to
957	change the existing author mapping rules to re-map a a syndicated
958	author's name to the proper target account. Go to **Syndication -->
959	Authors**, select the feed you want to change from the drop-down list,
960	and then change the settings under the "Syndicated Authors" section.
961	(You will probably need to select "will be assigned to a new user..." to
962	create a new user account with the appropriate name.)
963
964	Second, for each feed where posts have been mis-attributed, you need to
965	re-assign already-syndicated posts that were mis-attributed to the
966	correct author. You can do that from Syndication --> Authors by
967	using the author re-assignment feature, described below.
968
969	* AUTHOR RE-ASSIGNMENT FOR A PARTICULAR FEED: The author settings page
970	for each syndicated feed, under Syndication --> Authors, now
971	includes an section titled "Fixing mis-matched authors," which provides
972	an interface for re-assigning or deleting all posts attributed to a
973	particular author on a particular feed.
974
975	* SUPPORT FOR `<atom:source>` ELEMENT IN SYNDICATED FEEDS: Some feeds
976	(for example, those produced by FeedWordPress) aggregate content from
977	several different sources, and include information about the original
978	source of the post in an `<atom:source>` element. A new setting under
979	Syndication --> Options allows you to control what FeedWordPress
980	will report as the source of posts syndicated from aggregator feeds in
981	your templates and feeds: you can have FeedWordPress report that the
982	source of a post is the aggregator feed itself, or you can have it
983	report that the source of a post is the original source that the
984	aggregator originally syndicated the post from.
985
986	By default, FeedWordPress will report the aggregator, not the original
987	source, as the source of a syndicated item.
988
989	* LOAD BALANCING AND TIME LIMITING FEATURES FOR UPDATES: Some users have
990	encountered issues due to running up against PHP execution time limits
991	during the process of updating large syndicated feeds, or a very large
992	set of syndicated feeds. FeedWordPress now has a feature that allows you
993	to limit the total amount of time spent updating a feed, through the
994	"Time limit on updates" setting under Syndication --> Options. By
995	turning on this setting and adjusting the time limit to a low enough
996	figure to avoid your PHP installation's time-out setting. (PHP execution
997	time limits are usually in the vicinity of 30 seconds, so an update
998	time limit of 25 seconds or so should provide plenty of time for updates
999	while allowing a cushion of time for other, non-update-related functions
1000	to do their work.)
1001
1002	If feed updates are interrupted by the time limit, FeedWordPress uses
1003	some simple load balancing features to make sure that updates to other
1004	feeds will not be blocked by the time-hogging feed, and will also make
1005	sure that when the interrupted update is resumed, FeedWordPress will
1006	skip ahead to resume processing items at the point at which it was
1007	interrupted last time, so that posts further down in the feed will
1008	eventually get processed, and not get blocked by the amount of time it
1009	takes to process the items higher up in the feed.
1010
1011	* `guid` INDEX CREATION BUTTON: FeedWordPress frequently issues queries on
1012	the `guid` column of the WordPress posts database (since it uses post
1013	guid URIs to keep track of which posts it has syndicated). In very large
1014	FeedWordPress installations, you can often significantly improve
1015	performance by creating a database index on the `guid` column, but
1016	normally you would need to poke around with MySQL or a tool like
1017	phpMyAdmin to do this. FeedWordPress can now save you the trouble: to
1018	create an index on the `guid` column, just go to
1019	Syndication --> Options, and mash the button at the bottom of the
1020	"Back End" section.
1021
1022	= 2008.1101 =
1023
1024	* INTERFACE BUG THAT PREVENTED ADDING NEW SITES FIXED: The UI reforms in
1025	FWP 2008.1030 unintentionally introduced a bug that prevents clean
1026	installations of FeedWordPress from providing an input box for adding
1027	new feeds to the list of syndicated feeds. This bug has been fixed.
1028
1029	= 2008.1030 =
1030
1031	* WORDPRESS 2.6 COMPATIBILITY: FeedWordPress should now be compatible with
1032	WordPress 2.6, and should work more or less seamlessly with the new post
1033	revision system. A bug which caused multiple new revisions to be created
1034	for posts on certain feeds, regardless of whether or not the item had
1035	been updated, has been fixed.
1036
1037	* INTERFACE IMPROVEMENTS: The user interface has been substantially
1038	restyled to fit in better with the visual style of WordPress 2.5 and
1039	2.6.
1040
1041	* YOUTUBE BUG FIXED: POSTS SYNDICATED THROUGH AN AUTOMATIC UPDATE ARE NO
1042	LONGER STRIPPED OF `<OBJECT>` TAGS AND CERTAIN OTHER HTML ELEMENTS: Due
1043	to the way that some versions of WordPress process posts that are
1044	inserted into the database when no user is logged in, many users
1045	experienced an issue where YouTube videos and other content using the
1046	HTML `<object>` tag would be stripped out of posts that were syndicated
1047	during an automatic update. (Posts that were syndicated through manual
1048	updates from within the WordPress Dashboard were not affected, because
1049	the issue does not arise when an update is executed under a logged-in
1050	administrator's credentials.) This bug has now been fixed; YouTube
1051	videos and other content using `<object>` tags should now appear
1052	properly in syndicated posts, regardless of the way in which the post
1053	was syndicated.
1054
1055	* AJAX BUGS FIXED: Bugs which blocked the normal operation of WordPress
1056	2.5's AJAX interface elements when FeedWordPress was activated have been
1057	fixed.
1058
1059	* TAG SUPPORT: A couple of features have been introduced to take advantage
1060	of the tagging features in WordPress 2.3.x, 2.5.x, and 2.6.x. Now, when
1061	unfamiliar categories are encountered for posts on a feed, you can
1062	choose for FeedWordPress (1) to drop the category; (2) to drop the
1063	category and to filter out any post that does not match at least one
1064	familiar category; (3) to create a new category with that name, or,
1065	now, you can also have FeedWordPress (4) create a new tag with that
1066	name. This option can be set site-wide under Syndication --> Options,
1067	or it can be set on a feed-by-feed basis in a feed's Edit screen.
1068
1069	In addition, you can now set particular tags to apply to all incoming
1070	syndicated posts, under Syndication --> Options, or you can set tags
1071	to apply to all incoming syndicated posts from a particular feed in that
1072	feed's Edit screen.
1073
1074	* FORMATTING FILTERS: There is a new option available under Syndication ->
1075	Options which allows users to choose whether or not to expose syndicated
1076	posts to being altered by formatting filters. By default, FeedWordPress
1077	has always protected syndicated posts (which are already in display-ready
1078	HTML when they are syndicated) from being reformatted by formatting
1079	filters. However, this approach means that certain plugins which depend
1080	on formatting filters (for example, to add "Share This" bars or relevant
1081	links to the end of a post) are blocked from working on any syndicated
1082	posts. If you want to use one of these plugins together with
1083	FeedWordPress, you can now do so by changing the "Formatting Filters"
1084	setting from "Protect" to "Expose."
1085
1086	* `<atom:source>` ELEMENTS NOW INCLUDED IN ATOM FEED: Atom 1.0 provides
1087	a standard method for aggregators to indicate information about the original source of
1088	a syndicated post, using the `<atom:source>` element. FeedWordPress now
1089	introduces standard `<atom:source>` elements including the title, homepage, and
1090	feed URI of the source from which a syndicated post was syndicated. Cf.
1091	<http://www.atomenabled.org/developers/syndication/atom-format-spec.php#element.source>
1092
1093	* MODULARIZATION OF CODE: The code for different elements of FeedWordPress
1094	has been broken out into several modules for easier inspection,
1095	documentation, and maintenance of the code.
1096
1097	* VERSIONING SCHEME CHANGED: FeedWordPress's feature set has proven stable
1098	enough that it can now be removed from beta status; a good thing, since
1099	I was very quickly running out of version numbers to use. New releases
1100	of FeedWordPress will have version numbers based on the date of their
1101	release.
1102
1103	= 0.993 =
1104
1105	* WORDPRESS 2.5.1 COMPATIBILITY: FeedWordPress should now be compatible
1106	with WordPress 2.5.1.
1107
1108	* WORDPRESS 2.5 INTERFACE IMPROVEMENTS: FeedWordPress's Dashboard
1109	interface has undergone several cosmetic changes that should help it
1110	integrate better with the WordPress Dashboard interface in WordPress
1111	version 2.5.x.
1112
1113	* SYNDICATED POSTS CAN BE MARKED AS "PENDING REVIEW": WordPress 2.3 users
1114	can now take advantage of WordPress's new "Pending Review" features for
1115	incoming syndicated posts. Posts marked as "Pending Review" are not
1116	published immediately, but are marked as ready to be reviewed by an
1117	Administrator or Editor, who can then choose to publish the post or
1118	hold it back. If you want to review syndicated posts from a particular
1119	feed, or from all feeds, before they are posted, then use
1120	Syndication --> Syndicated Sites --> Edit or Syndication --> Options to
1121	change the settings for handling new posts.
1122
1123	* AWARE OF NEW URI FOR del.icio.us FEEDS: Previous releases of
1124	FeedWordPress already automatically split del.icio.us tags up
1125	appropriately appropriately when generating categories. (del.icio.us
1126	feeds smoosh all the tags into a single `<dc:subject>` element,
1127	separated by spaces; FeedWordPress un-smooshes them into multiple
1128	categories by separating them at whitespace.) Unfortunately, del.icio.us
1129	recently broke the existing behavior by changing host names for their
1130	feeds from del.icio.us to feeds.delicious.com. Version 0.993 accounts
1131	for the new host name and un-breaks the tag splitting.
1132
1133	= 0.992 =
1134
1135	* AUTHOR RE-MAPPING: FeedWordPress now offers considerable control over
1136	how author names on a feed are translated into usernames within the
1137	WordPress database. When a post by an unrecognized author comes in,
1138	Administrators can now specify any username as the default username to
1139	assign the post to by setting the option in Syndication --> Options
1140	(formerly FeedWordPress only allowed you to assign such posts to user
1141	#1, the site administrator). Administrators can also create re-mapping
1142	rules for particular feeds (under Syndication --> Syndicated Sites -->
1143	Edit), so that (for example) any posts attributed to "Administrator"
1144	on the feed <http://praxeology.net/blog/feed/> will be assigned to
1145	a user named "Roderick T. Long," rather than a user named
1146	"Administrator." These settings also allow administrators to filter out
1147	posts by particular users, and to control what will happen when
1148	FeedWordPress encounters a post by an unrecognized user on that
1149	particular feed.
1150
1151	* BUG RELATED TO URIS CONTAINING AMPERSAND CHARACTERS FIXED: A bug in
1152	WordPress 2.x's handling of URIs in Blogroll links created problems for
1153	updating any feeds whose URIs included an ampersand character, such as
1154	Google News RSS feeds and other feeds that have multiple parameters
1155	passed through HTTP GET. If you experienced this bug, the most likely
1156	effect was that FeedWordPress simply would not import new posts from a
1157	feed when instructred to do so, returning a "0 new posts" response. In
1158	other cases, it might lead to unpredictable results from feed updates,
1159	such as importing posts which were not contained in the feed being
1160	syndicated, but which did appear elsewhere on the same website. This bug
1161	has, hopefully, been resolved, by correcting for the bug in WordPress.
1162
1163	= 0.991 =
1164
1165	* WORDPRESS MU COMPATIBILITY: FeedWordPress should now be compatible with
1166	recent releases of WordPress MU. Once FeedWordPress is made available
1167	as a plugin, each individual blog can choose to activate FeedWordPress
1168	and syndicate content from its own set of contributors.
1169
1170	* DISPLAY OF MAGPIE WARNINGS: A number of MagpieRSS warnings or error
1171	messages that were displayed when performing an automatic update are
1172	no longer displayed, unless debugging parameters have been explicitly
1173	enabled.
1174
1175	* BUG RELATED TO INTERNATIONAL CHARACTERS IN AUTHOR NAMES FIXED: Due to a
1176	subtle incompatability between the way that FeedWordPress generated new
1177	user information, and the way that WordPress 2.0 and later added new
1178	authors to the database, FeedWordPress might end up creating duplicate
1179	authors, or throwing a critical error message, when it encountered
1180	authors whose names included international characters. This
1181	incompatability has now been fixed; hopefully, authors with
1182	international characters in their names should now be handled properly.
1183
1184	* `<media:content>` BUG IN MAGPIERSS FIXED: A bug in MagpieRSS's handling
1185	of namespaced elements has been fixed. Among other things, this bug
1186	caused items containing a Yahoo MediaRSS `<media:content>` element (such
1187	as many of the feeds produced by wordpress.com) to be represented
1188	incorrectly, with only a capital "A" where the content of the post
1189	should have been. Feeds containing `<media:content>` elements should now
1190	be syndicated correctly.
1191
1192	* update_feedwordpress PARAMETER: You can now use an HTTP GET parameter
1193	(`update_feedwordpress=1`) to request that FeedWordPress poll its feeds
1194	for updates. When used together with a crontab or other means of
1195	scheduling tasks, this means that you can keep your blog automatically
1196	updated on a regular schedule, even if you do not choose to use the
1197	cron-less automatic updates option.
1198
1199	* Some minor interface-related bugs were also fixed.
1200
1201
1202	= 0.99 =
1203
1204	Version 0.99 adds several significant new features, fixes some bugs, and
1205	provides compatability with WordPress 2.2.x and 2.3.x.
1206
1207	* WORDPRESS 2.2 AND 2.3 COMPATIBILITY: FeedWordPress should now be
1208	compatible with WordPress version 2.2 and the upcoming WordPress
1209	version 2.3. In particular, it has been tested extensively against
1210	WordPress 2.2.3 and WordPress 2.3 Release Candidate 1.
1211
1212	* AUTOMATIC UPDATES WITHOUT CRON: FeedWordPress now allows you to
1213	automatically schedule checks for new posts without using external task
1214	scheduling tools such as cron. In order to enable automatic updates, go
1215	to Syndication --> Options and set "Check for new posts" to
1216	"automatically." For details, see "Automatic Feed Updates" in
1217	README.text.
1218
1219	An important side-effect of the changes to the update system is that if
1220	you were previously using the cron job and the `update-feeds.php` script
1221	to schedule updates, you need to change your cron set-up. The old
1222	`update-feeds.php` script no longer exists. Instead, if you wish to use
1223	a cron job to guarantee updates on a particular schedule, you should
1224	have the cron job fetch the front page of your blog (for example, by
1225	using `curl http://www.zyx.com/blog/ > /dev/null`) instead of activating
1226	the `update-feeds.php` script. If automatic updates have been enabled,
1227	fetching the front page will automatically trigger the update process.
1228
1229	* INTERFACE REORGANIZATION: All FeedWordPress functions are now located
1230	under a top-level "Syndication" menu in the WordPress Dashboard. To
1231	manage the list of syndicated sites, manually check for new posts on
1232	one or more feeds, or syndicate a new site, you should use the main page
1233	under Syndication. To change global settings for FeedWordPress,
1234	you should use Syndication --> Options.
1235
1236	* FILE STRUCTURE REORGANIZATION: Due to a combination of changing styles
1237	for FeedWordPress plugins and lingering bugs in the FeedWordPress admin
1238	menu code, the code for FeedWordPress is now contained in two different
1239	PHP files, which should be installed together in a subdirectory of your
1240	plugins directory named `feedwordpress`. (See README.text for
1241	installation and upgrade instructions relating to the change.)
1242
1243	* MULTIPLE CATEGORIES SETTING: Some feeds use non-standard methods to
1244	indicate multiple categories within a single category element. (The most
1245	popular site to do this is del.icio.us, which separates tags with a
1246	space.) FeedWordPress now allows you to set an optional setting, for any
1247	feed which does this, indicating the character or characters used to
1248	divide multiple categories, using a Perl-compatible regular expression.
1249	(In the case of del.icio.us feeds, FeedWordPress will automatically use
1250	\s for the pattern without your having to do any further configuration.)
1251	To turn this setting on, simply use the "Edit" link for the feed that
1252	you want to turn it on for.
1253
1254	* REGULAR EXPRESSION BUG FIXED: Eliminated a minor bug in the regular
1255	expressions for e-mail addresses (used in parsing RSS `author`
1256	elements), which could produce unsightly error messages for some users
1257	parsing RSS 2.0 feeds.
1258
1259	* DATE / UPDATE BUG FIXED: A bug in date handling was eliminated that may
1260	have caused problems if any of (1) WordPress, or (2) PHP, or (3) your
1261	web server, or (4) your MySQL server, has been set to use a different
1262	time zone from the one that any of the others is set to use. If
1263	FeedWordPress has not been properly updating updated posts, or has been
1264	updating posts when there shouldn't be any changes for the update, this
1265	release may solve that problem.
1266
1267	* GOOGLE READER BUGS FIXED: A couple of bugs that made it difficult for
1268	FeedWordPress to interact with Google Reader public feeds have been
1269	fixed. Firstly, if you encountered an error message reading "There was a
1270	problem adding the newsfeed. [SQL: ]" when you tried to add the feed,
1271	the cause of this error has been fixed. Secondly, if you succeeded in
1272	getting FeedWordPress to check a Google Reader feed, only to find that
1273	the title of posts had junk squashed on to the end of them, that bug
1274	has been fixed too. To fix this bug, you must install the newest version
1275	of the optional MagpieRSS upgrade.
1276
1277	* FILTER PARAMETERS: Due to an old, old bug in WordPress 1.5.0 (which was
1278	what was available back when I first wrote the filter interface),
1279	FeedWordPress has traditionally only passed one parameter to
1280	syndicated_item and syndicated_post filters functions -- an array
1281	containing either the Magpie representation of a syndicated item from
1282	the feed, or the database representation of a post about to be inserted
1283	into the WordPress database. If you needed information about the feed
1284	that the item came from, this was accessible only through a pair of
1285	global variables, $fwp_channel and $fwp_feedmeta.
1286
1287	Since it's been a pretty long time since WordPress 1.5.0 was in
1288	widespread usage, I have gone ahead and added an optional second
1289	parameter to the invocation of the syndicated_item and syndicated_post
1290	filters. If you have written a filter for FeedWordPress that uses either
1291	of these hooks, you can now register that filter to accept 2 parameters.
1292	If you do so, the second parameter will be a SyndicatedPost object,
1293	which, among other things, allows you to access information about the
1294	feed from which an item is syndicated using the $post->feed and the
1295	$post->feedmeta elements (where $post is the name of the second
1296	parameter).
1297
1298	NOTE THAT THE OLD GLOBAL VARIABLES ARE STILL AVAILABLE, for the time
1299	being at least, so existing filters will not break with the upgrade.
1300	They should be considered deprecated, however, and may be eliminated in
1301	the future.
1302
1303	* FILTER CHANGE / BUGFIX: the array that is passed as the first argument
1304	syndicated_post filters no longer is no longer backslash-escaped for
1305	MySQL when filters are called. This was originally a bug, or an
1306	oversight; the contents of the array should only be escaped for the
1307	database after they have gone through all filters. IF YOU HAVE WRITTEN
1308	ANY syndicated_post FILTERS THAT PRESUME THE OLD BEHAVIOR OF PASSING IN
1309	STRINGS THAT ARE ALREADY BACKSLASH-ESCAPED, UPDATE YOUR FILTERS
1310	ACCORDINGLY.
1311
1312	* OTHER MINOR BUGFIXES AND INTERNAL CHANGES: The internal architecture of
1313	FeedWordPress has been significantly changed to make the code more
1314	modular and clean; hopefully this should help reduce the number of
1315	compatibility updates that are needed, and make them easier and quicker
1316	when they are needed.
1317
1318	= 0.981 =
1319
1320	Version 0.981 is a narrowly targeted bugfix and compatibility release, whose
1321	main purpose is to resolve a major outstanding problem: the incompatibility
1322	between version 0.98 of WordPress and the recently released WordPress 2.1.
1323
1324	* WORDPRESS 2.1 COMPATIBILITY: FeedWordPress is now compatible with
1325	WordPress 2.1, as well as retaining its existing support for WordPress
1326	2.0 and 1.5. Incompatibilities that resulted in database warnings, fatal
1327	errors, and which prevented FeedWordPress from syndicating new posts,
1328	have been eliminated.
1329
1330	* RSS-FUNCTIONS.PHP RENAMED TO RSS.PHP: if you use the upgraded MagpieRSS
1331	replacement that's included with FeedWordPress, be sure to note that
1332	there are now two files to upload from the `OPTIONAL/wp-includes`
1333	subdirectory in order to carry out the upgrade: rss-functions.php and
1334	rss.php. It is necessary to upload both files, due to a change in
1335	the file naming scheme in WordPress 2.1, and it is necessary to do so
1336	whether you are using WordPress 2.1 or not. If you only upload the
1337	`rss-functions.php` file as in previous installations you will not have
1338	a working copy of MagpieRSS; the rss.php file contains the actual code.
1339
1340	* DATE BUG AFFECTING SOME PHP INSTALLATIONS RESOLVED: due to a subtle bug
1341	in parse_w3cdtf(), some installations of PHP encountered problems with
1342	FeedWordPress's attempt to date posts, which would cause some new posts
1343	on Atom feeds to be dated as if they had apppeared in 1969 or 1970
1344	(thus, effectively, never appearing on front page at all). This bug in
1345	the date handling should now be fixed.
1346
1347	* PHP <?=...?> SHORT FORM ELIMINATED: some installations of PHP do not
1348	allow the <?=...?> short form for printing PHP values, which was used
1349	extensively in the FeedWordPress interface code. Since this could cause
1350	fatal errors for users with the wrong installation of PHP, the short
1351	form has been replaced with full PHP echo statements, and is no longer
1352	used in FeedWordPress.
1353
1354	* BETTER USER INTERFACE INTEGRATION WITH WORDPRESS 2.x: Some minor changes
1355	have been made to help the FeedWordPress interface pages blend in better
1356	with the user interface when running under WordPress 2.x.
1357
1358	* GLOBAL CATEGORIES BUG RESOLVED: a bug that prevented some users from
1359	setting one or more categories to apply to syndicated posts from all
1360	feeds (using the checkbox interface under Options --> Syndication) has
1361	been resolved.
1362
1363	= 0.98 =
1364
1365	* WORDPRESS 2.0 COMPATIBILITY: This is a narrowly-targeted release to
1366	solve a major outstanding problem. FeedWordPress is now compatible with
1367	both WordPress 1.5 and WordPress 2.0. Incompatibilities that caused
1368	fatal SQL errors, and a more subtle bug with off-kilter counts of posts
1369	under a given category, have been resolved. FeedWordPress tests for
1370	database schema using the global $wp_db_version variable (if null, then
1371	we presume that we're dealing with WordPress 1.5).
1372
1373	NOTE: I have not fully tested FeedWordPress with WordPress 2.0.
1374	Further testing may reveal more bugs. However, you should now be able
1375	to get at least basic FeedWordPress functionality up and running.
1376
1377	* AUTHOR MATCHING: FeedWordPress tests several fields to see if it can
1378	identify the author of the post as a user already in the WordPress user
1379	database. In previous versions, it tested the user login, the nickname,
1380	and tested for "aliases" listed in the Profile (see documentation). FWP
1381	now also matches authors on the basis of e-mail address (if an e-mail
1382	address is present). This is particularly helpful for formats such as
1383	RSS 2.0, in which authors are primarily identified by e-mail addresses.
1384
1385	= 0.97 =
1386
1387	* INSTALLATION PROCEDURE: Some of the changes between 0.96 and 0.97
1388	require upgrades to the meta-data stored by FeedWordPress to work
1389	properly. Thus, if you are upgrading from 0.96 or earlier to 0.97, most
1390	FeedWordPress operations (including updates and template functions)
1391	WILL BE DISABLED until you run the upgrade procedure. Fortunately,
1392	running the upgrade procedure is easy: just go to either Options -->
1393	Syndication or Links --> Syndicated in the WordPress Dashboard and press
1394	the button.
1395
1396	* FEED FORMAT SUPPORT: Support has been added for the Atom 1.0 IETF
1397	standard. Several other elements are also newly supported
1398	(dcterms:created, dcterms:issued, dcterms:modified, dc:identifier,
1399	proper support for the RSS 2.0 guid element, the RSS 2.0 author element,
1400	the use of Atom author or Dublin Core dc:creator constructs at the feed
1401	level to identify the author of individual items, etc.)
1402
1403	N.B.: full support of several Atom 1.0 features, such as categories
1404	and enclosures, requires you to install the optional rss-functions.php
1405	upgrade in your wp-includes directory.
1406
1407	* BUG FIX: Running `update-feeds.php` from command line or crontab
1408	returned "I don't syndicate..." errors. It turns out that WordPress
1409	sometimes tramples on the internal PHP superglobals that I depended on
1410	to determine whether or not the script was being invoked from the
1411	command line. This has been fixed (the variables are now checked
1412	before WordPress can trample them). Note that `update-feeds.php` has
1413	been thoroughly overhauled anyway; see below for details.
1414
1415	* BUG FIX: Duplicate categories or author names. Fixed two bugs that could
1416	create duplicate author and/or category names when the name contained
1417	either (a) certain international characters (causing a mismatch between
1418	MySQL and PHP's handling of lowercasing text), or (b) characters that
1419	have a special meaning in regular expressions (causing MySQL errors when
1420	looking for the author or category due to regexp syntax errors). These
1421	should now be fixed thanks to careful escaping of names that go into
1422	regular expressions and careful matching of lowercasing functions
1423	(comparing results from PHP only to other results from PHP, and results
1424	from MySQL only to other results from MySQL).
1425
1426	* BUG FIX: Items dated December 31, 1969 should appear less often. The
1427	function for parsing W3C date-time format dates that ships with
1428	MagpieRSS can only correctly parse fully-specified dates with a
1429	fully-specified time, but valid W3C date-time format dates may omit the
1430	time, the day of the month, or even the month. Some feeds in the wild
1431	date their items with coarse-grained dates, so the optional
1432	`rss-functions.php` upgrade now includes a more flexible parse_w3cdtf()
1433	function that will work with both coarse-grained and fully-specified
1434	dates. (If parts of the date or the time are omitted, they are filled in
1435	with values based on the current time, so '2005-09-10' will be dated to
1436	the current time on that day; '2004' will be dated to this day and time
1437	one year ago.
1438
1439	N.B.: This fix is only available in the optional `rss-functions.php`
1440	upgrade.
1441
1442	* BUG FIX: Evil use of HTTP GET has been undone. The WordPress interface
1443	is riddled with inappropriate (non-idempotent) uses of HTTP GET queries
1444	(ordinary links that make the server do something with significant
1445	side-effects, such as deleting a post or a link from the database).
1446	FeedWordPress did some of this too, especially in places where it aped
1447	the WordPress interface (e.g. the "Delete" links in Links -->
1448	Syndicated). That's bad business, though. I've changed the interface so
1449	that all the examples of improper side-effects that I can find now
1450	require an HTTP POST to take effect. I think I got pretty much
1451	everything; if there's anything that I missed, let me know.
1452
1453	Further reading: [Sam Ruby 2005-05-06: This Stuff Matters](http://www.intertwingly.net/blog/2005/05/06/This-Stuff-Matters)
1454
1455	* BUG FIX: Categories applied by `cats` setting should no longer prevent
1456	category-based filtering from working. In FeedWordPress, you can (1)
1457	apply certain categories to all syndicated posts, or all posts from
1458	a particular feed; and (2) filter out all posts that don't match one
1459	of the categories that are already in the WordPress database (allowing
1460	for simple category-based filtering; just load up WordPress with the
1461	categories you want to accept, and then tell FeedWordPress not to create
1462	new ones). However, the way that (1) and (2) were implemented meant that
1463	you couldn't effectively use them together; once you applied a known
1464	category to all syndicated posts from a particular feed, it meant that
1465	they'd have at least one familiar category (the category or categories
1466	you were applying), and that would get all posts past the filter no
1467	matter what categories they were originally from.
1468
1469	Well, no longer. You can still apply categories to all syndicated posts
1470	(using either Syndication --> Options, or the feed-level settings under
1471	Links --> Syndicated). But these categories are not applied to the post
1472	until after it has already passed by the "familiar categories" filter.
1473	So now, if you want, you can do category filtering and then apply as
1474	many categories as you please to all and only posts that pass the filter.
1475
1476	* BUG FIX: Other minor typos and HTML gaffes were fixed along the way.
1477
1478	* PERFORMANCE: get_feed_meta() no longer hits the database for information
1479	on every call; it now caches link data in memory, so FeedWordPress only
1480	goes to the database once for each syndicated link. This may
1481	substantially improve performance if your database server resources
1482	are tight and your templates make a lot of use of custom settings from
1483	get_feed_meta().
1484
1485	* API CHANGE: Link ID numbers, rather than RSS URIs, are now used to
1486	identify the feed from which a post is syndicated when you use template
1487	functions such as get_feed_meta(). The practical upshot of this is you
1488	can switch feeds, or change the feed address for a particular syndicated
1489	site, without breaking your templates for all the posts that were
1490	syndicated from the earlier URI.
1491
1492	* API CHANGE: if you have plugins or templates that make use of the
1493	get_feed_meta() function or the $fwp_feedmeta global, note that the
1494	data formerly located under the `uri` and `name` fields is now located
1495	under the `link/uri` field and the `link/name` field, respectively. Note
1496	also that you can access the link ID number for any given feed under the
1497	global $fwp_feedmeta['link/id'] (in plugins) or
1498	get_feed_meta('link/id') (in a template in post contexts).
1499
1500	* FEATURE: the settings for individual feeds can now be edited using a
1501	humane interface (where formerly you had to tweak key-value pairs in the
1502	Link Notes section). To edit settings for a feed, pick the feed that you
1503	want under Links --> Syndicated and click the Edit link.
1504
1505	* FEATURE: The "Unsubscribe" button (formerly "Delete") in Links -->
1506	Syndicated now offers three options for unsubscribing from a feed: (1)
1507	turning off the subscription without deleting the feed data or affecting
1508	posts that were syndicated from the feed (this works by setting the Link
1509	for the feed as "invisible"); (2) deleting the feed data and all of the
1510	posts that were syndicated from the feed; or (3) deleting the feed data
1511	and keeping the posts that were syndicated from the feed
1512	setting the Link to "Invisible" (meaning that it will not be displayed
1513	in lists of the site links on the front page, and it won't be checked
1514	for updates; (2) deleting the Link and all of the posts that were
1515	syndicated from its feed; or (3) deleting the feed data but keeping the
1516	posts that were syndicated (which will henceforward be treated as if
1517	they were local rather than syndicated posts). (Note that (1) is usually
1518	the best option for aggregator sites, unless you want to clean up the
1519	results of an error or a test.)
1520
1521	* FEATURE / BUG FIX: If you have been receiving mysterious "I don't
1522	syndicate...", or "(local) HTTP status code was not 200", or "(local)
1523	transport error - could not open socket", or "parse error - not well
1524	formed" errors, then this update may solve your problems, and if it does
1525	not solve them, it will at least make the reasons for the problems
1526	easier to understand. That's because I've overhauled the way that
1527	FeedWordPress goes about updating feeds.
1528
1529	If you use the command-line PHP scripting method to run scheduled
1530	updates, then not much should change for you, except for fewer
1531	mysterious errors. If you have done updates by sending periodic HTTP
1532	requests to <http://your-blog.com/path/wp-content/update-feeds.php>,
1533	then the details have changed somewhat; mostly in such a way as to make
1534	things easier on you. See the README file or online documentation on
1535	Staying Current for the details.
1536
1537	* FEATURE: FeedWordPress now features a more sophisticated system for
1538	timed updates. Instead of polling every subscribed feed for updates
1539	each time `update-feeds.php` is run, FeedWordPress now keeps track of
1540	the last time it polled each feed, and only polls them again after a
1541	certain period of time has passed. The amount of time is normally set
1542	randomly for each feed, in a period between 30 minutes and 2 hours (so
1543	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
1544	directly by the feed, which brings us to ...
1545
1546	* FEATURE: FeedWordPress now respects the settings in the `ttl` and
1547	Syndication Module RSS elements. Feeds with these elements set will not
1548	be polled any more frequently than they indicate with these feeds unless
1549	the user manually forces FeedWordPress to poll the feed (see Links -->
1550	Syndicated --> Edit settings).
1551
1552	= 0.96 =
1553
1554	* FEATURE: support has been added for enclosures in RSS 2.0 and Atom
1555	0.6+ newsfeeds. WordPress already supports adding enclosures to an
1556	item; FeedWordPress merely gets the information on the enclosure
1557	from the feed it is syndicating and plugs that information directly
1558	into the WordPress database so that (among other things) that post
1559	will have its enclosure listed in your blog's RSS 2 newsfeed.
1560
1561	Note that enclosure support requires using the optional MagpieRSS
1562	upgrade (i.e., replacing your `wp-includes/rss-functions.php` with
1563	`OPTIONAL/wp-includes/rss-functions.php` from the FWP archive)
1564
1565	* FEATURE: for completeness's sake, there is now a feed setting,
1566	`hardcode url`, that allows you to set the URI for the front page
1567	of a contributor's website manually (that is, prevent it from being
1568	automatically updated from the feed channel link on each update). To
1569	set the URI manually, put a line like this in the Link Notes section
1570	of a feed:
1571
1572	hardcode url: yes
1573
1574	You can also instruct FeedWordPress to use hardcoded URIs by default
1575	on all feeds using Options --> Syndication
1576
1577	* FEATURE: by default, when FeedWordPress finds new syndicated posts,
1578	it (1) publishes them immediately, (2) turns comments off, and (3)
1579	turns trackback / pingback pings off. You can now alter all three
1580	default behaviors (e.g., to allow pings on syndicated posts, or to
1581	send newly-syndicated posts to the draft pile for moderation) using
1582	Options --> Syndication
1583
1584
1585	= From 0.91 to 0.95 =
1586
1587	* BUG FIX: Fixed an obscure bug in the handling of categories:
1588	categories with trailing whitespace could cause categories with
1589	duplicate names to be created. This no longer happens. While I was
1590	at it I tightened up the operation of
1591	FeedWordPress::lookup_categories() a bit in general.
1592
1593	* FEATURE DEPRECATED: the feed setting `hardcode categories` is now
1594	deprecated in favor of `unknown categories` (see below), which
1595	allows you to strip off any syndication categories not already in
1596	your database using `unknown categories: default` or `unknown
1597	categories: filter`. If you have `hardcode categories: yes` set on a
1598	feed, this will be treated as `unknown categories: default` (i.e.,
1599	no new categories will be added, but if a post doesn't match any of
1600	the categories it will be added in the default category--usually
1601	"Uncategorized" or "General").
1602
1603	* FEATURE: You can now set global defaults as to whether or not
1604	FeedWordPress will update the Link Name and Link Description
1605	settings for feeds automatically from the feed title and feed
1606	tagline. (By default, it does, as it has in past versions.) Whether
1607	this behavior is turned on or off, you can still override the
1608	default behavior using feed settings of `hardcode name: yes`,
1609	`hardcode name: no`, `hardcode description: yes`, or `hardcode
1610	description: no`.
1611
1612	* FEATURE: Users can now provide one or several "aliases" for an
1613	author, just as they can for a category. For example, to make
1614	FeedWordPress treat posts by "Joseph Cardinal Ratzinger" and "Pope
1615	Benedict XVI" as by the same author, edit the user profile for Pope
1616	Benedict XVI and add a line like this to the "User profile" field:
1617
1618	a.k.a.: Joseph Cardinal Ratzinger
1619
1620	You can add several aliases, each on a line by itself. You can also
1621	add any other text you like to the Profile without interfering with
1622	the aliases.
1623
1624	* FEATURE: Users can now choose how to handle syndicated posts that
1625	are in unfamiliar categories or by unfamiliar authors (i.e.,
1626	categories or authors whose names are not yet in the WordPress
1627	database). By default, FeedWordPress will (as before) create a new
1628	category (or new author) and use it for the current post and any
1629	future posts. This behavior can be changed, either for all feeds or
1630	for one or another particular feed.
1631
1632	There are now three different options for an unfamiliar author: (1)
1633	FeedWordPress can create a new author account and attribute the
1634	syndicated post to the new account; (2) FeedWordPress can attribute
1635	the post to an author if the author's name is familiar, and to a
1636	default author (currently, this means the Site Administrator
1637	account) if it is not; (3) FeedWordPress can drop posts by
1638	unfamiliar authors and syndicate only posts by authors who are
1639	already in the database.
1640
1641	There are, similarly, two different options for an unfamiliar
1642	category: (1) FeedWordPress can create new categories and place the
1643	syndicated post in them; (2) FeedWordPress can drop the unfamiliar
1644	categories and place syndicated posts only in categories that it is
1645	already familiar with. In addition, FeedWordPress 0.95 lets you
1646	choose whether posts that are in no familiar categories should be
1647	syndicated (and placed in the default category for the blog) or
1648	simply dropped.
1649
1650	You can set the default behavior for both authors and categories
1651	using the settings in Options --> Syndication. You can also set
1652	different behavior for specific feeds by adding the `unfamiliar
1653	author` and / or `unfamiliar categories` settings to the Link Notes
1654	section of a feed:
1655
1656	unfamiliar author: (create\|default\|filter)
1657	unfamiliar categories: (create\|default\|filter)
1658
1659	A setting of `unfamiliar author: create` will make FeedWordPress
1660	create new authors to match unfamiliar author names *for this feed
1661	alone*. A setting of `unfamiliar author: default` will make it
1662	assign posts from unfamiliar authors to the default user account. A
1663	setting of `unfamiliar author: filter` will cause all posts (from
1664	this feed alone) to be dropped unless they are by an author already
1665	listed in the database. Similiarly, `unfamiliar categories: create`
1666	will make FeedWordPress create new categories to match unfamiliar
1667	category names for this feed alone; `unfamiliar categories:
1668	default` will cause it to drop any unfamiliar category names; and
1669	`unfamiliar categories: filter` will cause it to both drop any
1670	unfamiliar category names and to only syndicate posts that are
1671	placed in one or more familiar categories.
1672
1673	These two new features allow users to do some coarse-grained
1674	filtering without having to write a PHP filter. Specifically, they
1675	offer an easy way for you to filter feeds by category or by author.
1676	Suppose, for example, that you only wanted to syndicate posts that
1677	your contributors place in the "Llamas" category. You could do so by
1678	setting up your installation of WordPress so that the only category
1679	in the database is "Llamas," and then use Options --> Syndication to
1680	set "Unfamiliar categories" to "don't create new categories and
1681	don't syndicate posts unless they match at least one familiar
1682	category". Now, when you update, only posts in the "Llamas" category
1683	will be syndicated by FeedWordPress.
1684
1685	Similarly, if you wanted to filter one particular feed so that only
1686	posts by (for example) the author "Earl J. Llama" were syndicated to
1687	your site, you could do so by creating a user account for Earl J.
1688	Llama, then adding the following line to the settings for the feed
1689	in Link Notes:
1690
1691	unfamiliar author: filter
1692
1693	This will cause any posts from this feed that are not authored by
1694	Earl J. Llama to be discarded, and only the posts by Earl J. Llama
1695	will be syndicated. (If the setting is used on one specific feed, it
1696	will not affect how posts from other feeds are syndicated.)
1697
1698	== License ==
1699
1700	The FeedWordPress plugin is copyright © 2005-2010 by Charles Johnson. It uses
1701	code derived or translated from:
1702
1703	- [wp-rss-aggregate.php][] by [Kellan Elliot-McCrea](kellan@protest.net)
1704	- [MagpieRSS][] by [Kellan Elliot-McCrea](kellan@protest.net)
1705	- [Ultra-Liberal Feed Finder][] by [Mark Pilgrim](mark@diveintomark.org)
1706	- [WordPress Blog Tool and Publishing Platform](http://wordpress.org/)
1707
1708	according to the terms of the [GNU General Public License][].
1709
1710	This program is free software; you can redistribute it and/or modify it under
1711	the terms of the [GNU General Public License][] as published by the Free
1712	Software Foundation; either version 2 of the License, or (at your option) any
1713	later version.
1714
1715	This program is distributed in the hope that it will be useful, but WITHOUT ANY
1716	WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A
1717	PARTICULAR PURPOSE. See the GNU General Public License for more details.
1718
1719	[wp-rss-aggregate.php]: http://laughingmeme.org/archives/002203.html
1720	[MagpieRSS]: http://magpierss.sourceforge.net/
1721	[HTTP Navigator 2]: http://www.keyvan.net/2004/11/16/http-navigator/
1722	[Ultra-Liberal Feed Finder]: http://diveintomark.org/projects/feed_finder/
1723	[GNU General Public License]: http://www.gnu.org/copyleft/gpl.html
1724
1725