Sorry if this should be better reported on the CiviCRM site - I may do that as well.

I've tested Honeypot on a Drupal 6 site with CiviCRM. When using a CiviCRM contribution form with allowing the integrated creation of a Drupal user at the same time as submitting the contact info, I get an error "There was a problem with your form submission. Please wait 5 seconds and try again."

I haven't looked at it too closely. I had assumed that the CiviCRM form submission wouldn't touch the honeypot field. Maybe because CiviCRM doesn't know what fields need to be created in the Drupal registration (it has a similar issue with required profile fields) that the submission has missing data required for honeypot and so it throws an error even though technically the field is blank.

Comments

geerlingguy’s picture

Version: 6.x-1.5 » 6.x-1.x-dev

That's an interesting problem... I haven't run into something like this with anything else, though I haven't ever used CiviCRM either. I'm wondering if they have some sort of logic that autofills form fields when a form is submitted, or combines two forms together.

At some point, I will make it so you can disable the time restriction independently of the honeypot check in the interface.

Until that time, you could set honeypot to not protect the registration form, and in a custom module, use a hook_form_alter() to alter the user registration form and add in honeypot protection with just the 'honeypot' protection (and not the timestamp protection).

geerlingguy’s picture

Status: Active » Closed (works as designed)

Actually, after re-reading your original post, it looks like you hit the time limit, and the honeypot field wasn't actually filled in. You can either set the time limit to something lower than 5 seconds, or disable Honeypot for that form.

You must've submitted the form more quickly than 5 seconds — maybe you're just too fast a typist ;)

kriskhaira’s picture

Hi, I'm having this problem with the following setup on Drupal 7:

  • Honeypot 7.x-1.14
  • CiviCRM 4.0
  • Drupal 7.22

Should I open a new issue or change the version number designated to this issue?

Thanks.