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.Tags: wordpress mollom bugfix spam