"triggered the spam filter" when using Login/Search block

I upgraded yesterday also and I had the same issue this morning when attempting to log in from a comment page . In addition, it appears that Mollom allowed about 20 comments to be posted that were all spam. I noticed I had comments before I logged on that all seemed like "SPAM". When I went to the comments page and tried to log in I received the same message you mentioned above.

When I went back to the home page I was able to log in and then went to admin / mollom and was denied. It said I did not have access to mollom. So I went to the user permissions and looked at the mollom settings. The "admin mollom" for administrators was "unchecked". I checked it and went to mollom to check if the settings for "comments" had changed. Everything was still checked with "Text analysis and CAPTCHA Backup"

I would be interested to hear what is going on with this update.

I am getting something similar from the search block. Only seems to occur if I am in a node, not from the home page.
Any search entered while viewing a content node seems to be affected.
Message is the same. "Your submission has triggered the spam filter and will not be accepted."
I don't know if this is related but it seemed like it might be.

Investigating, but it would be helpful if someone could help debug this problem. If it is reproducible, you could alter _mollom_debug() to do some logging to your Apache log files or to watchdog() if you want. Hopefully that will provide more insight in why Mollom is triggered.

Mollom incorrectly detects the "submittability" of the form. We only check if $form['#post'] is not empty, without checking the form_id, as does drupal_process_form().

Here is a patch.

And a less stupid one.

I've been testing this one and it seems to address the problem. I'll commit this to the Drupal 6 development branch after some more testing. Thanks Damien.

I was just about to report I was experiencing this on my blog recently as well. With Damien's patch it seems to be working properly. I'll try and actually get a SimpleTest written for this so we don't regress this bug.

Damien,

How do I apply this patch? I'm not really a coder, so I have not idea where to apply this patch. If you could explain what I need to do, it would be greatly appreciated.

Thanks,

I committed to DRUPAL-6 HEAD but we still need tests.

Writing regression test and will post shortly. Assigning myself.

Here's a regression test. It was a PITA since DWTC->drupalPost() doesn't allow us to submit fields from multiple forms at once. This might be a little cleaner with the 'additional_post' option in #335035: drupalPost() incorrectly submits input for disabled elements but we'll still need to wait for it to be backported.

I confirm that the test has 2 fails as expected without the patch in #5 and passes successfully with the current fixed/HEAD code.

Subscribing.

Upgraded to the new version, spam filter is still triggered when searching content from node pages. Fine from the homepage and from views pages. I'm going to disable molllum for now.

Is there any way to tell Mollom to let the spam filter alone? Seems like that should be an option.

@robotoverload: Can you confirm you are using the current 6.x-1.9 version of the module? It's been working fine for the rest of us.

This has been fixed in the 6.x-1.9 version so marking this 'fixed' for now. Feel free to re-open if it is not fixed.

Yes, it's v1.9 that I'm having problems with. I will try to reproduce the error on a local copy of the site and get a better idea of what's happening.

Strange that everyone else is fixo.