Alex King › Comments

Thanks very much for figuring it out, sharing, AND for shaming. Not cool that he didn't even bother to look. - Ken Kennedy

I'm thinking I'll comment out the auto-upgrade URL in my copy of the plugin and fork it for myself. I'm so unimpressed by the non-handling of this REALLY SERIOUS error that I'll just take my chances without future updates. - Dave Slusher

So many wrong assumptions - so little time to correct them all. Gotta love the internets. ;) - Alex King

The "it's a beta" defense bugs me. I was just updating plugins via wp-admin and it was an option. If it's not ready to ship, it shouldn't be available via that. Am I going to have to look for a "b" in all the version numbers before I hit the upgrade link or else be told it is my fault? - Dave Slusher

I don't like it either; plugin author name noted (nothing personal, Alex...just protecting the blog). And one would hope that the blog-killing error has already been corrected (or at least commented out) in source control, and pushed out! - Ken Kennedy

I changed my mind and just removed the plugin. I don't like it enough to have it bork my blog. I don't like how lightly Alex seems to take the immediate and total killing of some people's blogs. It's easy to reproduce: start at the old version, delete all the rows from the options table, upgrade. Dead blog, and you can't even get to the wp-admin to deactivate it. Alex defends the wp_die command. Wouldn't it be better to deactivate the plugin on this error rather than stop serving all pages? - Dave Slusher

I agree that using wp_die is...um...kinda overkill. Like sledgehammer -> fly overkill. - Ken Kennedy