Mollom

Over the past couple of days, it became apparent that WP Mollom suffers an issue where it “eats” your comment when a CAPTCHA is shown. The result is that only half of your comment is saved. Not good of course.  Apart from that, there was also a problem with character encoding.

Of course, this issue needs solving. I could recreate the problem on a testsetup and found the culprit. This issue rears its’ ugly head when a commenter uses double quotes in his/her comment. Because of the way WordPress implements commenting, I have to embed the commentdata in the CAPTCHA form as a cluster of hidden fields. The handling of the encoding was a bit wonky here which causes data to get corrupted.

I fixed the issue and commited the code in the development version of the plugin (trunk). I’m not commiting it to a stable version yet because the adjusted code needs testing against foreign non-western character sets like simplified chinese and such. If your blog is set to use UTF-8 encoding (which it should!), you shouldn’t notice big problems with this update.

If you’re really anxious to get your hands wet, you can download the development version here.

I just released WP Mollom 0.7.1. Here’s the changelog:

• fixed: all plugin panels are now shown in the new WP 2.7 administration interface menu
• fixed: non-western character sets are now handled properly in the captcha form
• fixed: handles threaded comments properly
• fixed: multiple records in the manage module not correctly processed
• improved: extra – non standard – fields added to the comment form don’t get dropped
• improved: revamped the administration panel
• improved: various smaller code improvements
• added: the plugin is now compatible with the new plugin uninstall features in WordPress 2.7
• added: the ‘quality’ of ‘spaminess’ of a comment is now logged and shown as an extra indicator

Wishing all the best in 2009!

I just tagged version 0.6.1 of WP Mollom in the WordPress Extend repository. Which means in a few moments, you’ll be able to download the latest installment of my plugin.

So, what has changed? Well, this is a bugfix release which means no new features. Here’s the changelog:

• Fixed: division by 0 error on line 317
• Fixed: if ‘unsure’ but captcha was filled in correctly, HTML attributes in comment content would sometimes be eaten by kses
• Improved: the mollom function got an overhaul to reflect the september 15 version of the Mollom API documentation
• Changed: mollom statistics are now hooked in edit-comments.php instead of plugins.php
• Added: _mollom_retrieve_server_list() function now handles all getServerList calls

Although almost all basic functions are up and running now, there’s still a long road ahead. Today, I’m happy with what I’ve accomplished technically so far, but such things as usability, performance, flexibility,… still need more work. For instance, there’s still no WordPress MU version, i8n support is still missing, the backend needs more simplifying and much more.

But then again, if spam annoys you as much as the mosquitos in my room did me last night, then this is the plugin for you. Download the package, drop wp-mollom.php in your plugins folder, register with mollom.com to get your keys, just configure them in the plugin and you’re all packed with some serious spam stoppage power.

Happy blogging!

I just released a minor update of WP Mollom with some bugfixes. This is the changelog:

• Fixed: minor issues with the Captcha not being rendered correctly
• Added: mollom_manage_wp_queue() function which adds Mollom support to the default comment administration panel
• Improved: updating from a previous version is now more robust

More info and download on WordPress Extend

Oké mensen. Tijd voor het moment van de waarheid. De laatste maand heb ik tussendoor, voornamelijk op de trein, geprogrammeerd aan een plugin voor WordPress. Niet zomaar een plugin, maar eentje die het de diensten van Mollom, de startup van Dries Buytaert en Benjamin Schrauwen, ook voor WordPress gebruikers toegankelijk maakt.

Ik huldig eigenlijk het principe eat your own dogfood. En om eens te kijken hoe sterk mijn plugin reeds staat, zet ik die bij wijze van allereerste publieke test in op mijn eigenste blogje. Akismet en Spam Karma heb ik voor de gelegenheid gewoon uitgeschakeld. Vanaf nu worden jullie comments door de spamfilters van Mollom gehaald.

Hoe werkt het? Bij een normale comment zal je niets merken van het werk dat Mollom achter de scherm uitvoert. Stel dat je een spambot bent, dan wordt je bijdrage gewoon geweigerd nog voor er wordpress een query op de database uitvoert. Moest er nu twijfel bestaan over de legitimiteit, dan wordt je comment in moderatie gehouden en krijg je een eenvoudig testje voorgeschoteld om te bevestigen dat je wel degelijk een persoon bent met de allerbeste bedoelingen.

Bij wijze van proef mogen jullie je even in de commentaren van deze post laten gaan. Het gaat om een proef om de basisfunctionaliteit van de plugin te verbeteren. Verder gaat het er mij nu om een aantal secundaire doeleinden op korte termijn te implementeren. Bij problemen of opmerkingen kan je mij altijd op mijn mailadres, matthias apestaartje netsensei puntje nl, contacteren.

‘Do your worst‘ zou ik zeggen!

O ja, ik ben Benjamin en Dries alvast heel erg dankbaar voor de steun en de feedback van de afgelopen weken!

English readers:

Yes, I’ve been working on a plugin that brings Mollom to WordPress. I’ve enabled my plugin on this blog to protect it from spam through Mollom. This is a preliminary test for the basic, barebones functionality of the plugin: filtering out spam. Unless you’re a spambot, you should have no trouble posting comments. Keep an eye out for the CAPTCHA test, though. If you run into problems or you have suggestions, don’t hestitate to contact me: matthias apetail netsensei dot nl. A big thank you to Dries and Benjamin for their support in these past weeks.