• Resolved central4all

    (@central4allgmailcom)


    When i try to login with google i get this error:

    Error: The password field is empty.

    Please advice

    The page I need help with: [log in to see the link]

Viewing 10 replies - 1 through 10 (of 10 total)
  • Plugin Support Laszlo

    (@laszloszalvak)

    Hi @central4allgmailcom

    I checked the login with Google, and I can also see the problem.

    I think it is caused by a third party, as normally we will try to handle the OAuth flow and the Register flow over the WordPress default login page ( /wp-login.php ), but in your case we are getting redirected to a custom login page and that is what displays this error message.

    So what you could try, is forcing Nextend Social Login to handle all the process over other public pages, that you don’t use for anything else and excluded from all kind of caching.
    For this you need to use our “OAuth redirect uri proxy page” and “Page for register flow” settings. Both of these can be found in our Global settings > General tab:

    and you should configure them in the following way:

    • For the Page for register flow: You should create a new page and add the shortcode into it: [nextend_social_login_register_flow]
      then select that page for this setting. Extra information before the registration with social login – like Terms and Conditions, Username, Password, Email – would be asked on this page. ( Make sure you don’t use this page for anything else! )
    • For the OAuth redirect uri proxy page: You should create another new and completely empty page ( that you won’t use for anything else either ) and select it as OAuth redirect uri proxy page. Once it is done, the redirect URL of each configured provider will change, as the OAuth flow will be handled over this new page instead of the /wp-login.php page. So, you will need to add the new redirect URLs into each of your configured Apps again. ( Nextend Social Login will also warn you about this with a message, where you can see all the steps, but actually, you can find the redirect URLs in the Getting Started section of the providers, too. – The redirect URLs are the URLs that usually contain this query string: “?loginSocial=” )

    Once both of these are done, please check the login with Google again if you are still able to reproduce the problem or not. If you can, then please get in touch with us directly over the ticket system:

    and we will take another look.

    Best regards,
    Laszlo.

    Thread Starter central4all

    (@central4allgmailcom)

    I think i did everything you told me but now i get other error

    https://prnt.sc/DLgqpWdlVqrT

    Plugin Support Laszlo

    (@laszloszalvak)

    Hi @central4allgmailcom

    According to your error message, the problem is that, you haven’t added the new redirect URL to your Google App yet. As I suggested above, once you use the “OAuth redirect uri proxy page” setting, the redirect URL of the providers will change. So you will need to add the new redirect URLs to your Apps. Like I mentioned above we display a warning where if you click on the “Fix Error – OAuth Redirect URI” button, we will list all the steps you need to make. If you skipped that warning without making the suggested modifications, then you should check the Getting Started section as you will find the URL suggestion there, too.

    Note: don’t forget to check the Getting Started section of the other configured providers too as you will need to add the new redirect URL there as well. ( E.g. I can see you have Facebook configured as well. )

    Thread Starter central4all

    (@central4allgmailcom)

    https://prnt.sc/JP552438EXVY

    The redirect URL was already added, unless the URL itself is wrong (got it from the “Fix Error – OAuth Redirect URL” button prompt. Same with the Facebook URL

    Plugin Support Laszlo

    (@laszloszalvak)

    Hi @central4allgmailcom

    If I check the social buttons on the URL that you linked above, then I can confirm that currently we are trying to use the same endpoint that appears in your screenshot, so that is fine. However if I try to connect with Google, I still receive the error:

    Error 400: redirect_uri_mismatch

    and if I check the error details, it says the mentioned URL wasn’t added to that particular Google App.

    Are you sure you added that URL to the same App that you configured the Nextend Social Login with? As it is a common problem that people have multiple Google Apps, and they edit the wrong one.

    Could you compare the Client ID that you have in our “Client ID” field to the Client ID listed for the Google App where you tried to add the suggested URL as “Authorised redirect URIs”, please?

    Thread Starter central4all

    (@central4allgmailcom)

    thank you is fixed

    Thread Starter central4all

    (@central4allgmailcom)

    No is not fixed , is doing it again

    https://prnt.sc/SyF_BH7eLR7y

    https://prnt.sc/mv5g7dERWO3O

    Plugin Support Laszlo

    (@laszloszalvak)

    Hi @central4allgmailcom

    I checked the login with Google again, and the problem is that the pages you created for our “OAuth redirect uri proxy page” and “Page for register flow” settings are protected, and will automatically redirect you to your custom login page when you try to reach them.

    As I suggested above you need to make those pages public, otherwise your login redirect will prevent us from redirecting the users to those pages to handle the oauth and register flow.

    • This reply was modified 3 years ago by Laszlo.
    Thread Starter central4all

    (@central4allgmailcom)

    The pages are all public it’s something else that redirects them. I created a random new page called test2 and it opens properly. “https://seeme.baby/test-2/” if I select this new page under “OAuth redirect uri proxy page” in the plugin settings, the page stops opening and redirects to the main page. It only redirects to the main page when I use it in the plugin settings.
    Furthermore, the page (test2) opens properly when I put the [nextend_social_login_register_flow] shortcode in it. But if I select it from the dropdown “Page for register flow” it starts redirecting again.
    So in both page cases, it’s not the page itself that is redirecting but the plugin option is causing it.

    Plugin Support Laszlo

    (@laszloszalvak)

    @central4allgmailcom

    That is the expected behavior, since once you select a page for the “OAuth redirect uri proxy page” or the “Page for register flow” setting, we will reserve it for ourselves, and it should be accessible only during our OAuth and Register flow.

    Returning to the problem:
    Have you checked the page as a logged in user or as a logged out user? Since as a logged in user you probably won’t see that redirect to your custom login page, as you are already logged in.

    For example the same thing happens on some of the menu links as well, e.g.: if you visit this link as a logged out user:

    it will redirect you to the login page:

    Probably the same thing happens with the page, too that you created for our OAuth redirect uri proxy page and Page for register flow settings. So what you should check is the following:

    1. Set our “OAuth redirect uri proxy page” setting to None. ( Don’t forget the name of the page that was selected )
    2. Set our “Page for register flow” setting to None. ( Don’t forget the name of this page either )
    3. Open another browser where you are not logged in to your site ( or e.g. Incognito mode )
    4. Try to open the link of the 2 pages that you created for our “OAuth redirect uri proxy page” and “Page for register flow” and see if they load or they redirect to your custom login page.
      If they redirect, then something protects those pages from being accessed as a logged out user. You need to find the plugin that protects them, and make it accessible for the logged out users, too.

    In that case, if the 2 pages load fine, then please get in touch with us directly over the ticket system:

    and we will check this problem on your site.

Viewing 10 replies - 1 through 10 (of 10 total)

The topic ‘Error: The password field is empty.’ is closed to new replies.