PluginProbe
FeedWordPress / 2008.1101
FeedWordPress v2008.1101
trunk 0.8 0.9 0.91 0.95 0.96 0.97 0.98 0.981 0.99 0.991 0.992 0.993 2008.1030 2008.1101 2008.1105 2008.1214 2009.0612 2009.0613 2009.0618 2009.0707 2009.1111 2009.1112 2010.0127 2010.0528 All 65 releases
← All changes | ChangeLog.text +183 -0 0.992008.1101 View file →
@@ -1,7 +1,190 @@
1 1 FeedWordPress Change Log
2 2 ========================
3 3
4 +Changes from 2008.1030 to 2008.1101
5 +-----------------------------------
6 +
7 +* INTERFACE BUG THAT PREVENTED ADDING NEW SITES FIXED: The UI reforms in
8 + FWP 2008.1030 unintentionally introduced a bug that prevents clean
9 + installations of FeedWordPress from providing an input box for adding
10 + new feeds to the list of syndicated feeds. This bug has been fixed.
11 +
12 +Changes from 0.993 to 2008.1030
13 +-------------------------------
14 +
15 +* WORDPRESS 2.6 COMPATABILITY: FeedWordPress should now be compatible with
16 + WordPress 2.6, and should work more or less seamlessly with the new post
17 + revision system. A bug which caused multiple new revisions to be created
18 + for posts on certain feeds, regardless of whether or not the item had
19 + been updated, has been fixed.
20 +
21 +* INTERFACE IMPROVEMENTS: The user interface has been substantially
22 + restyled to fit in better with the visual style of WordPress 2.5 and
23 + 2.6.
24 +
25 +* YOUTUBE BUG FIXED: POSTS SYNDICATED THROUGH AN AUTOMATIC UPDATE ARE NO
26 + LONGER STRIPPED OF `<OBJECT>` TAGS AND CERTAIN OTHER HTML ELEMENTS: Due
27 + to the way that some versions of WordPress process posts that are
28 + inserted into the database when no user is logged in, many users
29 + experienced an issue where YouTube videos and other content using the
30 + HTML `<object>` tag would be stripped out of posts that were syndicated
31 + during an automatic update. (Posts that were syndicated through manual
32 + updates from within the WordPress Dashboard were not affected, because
33 + the issue does not arise when an update is executed under a logged-in
34 + administrator's credentials.) This bug has now been fixed; YouTube
35 + videos and other content using `<object>` tags should now appear
36 + properly in syndicated posts, regardless of the way in which the post
37 + was syndicated.
38 +
39 +* AJAX BUGS FIXED: Bugs which blocked the normal operation of WordPress
40 + 2.5's AJAX interface elements when FeedWordPress was activated have been
41 + fixed.
42 +
43 +* TAG SUPPORT: A couple of features have been introduced to take advantage
44 + of the tagging features in WordPress 2.3.x, 2.5.x, and 2.6.x. Now, when
45 + unfamiliar categories are encountered for posts on a feed, you can
46 + choose for FeedWordPress (1) to drop the category; (2) to drop the
47 + category and to filter out any post that does not match at least one
48 + familiar category; (3) to create a new category with that name, or,
49 + now, you can also have FeedWordPress (4) create a new *tag* with that
50 + name. This option can be set site-wide under Syndication --> Options,
51 + or it can be set on a feed-by-feed basis in a feed's Edit screen.
52 +
53 + In addition, you can now set particular tags to apply to all incoming
54 + syndicated posts, under Syndication --> Options, or you can set tags
55 + to apply to all incoming syndicated posts from a particular feed in that
56 + feed's Edit screen.
57 +
58 +* FORMATTING FILTERS: There is a new option available under Syndication ->
59 + Options which allows users to choose whether or not to expose syndicated
60 + posts to being altered by formatting filters. By default, FeedWordPress
61 + has always protected syndicated posts (which are already in display-ready
62 + HTML when they are syndicated) from being reformatted by formatting
63 + filters. However, this approach means that certain plugins which depend
64 + on formatting filters (for example, to add "Share This" bars or relevant
65 + links to the end of a post) are blocked from working on any syndicated
66 + posts. If you want to use one of these plugins together with
67 + FeedWordPress, you can now do so by changing the "Formatting Filters"
68 + setting from "Protect" to "Expose."
69 +
70 +* **`<atom:source>` ELEMENTS NOW INCLUDED IN ATOM FEED:** Atom 1.0 provides
71 + a standard method for aggregators to indicate information about the original source of
72 + a syndicated post, using the `<atom:source>` element. FeedWordPress now
73 + introduces standard `<atom:source>` elements including the title, homepage, and
74 + feed URI of the source from which a syndicated post was syndicated. Cf.
75 + <http://www.atomenabled.org/developers/syndication/atom-format-spec.php#element.source>
76 +
77 +* MODULARIZATION OF CODE: The code for different elements of FeedWordPress
78 + has been broken out into several modules for easier inspection,
79 + documentation, and maintenance of the code.
80 +
81 +* VERSIONING SCHEME CHANGED: FeedWordPress's feature set has proven stable
82 + enough that it can now be removed from beta status; a good thing, since
83 + I was very quickly running out of version numbers to use. New releases
84 + of FeedWordPress will have version numbers based on the date of their
85 + release.
86 +
87 +Changes from 0.992 to 0.993
88 +---------------------------
89 +
90 +* WORDPRESS 2.5.1 COMPATIBILITY: FeedWordPress should now be compatible
91 + with WordPress 2.5.1.
92 +
93 +* WORDPRESS 2.5 INTERFACE IMPROVEMENTS: FeedWordPress's Dashboard
94 + interface has undergone several cosmetic changes that should help it
95 + integrate better with the WordPress Dashboard interface in WordPress
96 + version 2.5.x.
97 +
98 +* SYNDICATED POSTS CAN BE MARKED AS "PENDING REVIEW": WordPress 2.3 users
99 + can now take advantage of WordPress's new "Pending Review" features for
100 + incoming syndicated posts. Posts marked as "Pending Review" are not
101 + published immediately, but are marked as ready to be reviewed by an
102 + Administrator or Editor, who can then choose to publish the post or
103 + hold it back. If you want to review syndicated posts from a particular
104 + feed, or from all feeds, before they are posted, then use
105 + Syndication --> Syndicated Sites --> Edit or Syndication --> Options to
106 + change the settings for handling new posts.
107 +
108 +* AWARE OF NEW URI FOR del.icio.us FEEDS: Previous releases of
109 + FeedWordPress already automatically split del.icio.us tags up
110 + appropriately appropriately when generating categories. (del.icio.us
111 + feeds smoosh all the tags into a single `<dc:subject>` element,
112 + separated by spaces; FeedWordPress un-smooshes them into multiple
113 + categories by separating them at whitespace.) Unfortunately, del.icio.us
114 + recently broke the existing behavior by changing host names for their
115 + feeds from del.icio.us to feeds.delicious.com. Version 0.993 accounts
116 + for the new host name and un-breaks the tag splitting.
117 +
118 +Changes from 0.991 to 0.992
119 +---------------------------
120 +* AUTHOR RE-MAPPING: FeedWordPress now offers considerable control over
121 + how author names on a feed are translated into usernames within the
122 + WordPress database. When a post by an unrecognized author comes in,
123 + Administrators can now specify any username as the default username to
124 + assign the post to by setting the option in Syndication --> Options
125 + (formerly FeedWordPress only allowed you to assign such posts to user
126 + #1, the site administrator). Administrators can also create re-mapping
127 + rules for particular feeds (under Syndication --> Syndicated Sites -->
128 + Edit), so that (for example) any posts attributed to "Administrator"
129 + on the feed <http://praxeology.net/blog/feed/> will be assigned to
130 + a user named "Roderick T. Long," rather than a user named
131 + "Administrator." These settings also allow administrators to filter out
132 + posts by particular users, and to control what will happen when
133 + FeedWordPress encounters a post by an unrecognized user on that
134 + particular feed.
135 +
136 +* BUG RELATED TO URIS CONTAINING AMPERSAND CHARACTERS FIXED: A bug in
137 + WordPress 2.x's handling of URIs in Blogroll links created problems for
138 + updating any feeds whose URIs included an ampersand character, such as
139 + Google News RSS feeds and other feeds that have multiple parameters
140 + passed through HTTP GET. If you experienced this bug, the most likely
141 + effect was that FeedWordPress simply would not import new posts from a
142 + feed when instructred to do so, returning a "0 new posts" response. In
143 + other cases, it might lead to unpredictable results from feed updates,
144 + such as importing posts which were not contained in the feed being
145 + syndicated, but which did appear elsewhere on the same website. This bug
146 + has, hopefully, been resolved, by correcting for the bug in WordPress.
147 +
148 +Changes from 0.99 to 0.991
149 +--------------------------
150 +* WORDPRESS MU COMPATABILITY: FeedWordPress should now be compatible with
151 + recent releases of WordPress MU. Once FeedWordPress is made available
152 + as a plugin, each individual blog can choose to activate FeedWordPress
153 + and syndicate content from its own set of contributors.
154 +
155 +* DISPLAY OF MAGPIE WARNINGS: A number of MagpieRSS warnings or error
156 + messages that were displayed when performing an automatic update are
157 + no longer displayed, unless debugging parameters have been explicitly
158 + enabled.
159 +
160 +* BUG RELATED TO INTERNATIONAL CHARACTERS IN AUTHOR NAMES FIXED: Due to a
161 + subtle incompatability between the way that FeedWordPress generated new
162 + user information, and the way that WordPress 2.0 and later added new
163 + authors to the database, FeedWordPress might end up creating duplicate
164 + authors, or throwing a critical error message, when it encountered
165 + authors whose names included international characters. This
166 + incompatability has now been fixed; hopefully, authors with
167 + international characters in their names should now be handled properly.
168 +
169 +* media:content BUG IN MAGPIERSS FIXED: A bug in MagpieRSS's handling of
170 + namespaced elements has been fixed. Among other things, this bug caused
171 + items containing a Yahoo MediaRSS `<media:content>` element (such as
172 + many of the feeds produced by wordpress.com) to be represented
173 + incorrectly, with only a capital "A" where the content of the post
174 + should have been. Feeds containing `<media:content>` elements should now
175 + be syndicated correctly.
176 +
177 +* update_feedwordpress PARAMETER: You can now use an HTTP GET parameter
178 + (`update_feedwordpress=1`) to request that FeedWordPress poll its feeds
179 + for updates. When used together with a crontab or other means of
180 + scheduling tasks, this means that you can keep your blog automatically
181 + updated on a regular schedule, even if you do not choose to use the
182 + cron-less automatic updates option.
183 +
184 +* Some minor interface-related bugs were also fixed.
185 +
186 +
4 187 Changes from 0.981 to 0.99
5 188 --------------------------
6 189 Version 0.99 adds several significant new features, fixes some bugs, and
7 190 provides compatability with WordPress 2.2.x and 2.3.x.