WordPress v1.5.1 Rant

Ok, this is crazy. I can’t believe this. This is bloody crazy. I have spent the last 48 hours trying to fix bugs with the final release of WordPress v1.5.1. I have never had problems with a WordPress final release, but this is ridiculous. Honestly, did I miss the part that said “public beta” on this release? I’ve never had this amount of problems with a final WordPress release. WordPress v1.5.0 was and is still functioning perfectly. Currently at the top of my list is the trackback and pingback bug (resolved by revision 2612 of functions.php, revision 2612 of functions-post.php, and revision 2606 of xmlrpc.php). Next is the feeds bug (resolved by revision 2600 of wp-blog-header.php). And, finally, the ping-o-matic bug (resolved on ping-o-matic’s end). My personal history with the trackback and pingback bug can be viewed here.

Update: WordPress v1.5.1.1 has been released. This is a recommended update for all users.

I don’t know what to make of all this. All I can say is that I am more frustrated than I have ever been. Two weeks ago, DreamHost disabled allow_url_fopen(), which crippled WordPress’ trackbacks and pingbacks. So, after being fed up with running PHP as CGI as well, I moved to a BlueHost, a host which had allow_url_fopen() enabled and ran PHP as a fully-featured Apache module. My trackbacks and pingbacks were restored to flawless functionality. Well, thanks to WordPress v1.5.1, there is a new fix for trackbacks and pingbacks that uses C-U-R-L rather than fopen(). And, guess what … my trackbacks and pingbacks are crippled again! Let me remind you all that my server move to fix this problem was only six days ago. It hasn’t even been a full week yet. ::sigh:: This site is about presenting functionality to its very large reader-base. We will have a fully-functional v1.5.1 implementation or we will switch back to v1.5.0 before tomorrow. If we must switch back to v1.5.0, then I must apologize, as all recent comments will be lost.

I should also clarify that I wish nothing bad against the WordPress developers. I just wish that this release would have gone through more testing.

11 responses

  1. Yikes!

    I think I’ll wait until you give it your okay.

  2. At least the ping-o-matic issue has been resolved. It was a problem on ping-o-matic’s end.

  3. Really?

    So should we reverse the extended ping change we made to function.php?

  4. Yes, you may return to using your normal (un-edited) functions.php file.

  5. If I had any inclinations before to upgrade, I don’t have any now 🙂
    I am just looking to update with the security patch.

    Have a good weekend.

  6. Fortunately, I looks like most of the big bugs have been fixed. You should be fine updating to the recent nightly build: http://trac.wordpress.org/browser/

  7. James,

    apologies if this is a dumb question but is there somewhere I can download a bug-free version of WP 1.5.1 – I have looked through http://trac.wordpress.org/browser/ and can only see single file downloads for each file in WP 1.5.1

  8. […] en sich zwei Postings zu den insgesamt drei Fehlern in WordPress 1.5.1. Im zweiten Posting WordPress v1.5.1 Rant finden sich die Hinweise zur Lösung aller drei P […]

  9. If you want have the same “[I hope] bug-free WordPress” as I do, you’ll need the v1.5.1 download that is available at WordPress.org. You’ll also need:

    This version of xmlrpc.php: http://trac.wordpress.org/file/trunk/xmlrpc.php?rev=2606

    This version of functions.php: http://trac.wordpress.org/file/trunk/wp-includes/functions.php?rev=2606

    And this version of wp-blog-header.php: http://trac.wordpress.org/file/trunk/wp-blog-header.php?rev=2600

  10. […] WordPress v1.5.1 Fixes Those of you who stop by often, know that I ran into some problems after upgrading to WordPress v1.5.1. Fortunately, I beli […]

  11. […] us all to get along almost convinced me to go ahead and update. Then I dropped in to see what MacManX thinks about it… and now I believe I’ll wait. […]