Google Verification

Hi @mpearson65

I can think of two reasons why would this happen:
1) We’re using the /wp-login.php for handling the login and registration process, so the verification uses this page, too. If you have some kind of plugin that hides the /wp-login.php and for example, redirect to another page, that could cause such problems.
Set up a new, empty page what you won’t use for anything else, and set this new page at Global settings > OAuth redirect uri proxy page:
https://nextendweb.com/nextend-social-login-docs/global-settings/
After that you’ll need to add the new Authorised redirect URI to your Google app. See step 15:
https://nextendweb.com/nextend-social-login-docs/provider-google/

Then you could try the verification again.

2) I also find it possible that the problem happens because of some kind of plugin conflict. Try turning off all other plugins but Nextend Social Login, and see if you can verify like that.

Thanks – that worked (option 1)! Quick question:

– Can I unpublish that test page now or does it need to be live?

Thanks!

Hi @mpearson65

Do you mean the page that you created for the “OAuth redirect uri proxy page”? If you do, then actually that isn’t a test page, but a page that Nextend Social Login will handle the OAuth flow ( instead of the /wp-login.php page ) every time a user connects with social login.
So you should keep that page and it should still be selected for the “OAuth redirect uri proxy page” option at our Global Settings > General tab.

Note:
If you will enable the “Terms and Conditions” setting:
https://nextendweb.com/nextend-social-login-docs/global-settings-privacy/
in the future, then you should also use the “Page for register flow” setting on the General tab, as it is described there. Since the register flow is also handled on the default login page by default.

Best regards,
Laszlo.

Thanks – gotcha. One other issue, it passes through Google to login, but it doesn’t actually login the user to my site. I tried adding the login form shortcode to the URI page and that didn’t work.

I’m using Restrict Content Pro on my site Thanks!

Hi @mpearson65

Could you check please if the pages that you created for “OAuth redirect uri proxy page” and “Page for register flow” are publicly available? Since if Restrict Content Pro limits the access to those pages, then we won’t be able handle our codes there for logged out users, either.

If those pages are accessible, then please open a support ticket here:

• https://nextendweb.com/contact-us/nextend-social-login-support/?ref=https://www.ads-software.com/support/topic/google-verification-9/

with a link to your site and we will check this problem.

Best regards,
Laszlo.