Comments on: Fixing Feed Problems with WordPress 2.0.6 and PHP 5.2

By: Kelson

Kelson — Mon, 14 May 2007 15:59:10 +0000

Marcus, this bug was breaking feeds handled through FeedBurner too, because it interfered with the data that FeedBurner uses. In any case, it was fixed four months ago, so you’re better off just upgrading to a newer version of WordPress.

By: Marcus

Marcus — Mon, 14 May 2007 14:46:27 +0000

May be it’s better to use a FeedBurner?

By: Mark Siedle

Mark Siedle — Thu, 25 Jan 2007 01:02:08 +0000

Thanks for this info …I was having feed problems with WP2.0.6, so I upgraded to WP2.1 and all problems fixed. Upgrade went smoothly too, no problems.

Cheers,
Mark

By: WordPress 2.0.7 security & feed fix | K-Squared Ramblings

WordPress 2.0.7 security & feed fix | K-Squared Ramblings — Tue, 16 Jan 2007 00:46:42 +0000

[...] Just upgraded to WordPress 2.0.7. It fixes a security issue with certain versions of PHP, and it also includes the fix for the feed problem in 2.0.6 and a couple other minor fixes. [...]

By: Josh

Josh — Fri, 12 Jan 2007 15:47:28 +0000

Thanks for reporting this. I discovered the problem with Google’s Webmaster tools, where it said my 404 was returning a status of 200 OK. But I have gotten blank feed reports, and also had trouble with FeedBurner. The fix from Mark Jacquith fixed all of this.

By: Recommended Update: WordPress 2.0.6 at The Blog Herald

Recommended Update: WordPress 2.0.6 at The Blog Herald — Sun, 07 Jan 2007 20:34:21 +0000

[...] But as of writing, the 2.0.6 update is not without problems. Mark Jaquith was quick to point out the possible problem with Feedburner feeds. Apparently, fixes made to the 2.0.5 code has triggered another problem that may affect a different set of users. He offers a solution, and cites related entries from The NeoSmart Files and K-Squared Ramblings, both with more details on the problem and more importantly, how to fix them, now. With the almost–instant response to this last–minute problem, Lorelle was quick to point out how well the community of WordPress developers are addressing reported problems and vulnerabilities. [...]

By: Kelson

Kelson — Sun, 07 Jan 2007 03:31:37 +0000

You’re welcome!

By: Johanna

Johanna — Sat, 06 Jan 2007 19:34:30 +0000

Thanks so much for pointing out why I should upgrade! I agree, more specific information would have been nice. I’ve done the upgrade now, and it went smoothly enough — I used your second update approach, just commenting out the if/then around the problem lines. I very much appreciate your support in this — made me feel much more comfortable.

By: Kelson

Kelson — Sat, 06 Jan 2007 06:07:57 +0000

Brion — Thanks, I’ll paste that into the ticket!

Johanna — Unfortunately, it seems that the security hole could let someone hack into your site, so I wouldn’t recommend waiting at this point. (It would have been nice if they’d made that clear in the original announcement!)

On the plus side, it’s a really simple change to make. The hard part was finding where to make it. And I suspect it’s dependent on the version of PHP, or possibly the combination of the PHP version and Apache version, so it might not cause problems with your setup.

Also, I read somewhere in the support forums that upgrading from 2.0.5 to 2.0.6 doesn’t change the database, so you can move back to 2.0.5 just by restoring the files.

I’ll add the exact changes I made to the post (since comments don’t allow quite the same level of formatting). If you like, I can email you my copy of the file. That way if you upgrade and it breaks the feeds, you can just upload the altered file.

By: Johanna

Johanna — Sat, 06 Jan 2007 04:29:19 +0000

If someone isn’t as comfortable in PHP as you are, would you recommend that they wait to upgrade based on this? I get a significant amount of traffic through feeds and would hate to have problems with them. I’m hoping that 2.1 isn’t too far off.

Thanks for sharing your experiences.