There's apparently a conflict with user registrations in CiviCRM and Mollom. Both use a similar approach evidently CAPTCHA or reCAPTCHA. The current workaround is turning off Mollom, which seems counter productive. More info:
There's apparently a conflict with user registrations in CiviCRM and Mollom. Both use a similar approach evidently CAPTCHA or reCAPTCHA. The current workaround is turning off Mollom, which seems counter productive. More info:
Comments
Comment #1
dave reidThis likely has been fixed with the latest release. Please try the 6.x-1.11 code and re-open if it is still an issue.
Comment #3
steve hanson commentedI'd like to re-open this. As far as I can tell, this still does not work with Mollom 1.14
Comment #4
steve hanson commentedOops - didn't change the status - still broken with 6.x-1.14
Comment #5
sunIt seems like CiviCRM folks followed up with a workaround to make Mollom module work with CiviCRM.
In general, it sounds like CiviCRM is enhancing the user registration form for its "contribute process", but does not properly re-render the form upon a form validation error. Therefore, Mollom's CAPTCHA does not appear and only the error message does.
To fix this, CiviCRM needs to render the entire form, not just the fields it is interested in.
Reverting issue status.
Comment #6
laken commentedWe're still seeing this behavior on Mollom 6.x-1.15 and CiviCRM 3.3.5. Sun, where have you seen that the CiviCRM folks addressed this? There's no indication of that at http://forum.civicrm.org/index.php/topic,7835.0.html.
Comment #7
Poieo commentedI can confirm that Mollom and CiviCRM do not play nice together in D7 either. Trying to register as a new user with Mollom enabled and a Civi profile on the registration form throws the following:
Comment #8
cvining commentedI confirm Poieo's report. Fortunately, one doesn't need to remove Mollom. Just go to
http:///admin/config/content/mollom
and 'Unprotect' the User Registration Form. Not a fix, but a work around anyway.
-- Cronin
Comment #9
JamesSharpe commentedReopening against Drupal 7 version; I think the issue may actually lie with CiviCRM not being initialised correctly (i.e. not adding the search path to find the CRM directory) when called from xmlrpc.php.
Comment #10
torrance123 commentedSun in #5 was right about the cause of this issue. It is civicrm's fault.
See http://issues.civicrm.org/jira/browse/CRM-9711
Comment #11
sunMarking as duplicate of that CiviCRM JIRA issue then. This cannot be fixed from within the Mollom module either way.