Ok, so you know how when you get in a rush, and you install a Drupal Module update assuming everything will be ok.
If we only lived in a perfect world right.
The other day I updated the latest Drupal 6.x Mollom module release 1.11 on three different sites.
It was running late so I really didn’t check my work and ensure that everything was as it should be…
With most module updates if something is not working it’s not that serious and neither was this update, unless…
…You love getting comment spam.
I had assummed (we all know what that means) that it would have picked up the setting from the previous module and applied them…
But, no it didn’t. So you can imagine all the comment spam I found in all three sites today.
I’m not bashing Mollom only myself for not checking out the settings to ensure everything was working properly.
The module continues to do a very effective job in blocking Drupal comment spam.
If you’re plagued with comment spam which every web site is then I highly recommend Mollom.
And, no I’m not being compensated to write this, sometimes you just find something that works as advertised!
Comments on this entry are closed.
Fixed in Mollom’s development snapshot already, but it’s ultimately an issue with Drupal core’s update system:
http://drupal.org/node/717902
Sorry, I take the blame here. I wrote that module update and also tested it, but obviously, not enough.
Hi Sun,
Nothing to be sorry about, and thanks for all the hard work you do.
The 1.12 version of Mollom was released. Give it a try, and once again, sorry for the inconvenience.
Hi Dries,
Thank you for what I consider one of the essential Drupal modules. It was no really and inconvenience, more like one of those “Why didn’t I check the settings!”
A quick check and a few clicks on my part would have caught it. And, it really illustrates just how intent comment spammers are at looking for any opening to get in.