i will still be providing bug fixes, however. so please let me know if you encounter any issues that need fixing! i just won’t be adding any features anytime soon.

edit: it’s also worth mentioning that I’m no longer an iPhone user, so that makes things a little less interesting from my point of view. maybe i’ll think about having android support of some type (don’t know how, or if this is even desirable), or maybe I’ll get an iPad and get interested again. my frustration with the iPhone notification system had finally come to the point where I couldn’t stand being on the platform anymore, honestly.

as per usual, you can grab it from the wordpress plugin page or autoupdate through your wp dashboard. have fun out there.

• fixes issues with spam comment notifications slipping by, even when akismet catches them
• fixes issues with WordPress MU not being able to save options (i think)

if you test it, you’ve gotta let me know. thems the rules!

get the zip out of WordPress SVN. You’ll have to do a manual install since this is the beta.

Updates forthcoming:

• Not working in WP MU. Have to figure that one out. Something to do with how I’m saving options.
• People still getting spam messages? This is a weird one, because it should’ve been fixed. Will have to dig into Akismet, since apparently it’s too damn full of itself to use the standard data structures. Well excu-u-u-u-se me.

Also, new projects. Something else to do with Prowl. I’m only going to write the frontend. That is so long as the guy who wrote the backend doesn’t think I died or something.

Final thought, linkfarms? Things that aggregate posts from other sites, and then group them into inexplicable bunches on god awful websites? It’s a thing I don’t understand. Was Googling WP-Prowl to see if any nice people were saying nice things about it (some were!) but I get a bunch of goofy sites that are reposting posts that I’ve made to the WordPress forums. Useful? I fail to see how.

• Added new notification type: New Post Pending Review. (thanks djr!)
• Added delay in new posts/pages, so notifications aren’t spammed for multiple edits in a short period (not a final implementation).
• Terribly serious rewrite of Post/Page notification code.
• Makes sure plugin activation fires on manual upgrade.
• Made steps towards being ready for internationalization. Not there yet… things left to learn.

Yes it’s almost like I tried with this one. Internationalization is on it’s way, but there’s a few nuances in the WordPress localization process that I don’t quite understand yet. Anyhow, run on over to the WordPress Plugin Page and get yourself a copy, or use your auto-upgrade from your admin dashboard to install. It might be a few minutes/hours before it goes live. Let me know if you find anything wrong!

Beta 3 just implements the missing “delay” code for Page edits. This isn’t a complete implementation, however, since it’s only able to calculate from Initial Post Date to subsequent edit dates. You can see the problem pretty much right away, this works great for the initial post, but if you come back and edit again after the initial delay runs out, the same problem will be right back, and you’ll get notifications each time someone presses “Publish”. Not exactly ideal, but-t-t-t…

Well, it was the fastest to implement. Looking through all post revisions is really costly, at least through the WP API, and I’m looking into a proper way to do this. No problem, I’ll work it out, but I wanted to get something in for the 0.8.0 release. Better code will come 0.8.1 or 0.8.2, but with my new job starting, it might be a while until I get to it. I figured everyone would like a halfway implementation better than no implementation at all!

Anyhow: download, test, report bugs. I’ll love you for it!

• Added new notification type: New Post Pending Review. (thanks djr!)
• Terribly serious rewrite of Post/Page notification code.
• Made steps towards being ready for internationalization. Not there yet though.

I’m also working on putting in a “delay” for page edits, that way you don’t get notification-spammed when someone edits a page many times in succession. It isn’t working yet, even though there’s an option for it. I’m not sure why. I haven’t tried that hard on it yet to be honest.

WordPress Internationalization (i18n)

I was getting ready to say “WP-Prowl is ready to be translated!” but, well, I’m not positive that it is. The WP translation docs don’t really explain too well (that I can find anyhow) about how internationalization works, as far as changes go. If I understand correctly, it’s based on line numbers, meaning my translators would have to update their translations for every version? Is that right? Seems like bullocks if so. I’ll need to research better on how this all works before I go wasting anyone’s time.

reCAPTCHA’s implementation is strange, in my opinion. It still stores the comment in the database, which I assume is so that Akismet and others can still benefit from it being posted. Or perhaps (and more sensibly), so that it can deny duplicate comments should a subsequent comment pass reCAPTCHA? I don’t know the reasoning, but luckily, reCAPTCHA sets a global variable when a comment fails the CAPTCHA. Observe this simple fix:

global $recaptcha_saved_error;
if($recaptcha_saved_error) return;

Sorry if this fix is boneheaded in any way, but in all my testing it seems to work fine. This went into my comment handling function, and simply returns if reCAPTCHA set an error. I checked out the recaptchalib, and it seems to only set this global error variable whenever the comments fails to pass, so I’m going to call it good. Hopefully this helps out anyone having an issue. Let me know if not please!