Hi - Not sure why I'm running into this. Development build in MAMP. Everything seems to work fine. However when put into production and I log out and then log back in I get the error message "There was a problem with your form submission. Please refresh the page and try again." I'm guessing this is the honeypot returned message but not sure why I would get it on the user login.

I am using "Enable honeypot on all forms" - I guess that makes me wonder if user login is included but I'm only entering username and pw... no addt'l fields.

thoughts?

CommentFileSizeAuthor
#3 disable_login_protection-1260886-3.diff484 bytesgeerlingguy

Comments

john_b’s picture

john_b commented

Presumably, unless I misunderstood, becuase when you hit login button you are not actually logged in. So you are getting the same behaviour described here http://drupal.org/node/1232622 .

It is also not clear from your post whether you have waited the full five seconds before attempting to log in. If you have not waited five seconds, and you are not logged in when you hit the login button, then (according to Jeff's description of the way the module works ) you would expect it to shut you out, providing the module is working correctly. But maybe I misunderstood your post.

geerlingguy’s picture

geerlingguy commented
Title: There was a problem with your form submission. Please refresh the page and try again. » Disable timestamp protection on user login forms

Yeah, I might disable the time protection on the login form. I've also opened #1261984: Allow admin to choose which protection method(s) to choose, which is related.

geerlingguy’s picture

geerlingguy commented
Assigned: Unassigned » geerlingguy
Status: Active » Needs review
StatusFileSize
new disable_login_protection-1260886-3.diff484 bytes

I'm thinking of just having the login form unprotected in general - I can't think of a reason it particularly needs protection, as Drupal already offers flood control for that form, and login forms aren't generally spam targets anyways.

Please try the attached patch, and see if that fixes the problem. Patch is for 7.x-1.x, and is a simple diff of the module file. You can manually apply the changes to 6.x-1.x as well, and it should work. Let me know if this fixes the problem for you!

john_b’s picture

john_b commented

done, checked login works, no problems

geerlingguy’s picture

geerlingguy commented
Status: Needs review » Fixed

Fixed:

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.