• Resolved champdor

    (@champdor)


    Dear NSL,

    The site is a couple of weeks old (live). SL worked but after a while it started to display /wp-login/?socialLogin=google page empty white and did not logged in user.

    I have some redirect but not touching socialLogin: https://pastebin.com/EL3Fq7y7

    It was not working so I followed this solution of Laszlo: https://www.ads-software.com/support/topic/error-redirecting-when-signing-in-with-social-network-account/

    Please confirm what I did:

    1. Created /social-login/ page with shortcode, and empty /oauth-redirect/ page,
    2. set these two pages in NSL > Global Settings > General
    3. rewrote login page button links to /social-login/,
    4. set both social app redirect URIs to /oauth-redirect/ page.

    Now on button click user is redirected on home page and not logged in.

    Do I have to put some shortcode on /oauth-redirect/ as well? What did I miss?

    Regards,
    Champdor

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

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

    (@laszloszalvak)

    Hi @champdor

    As for the blank page ( /wp-login.php ):
    I checked the Pastebin code you sent, and as I see you are trying to redirect the /wp-login.php to the /belepes page.
    However in line 9 I can see and exit() and actually that’s why the site dies with a blank page, whenever the /wp-login.php page contains the loginSocial GET parameter.
    To prevent the redirection when the request is made by Nextend Social Login ( the request contains the loginSocial GET parameter ) you should rather use a “return;” statement instead of exit.

    But if the /wp-login.php is not available then usually it is better to use our “OAuth redirect uri proxy page” and “Page for register flow” features.

    The current problem that I see:
    You told you created 2 pages:

    • /social-login with the shortcode [nextend_social_login_register_flow] – so that should be selected for the “Page for register flow setting”.
    • and the empty /oauth-redirect page, that you should select for our “OAuth redirect uri proxy page” setting

    With this setup, your custom social buttons should contain the link of the “OAuth redirect uri proxy page” ( /oauth-redirect ) but currently on the linked page I can see they are pointing to the /social-login page, which is wrong.
    If you are not sure about the endpoints of the buttons, then you should open the “Usage” tab of the providers, and there you will find suggestions for “Simple link”, as you see in our documentation:

    So that is the URL that you should use for your custom social buttons.

    Another problem that I currently see is that, your links are wrong as they don’t contain the “loginSocial=<providerID>” part, e.g.: loginSocial=google. And actually that’s why we are redirecting you to the homepage, when you click on the link.

    So with your current configurations, a link should rather look like this:

    just instead of “example.com” you should use your own domain name. With that the login worked fine for me.

    If you still have a question or problem just let me know.

    Best regards,
    Laszlo.

    • This reply was modified 2 years, 9 months ago by Laszlo.
    Thread Starter champdor

    (@champdor)

    Dear Laszlo,

    Thank you for the speedy solution. It was easier to revert to normal wp-login.php. The exit() –> return solved the problem. OK I’m not a real programmer ??

    Thank you again, you rock!

    Champdor

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘White screen (empty html) after social login, tried custom redirect’ is closed to new replies.