| @@ -1,7 +1,76 @@ | ||
| 1 | 1 | FeedWordPress Change Log |
| 2 | 2 | ======================== |
| 3 | 3 | |
| 4 | +Changes from 0.98 to 0.981 | |
| 5 | +-------------------------- | |
| 6 | + | |
| 7 | +Version 0.981 is a narrowly targeted bugfix and compatibility release, whose | |
| 8 | +main purpose is to resolve a major outstanding problem: the incompatibility | |
| 9 | +between version 0.98 of WordPress and the recently released WordPress 2.1. | |
| 10 | + | |
| 11 | +* WORDPRESS 2.1 COMPATIBILITY: FeedWordPress is now compatible with | |
| 12 | + WordPress 2.1, as well as retaining its existing support for WordPress | |
| 13 | + 2.0 and 1.5. Incompatibilities that resulted in database warnings, fatal | |
| 14 | + errors, and which prevented FeedWordPress from syndicating new posts, | |
| 15 | + have been eliminated. | |
| 16 | + | |
| 17 | +* RSS-FUNCTIONS.PHP RENAMED TO RSS.PHP: if you use the upgraded MagpieRSS | |
| 18 | + replacement that's included with FeedWordPress, be sure to note that | |
| 19 | + there are now *two* files to upload from the `OPTIONAL/wp-includes` | |
| 20 | + subdirectory in order to carry out the upgrade: rss-functions.php and | |
| 21 | + rss.php. **It is necessary to upload both files**, due to a change in | |
| 22 | + the file naming scheme in WordPress 2.1, and it is necessary to do so | |
| 23 | + whether you are using WordPress 2.1 or not. If you only upload the | |
| 24 | + `rss-functions.php` file as in previous installations you will not have | |
| 25 | + a working copy of MagpieRSS; the rss.php file contains the actual code. | |
| 26 | + | |
| 27 | +* DATE BUG AFFECTING SOME PHP INSTALLATIONS RESOLVED: due to a subtle bug | |
| 28 | + in parse_w3cdtf(), some installations of PHP encountered problems with | |
| 29 | + FeedWordPress's attempt to date posts, which would cause some new posts | |
| 30 | + on Atom feeds to be dated as if they had apppeared in 1969 or 1970 | |
| 31 | + (thus, effectively, never appearing on front apge at all). This bug in | |
| 32 | + the date handling should now be fixed. | |
| 33 | + | |
| 34 | +* PHP <?=...?> SHORT FORM ELIMINATED: some installations of PHP do not | |
| 35 | + allow the <?=...?> short form for printing PHP values, which was used | |
| 36 | + extensively in the FeedWordPress interface code. Since this could cause | |
| 37 | + fatal errors for users with the wrong installation of PHP, the short | |
| 38 | + form has been replaced with full PHP echo statements, and is no longer | |
| 39 | + used in FeedWordPress. | |
| 40 | + | |
| 41 | +* BETTER USER INTERFACE INTEGRATION WITH WORDPRESS 2.x: Some minor changes | |
| 42 | + have been made to help the FeedWordPress interface pages blend in better | |
| 43 | + with the user interface when running under WordPress 2.x. | |
| 44 | + | |
| 45 | +* GLOBAL CATEGORIES BUG RESOLVED: a bug that prevented some users from | |
| 46 | + setting one or more categories to apply to syndicated posts from all | |
| 47 | + feeds (using the checkbox interface under Options --> Syndication) has | |
| 48 | + been resolved. | |
| 49 | + | |
| 50 | +Changes from 0.97 to 0.98 | |
| 51 | +-------------------------- | |
| 52 | + | |
| 53 | +* WORDPRESS 2.0 COMPATIBILITY: This is a narrowly-targeted release to | |
| 54 | + solve a major outstanding problem. FeedWordPress is now compatible with | |
| 55 | + both WordPress 1.5 and WordPress 2.0. Incompatibilities that caused | |
| 56 | + fatal SQL errors, and a more subtle bug with off-kilter counts of posts | |
| 57 | + under a given category, have been resolved. FeedWordPress tests for | |
| 58 | + database schema using the global $wp_db_version variable (if null, then | |
| 59 | + we presume that we're dealing with WordPress 1.5). | |
| 60 | + | |
| 61 | + NOTE: I have **not** fully tested FeedWordPress with WordPress 2.0. | |
| 62 | + Further testing may reveal more bugs. However, you should now be able | |
| 63 | + to get at least basic FeedWordPress functionality up and running. | |
| 64 | + | |
| 65 | +* AUTHOR MATCHING: FeedWordPress tests several fields to see if it can | |
| 66 | + identify the author of the post as a user already in the WordPress user | |
| 67 | + database. In previous versions, it tested the user login, the nickname, | |
| 68 | + and tested for "aliases" listed in the Profile (see documentation). FWP | |
| 69 | + now also matches authors on the basis of e-mail address (*if* an e-mail | |
| 70 | + address is present). This is particularly helpful for formats such as | |
| 71 | + RSS 2.0, in which authors are primarily identified by e-mail addresses. | |
| 72 | + | |
| 4 | 73 | Changes from 0.96 to 0.97 |
| 5 | 74 | ------------------------- |
| 6 | 75 | |
| 7 | 76 | * INSTALLATION PROCEDURE: Some of the changes between 0.96 and 0.97 |
