Closed (outdated)
Project:
BOTCHA Spam Prevention
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
13 Apr 2012 at 18:04 UTC
Updated:
28 Apr 2018 at 15:35 UTC
Jump to comment: Most recent
Comments
Comment #1
iva2k commentedThe issue is with default configuration of both modules to protect user/register page (user_register_form).
- Tried with Mollom 7.x-1.1, 7.x-2.0 - both fail
- Removing BOTCHA solves Mollom problem.
- Alternatively, removing Mollom captcha from that form also solves the problem.
Comment #2
iva2k commentedLooking for root cause of the problem, I found that this single line in hook_form_alter() breaks mollom captcha:
Filed issue in Mollom's queue #1532794: Mollom captcha fails on forms with $form_state['no_cache']=TRUE
Comment #3
iva2k commented"$form_state['no_cache'] = TRUE" was introduced to fix #1510082: BOTCHA D7: form rebuild is not happening properly on invalid submission.
Comment #4
iva2k commentedUse this verified rework: If you enable protection of user/register form in BOTCHA, disable Mollom protection on it. If you want captcha on it as well, use Captcha module.
BOTCHA has much more sophisticated protection than Mollom honeypot, but it depends on disabling form caching (Mollom is using form caching in some non-standard way), and Captcha module works as it has no dependency on form caching.
Comment #5
donquixote commentedIt would be a nice idea to first filter the form submission through BOTCHA, and then pass it on to Mollom for additional protection.
#4 means this cannot happen.
#1532794-10: Mollom captcha fails on forms with $form_state['no_cache']=TRUE (sun) suggests that the disabling of the form cache is not necessary.
Could we give this a try?
Comment #6
oadaeh commentedSince Mollom has reached it's end of life as of April 2, 2018, I'm closing this as outdated.