WordPress 2.0.6 has been released and already there are fixes for the new version, showing how fast WordPress developers respond.
Mark Jaquith, one of the lead developers in this new version, has the information on fixing the issues feedburner feeds and NeoSmart explains it a bit further.
For those willing to jump on the beta testing wagon with WordPress, there is also the WordPress 2.1 beta version available for download.
Me? I always wait a bit for these little things to be fixed before updating. But this version fixes some security issues, so be sure to update soon.
Also, news is out that this is the last update before the release of WordPress 2.1.
Related Articles
- Give the Gift of Love to WordPress
- WordPress 2.0.5 Released
- Firefox 2 versus Internet Explorer versus WordPress
- Preview of Upcoming Changes in WordPress 2.0.5
- Are WordPress Themes and Plugins Ready for Internet Explorer 7?
- One Year Anniversary Review: In the Beginning WordPress Begot WordPressMU Begot WordPress.com
- Happy Birthday, WordPress.com
- WordPress 2.0
- WordPress 2.0 Breaks Ecto – Here’s the Fix
- Problems with WordPress 2.01 Feeds
- Release of WordPress 2.0.1
Site Search Tags: wordpress, wordpress news, wordpress tips, wordpress update, wordpress ugrade, wordpress release, wordpress 2, wordpress 2.0.6
Copyright Lorelle VanFossen, member of the 9Rules Network
Lorelle on WordPress 
6 Comments
Hmm… very euphemistic point of view:
WordPress 2.0.6 has been released and already there are fixes for the new version, showing how fast WordPress developers respond.
I can really understand that you cannot test all plugins with a new version of WordPress. But the FeedBurner-plugin is – so I think – one of the most used plugins, so it should be in a test environment for new releases.
There are a lot of other WordPress Plugins that meet the “most used” list long before Feedburner. 😉 And if this is the only one, then something is really going well, don’t you think?
Okay, that’s a point… but now I’ve got a idea: What plugins should be on the “most used” list for WordPress? How about such an article here?
Well, it affects more than FeedBurner, it’s just that FeedBurner handles it less gracefully than other consumers, so people are more likely to notice that issue. Other consumers handle it a bit more gracefully, so no symptom is exhibited. And it’s worth noting that it’s not an issue on all servers. Apache with mod_php is the only environment in which I’ve witnessed the bug. It definitely warrants a 2.0.7 release, but not right away. There were a few tickets that didn’t quite make it into 2.0.6, and my workaround works for those who are affected. I’ve provided a drop-in solution, a patch, and a description of the fix, so hopefully that’ll cover it for now.
But the one lesson here is that we need more testers for release candidates! The fact that this was discovered within hours of WP 2.0.6 being released (when the bug had been in 2 release candidates, available for download for several weeks) just tells me that our tester pool isn’t big enough.
Guys, that’s not true!
1) It’s not a FeedBurner plugin, or even a FeedBurner issue that gets stuck: it’s WordPress and how it sends 304 headers: corrupted!
2) My post and emails to WP-Hackers focused on FB, because that’s where it was most obvious. However, any and all web-based and local RSS/Atom readers experience the same problem, FB or no FB. It’s just whether they kill the feed or only flag it that differs. FB kills it – hence the seriousness of the issue.
3) It doesn’t just affect Apache w/ mod_php but also virtually all IIS hosts as well: basically anything that uses a isapi/nsapi/*sapi module to extended the webserver with PHP support.
Many thanks to Mark for the super quick fix, and he *is* right, we do need more people testing it – but that’s going around the fact. This isn’t a “minority only” issue (Apache w/ mod_php *and* IIS w/ PHP as ISAPI probably add up to over 50% of all hosts, excluding other *sapi implementations), and it’s in the WP-Core. It’s not a plugin incompatibility, rather it’s a simple, old-fashioned bug. But a fix exists, I guess that’s what matters.
Let’s just not kid ourselves and pretend it’s nothing, because we’re above that.
I think all the plugins I use needs to be on there to be tested 🙂
I’m joking but actually like Lorelle said after a new version is there I wait a while until people discovered things that break or not and been fixed before i use it. This time I took the plunge and it worked out well. I’m on 2.06.
2 Trackbacks/Pingbacks
[…] 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 […]
[…] WordPress 2.0.6 Released With Feedburner Fixes […]