Enable Auto Login After Registration fails if reCaptcha i activated

[danielfletcher]

When I have the ‘Enable Auto Login After Registration’ option turned on, and the reCaptcha is active on the login form, when a user submits the registration form a new user is created in the back end but the following error message is displayed on the frontend: Captcha verification failed. Go back and try again.

It looks like the emember_recaptcha_verify() returns false in the emember_init_frontend() function (eMember_init.php file).

Can you advise, please?

Many thanks

[wzp]

I’m not surprised, that it happened. The reCaptcha verification checks for the presence of a valid “g-recaptcha-response” which will always be an invalid value; because the member was never asked to submit a reCaptcha form. This is something the developer will have to take care of. Would you rather have the new member perform the reCaptcha test, or just bypass it?

[admin]

You can’t enable captcha for the login form and at the same time enable “auto-login”. The auto login basically auto submits the information (the same way a bot does). The captcha is there to prevent that auto-submission. Pick one of those options.

[danielfletcher]

Thanks for your quick reply.
Is there a reason a user is redirected to the login form after registering instead of logging the user in using the WP login functions? I understand the login captcha fails because the login form is being submitted automatically but I’m not sure why the user is being redirected to the login page in the first place instead of just automatically logging them in after registration.

Many thanks

[admin]

Our plugin has a separate login process (we don’t use WP’s login). Our plugin doesn’t need the WP user entries. We prefer not to modify or add data to a core WordPress user’s database table. So WP eMember uses it’s own database table to store membership details. Most of our customers who create a membership site using our plugin prefer this clean approach where your core WordPress user database table doesn’t get cluttered.

We don’t have a hotwiring login system. We haven’t done that intentionally because we don’t want to have to worry about the security side of things of that hotwiring process. You may need to look at an alternative plugin which will be more suitable for the project that you are currently working on (different membership plugin’s work slightly differently).

[Author]

Posts