CiviCRM Community Forums (archive)

help, i am going crazy. i have set up contribute pages that work fine when i am logged in as superuser, i have been able to go through & make test payments and actual payments. but when someone else - either an authenticated user or a new user, goes through the contribute process, confirms their information & hits the "processing" button - they get returned to the home page with the error message "The CAPTCHA field is required."

however there is nowhere on the contribute page to enter a CAPTCHA field. as far as i can work out it is not connected to the name&address profile that is used. we are using Mollom but from what i can understand of the settings there is nothing that i can turn off on the contribute pages, & i can't even find any settings for reCaptcha so i have no idea what that is about.

i am totally confused about whether the problem is in the settings for drupal or civicrm, whether it is in the contribute settings or in the user profile or something to do with authenticating users - because it is working fine for me as superuser. i just feel like i'm spending hours going round in circles & never getting any closer to the solution ...

 

This module is Mollom. Whether it is Mollom or CiviCRM that is causing the hiccup is the question.

It seems like it would be very helpful for Mollom and CiviCRM to play well together. Any chance of this?

I'd love to, but I don't think I have the skills. I'll propose it to the Mollom/Acquia folks.

We are having the same issue here.

If, whilst completing a civicrm contribution form, you create a new user account, then this step will fail if Mollom is protecting the user_register form. In our case, we get redirected to the front page with a warning "Word verification field is required."

Mollom is doing everything right by protecting the form using the usual form_alter hooks. The issue with with Civicrm.

Civi is injecting a username and password field into the contribution form. Then, to process it, civi is 'faking' a form submission by loading up the form, filling in the form state with the username and password, deleted any captcha field info that may exist, and then asking drupal to process the form as if it was submitted by the user directly. I guess this was to take advantage of Drupal validation and process functions, so as not to have to write this stuff again. However, since it is 'faked', and since drupal forms can change by way of the hook system, this process will fail if the user_registration form has modified requirements, as is the case with Mollom.

I think the solution is that Civi needs to take care of the form validation and processing itself (and this could simply mean using the Drupal functions directly, rather than using them via a fake form submission), and do away with the fake form submission.

The offending code is lines 501 - 554 of CRM/Core/BAO/CMSUser.php, the function createDrupalUser().

I've opened a bug on Jira and supplied patch. http://issues.civicrm.org/jira/browse/CRM-9711

This affects Civicrm version 4.1.2 under Drupal 6 as well.  the CreateDrupalUser function is no longer in CMSUser.php as in the patch, but related code is in CRM/Utils/System/Drupal6.php as createUser

I tried to modify the CreateUser function based on the Torrance's patch, but the result is that I am redirected to the homepage.  The  Mollum Word Verification error is gone however, but the transaction in civicrm event, membership, contribution etc (anything that use the profile with account creation required)  fails to complete leaving a pending transaction and no Drupal account created.

Current solution is to turn mollum off for the user registration form, but require that admin approve all account requests.

Hi Guys.  A general rule of thumb is "With CiviCRM, use reCaptcha, not Mollom".

The makers of contributed modules make no guarantees their modules will work with every other module out there.

Some of you may be married to Mollom and if that is the case and you have budget or skills to build a patch so that the modules Mollom and CiviCRM will work together, then you are welcome to submit that patch and maintain it.

If you are simply looking to prevent spam and want a zero-cost workaround, then look to the Captcha and ReCaptcha Drupal modules.