WordPress 1.5.1 and Spam Karma 2.0

WordPress 1.5.1 is now officially released. If you are a WordPress user, you really ought to upgrade. This version fixes many of the bugs and shortcomings that were introduced with the botched release of WP 1.5. It takes seconds to upgrade from 1.5 (just overwrite everything in your blog directory except the wp-content directory). Shout out to all WordPress developers and contributors… Great job guys…

With this, I am glad to announce the official release of Spam Karma 2‘s first public beta.

In fact, it is pretty much final-grade quality and could probably do without the “beta” label… I’m just a big fan of the greek alphabet.

Many of the lingering issues with the last alpha have been fixed, a few missing features have been added (it now supports curl for those whose host doesn’t allow url_fopen). Check out the dedicated page for details.

Now go and spread the word! there are still far too many clunky SK1.x in the wild out there…

Also, feel free to contribute to the newly-opened official Wiki page for SK2: your help is much appreciated!

Update: Ahem, it would appear I spoke a bit fast. There is a rather nasty bug in this update that can bork your RSS feed. I do recommend updating nonetheless (and follow instructions in the link above to fix the bug).

Regarding that bug, let me add a little word. Honestly, I considered skipping this rant (and I waited quite a bit to ensure it really was what I was thinking about), but I am just to aggravated to keep my mouth shut. Consider this my final word on that branch of topic, though:

Obviously, and as usual, this blatant bug could probably have been avoided with a bit of real-world deployment strategy and testing before release, but I won’t even bother restating my opinion on the matter… What bears mentioning, though, is the fact that I did report it personally, more than 2 weeks before the release date.

The bug is at least somewhat directly connected to this change. I noticed it, shortly after the code was changed in SVN, emailed Matt about it, didn’t really get much of a response (apart from an invitation to basically go and fix it for him) and considered it none of my business any more (I had way enough things to take care of at the time).

It didn’t even cross my mind, though, that this code, after being clearly reported to Matt as broken, could make it seamlessly and without apparent revision into what was supposed to be a bug-fixing release.

Quite frankly, I feel rather insulted, if anything…

16 comments

  1. Dave,

    Thanks for the comment the other day. You’re absolutely right – I know that I ramble on for faaaaar too long. *hangs head in shame* Sadly, being concise has never been my strong point, but I’m working on it, I swear!

    I’m glad you found the translation useful – I enjoyed your commentary on the “scandal” (is that the correct word?) and Japanese reaction to it as well. I think you did an excellent job summarising both the relevant history and identifying some valid criticisms of the prevailing modern Japanese mindset. Good stuff, and I wish I could have written something like it instead of just providing a translation.

    On an unrelated note, I just wanted to say that I enjoy reading your blog and as I mentioned in my website “about” page, it has influenced me in the past as I tried to figure out just what the heck I’m doing in this country. Keep up the good work 😉

    (oh and I like your mixes too!)

  2. Dave, what kind of inclusion into the Plugin Manager are we going to see when 2.0 goes final? Will 1.x just get a one-click upgrade to 2.0, or will it be uninstall and reinstall, or will 2.0 take some manual configuration?

  3. Heliologue: most likely, WPPM 2.0 will just be an auto-update as usual.
    Actually: there might be an in-between version maintained by a kind contributor who seem willing to take care of development for the time being (something I really can’t do)… Stay tuned (it’ll appear in the ‘update’ section anyway)…

  4. Matt, I’m not too sure what you are talking about. All I know is that the bug I reported at the time was specifically linked to diff #2584. Reverting that code fixed it. The version I and many people downloaded had the *new* code. Reverting it, fixed it.

  5. What must I do to insure the correct operation of Spam Karma using mod_security on our server.

    At present, we can’t determine what is causing it, but we are unable to update the blacklist due to the #$%#$ rule.

    🙁

    Any help would be appreciated.

    Thanks

  6. Hi Dr. Dave, I used your spam karma 2 plugin up until about a month ago, at which point it began eating all of my comments. People who got through before I updated to v2 were no longer able to post comments w/o them getting marked as spam. Is this a common probelm w/ v2, or do you know of something I might be able to do to fix it? Thanks

    -Gnimsh

Comments are closed.