- This topic has 2 replies, 2 voices, and was last updated 10 years, 2 months ago by .
Viewing 3 posts - 1 through 3 (of 3 total)
Viewing 3 posts - 1 through 3 (of 3 total)
- You must be logged in to reply to this topic.
Support site for Tips and Tricks HQ premium products
by
Tips and Tricks HQ Support Portal › Forums › WP eMember › WP eMember captcha add-on breaks auto login after registration
Tagged: captcha, wp membership
Hi I’ve been at this for a couple of hours now with no satisfactory outcome. I’m using WordPress V3.8.4; emember V8.8.8; WP eMember Captcha V1.0.8.
If a registered member logs in and uses the really simple captcha code, there’s no problem. But if a new person tries to register they get the following error:
Security check: failed captcha. Please try again!
Warning: Cannot modify header information - headers already sent by (output started at .....)
However although the user sees the error screen above, their data are written to the member records database and if I ignore the error and just go to the member login page and use the fresh (supposedly failed) data to login as an existing member it works ok.
For a new member to join the captcha add-on must be turned off on BOTH the registration form AND the member login form. (if either is on it fails).
ALTERNATIVELY, I can leave the captcha on, but turn off “enable auto login after registration” (in Member login related settings) and it will work. So it seems to be some sort of conflict between the captcha and the auto login after registration.
There seemed to be a very similar question earlier today, but when I click on it I get a list of questions for today but I can’t see it anywhere.
Can you help?
Thanks
JOhn
Auto login after registration is an “automated action”. The whole purpose of the captcha addon is to block any automated action on the registration or login form. So if you want to use auto login after registration then you can’t have the captcha option on the login form.
Oh. Thanks for clarifying that. I was adding the captcha to reduce the probability of automated (non-human/spam)registrations. But now I see why it won’t work. At least we know the plugin/add-on are working correctly – even if the user isn’t