Discover and share the best of the web!
Learn more about Digg by taking the tour.
Small WordPress 2.0.6 Bug Leads to FeedBurner Disconnects
neosmart.net — If you are upgrading/have upgraded to WordPress 2.0.6, be sure to read this. "After upgrading to WordPress 2.0.6 or WordPress 2.1 Beta, your FeedBurner feed will, at times, give you an “invalid xml” error, and “FeedMedic” will show you something like this..."
schestowitz- 287 diggs
- digg it
- darkfate, on 10/12/2007, -0/+1I assume 2.0.7 will be out in the next day or two if this is the only fix. WP-hackers has some discussion about this:
http://comox.textdrive.com/pipermail/wp-hackers/2007-January/010189.html
http://comox.textdrive.com/pipermail/wp-hackers/2007-January/010196.html- ComputerGuru, on 10/12/2007, -1/+3I don't know...
According to Matt (founder of WordPress), WordPress 2.0.6 is the last release before 2.1. Should the need for a 2.0.7 come up, it would be released after 2.1 goes gold.
Keep in mind that only a very small percentage of self-hosted WordPress users also use FeedBurner. Hosted WordPress has already been updated. - Viper007Bond, on 10/12/2007, -0/+3This isn't a huge issue, so based on past actions, I doubt 2.0.7 will be released ASAP just to fix this.
I'll just most likely be fixed in the next version to be released at the normal time. - HaxityHaxHaxed, on 10/12/2007, -0/+4"Keep in mind that only a very small percentage of self-hosted WordPress users also use FeedBurner."
Surely you're joking..every major blog uses feed burner.
I've gotten no messages from feed burner saying there are errors, and I upgraded last night..
- ComputerGuru, on 10/12/2007, -1/+3I don't know...
- slantyeyed, on 10/12/2007, -1/+3rule # 1: don't be so quick to upgrade
- darkfate, on 10/12/2007, -3/+6That's usually a bad rule though. There are security fixes and a bunch of other stuff. I think you would want to upgrade quick.
- awhiteflame, on 10/12/2007, -0/+1new code always opens the room for new bugs or new vulnerabilities.
Therefore, it's best to wait a little before upgrading. Better sticking with the bugs you know of, then immediately try new code where who knows what might happen.
- kasted, on 10/12/2007, -2/+1Good thing I didn't update all my sites.
- stealthyninja, on 10/12/2007, -1/+3Mark Jaquith has a fix: http://markjaquith.wordpress.com/2007/01/06/wordpress-206-feedburner-issue-and-fix/
- stealthyninja, on 10/12/2007, -0/+2I know, I know...I RTFA after I commented and only noticed ComputerGuru's comment above mine now. Sorry.
- MarkJaquith, on 10/12/2007, -0/+4Point of clarification: only certain server setups are affected by this. Namely, Apache with mod_php. People on any sort of CGI/FastCGI setup should be fine, and I haven't seen any problems on LiteSpeed.
And please don't leave your blogs on 2.0.5 because of this. The workaround 2 posts above this one fixes the issue on every server I've tested. 2.0.5 has several security bugs, so staying on it would be very foolish.- ComputerGuru, on 10/12/2007, -0/+1And IIS with PHP installed as an ISAPI.
Between IIS w/ ISAPI PHP & Apache w/ mod_php, that's pretty much a clear majority.
- ComputerGuru, on 10/12/2007, -0/+1And IIS with PHP installed as an ISAPI.
- bonzotunes, on 10/12/2007, -0/+0I have been battling this for at least a week now (http://wwwMusicProShow.com). Put up my new podcast episode early this morning and the feed shut down for almost 12 hours. All FeedBurner tech support could do was tell me it was my fault and they couldn't do anything. Weird thing though, after about 12 hours the feed mysteriously started working again. It's up now, but for how long?!
- ComputerGuru, on 10/12/2007, -0/+1TFA says that the error pops up when FeedBurner checks your feed and finds out it hasn't changed. When the source feed changes, the FeedBurner error clears up, only to return again once it re-checks and discovers it hasn't changed. Rinse and repeat. Thank god for the quick fix.
Browsing Digg on your phone just got easier with our enhancements to the 
© Digg Inc. 2008 —
Content posted by