Viewing 2 replies - 1 through 2 (of 2 total)
  • rubenlinux

    (@rubenlinux)

    I did the same like you, but this is what worked for me

    Deactivate other plugins taht may be interfering with “WordPress Social Login” (WSL). For example a plugin that requires API’s from the same networks you have used with WSL. I did that and is working perfectly now. ??

    This error occurs for one of two reasons. The first is is the PHP session data cannot be written for any reason, then when WSL looks for the configuration, it doesn’t find it and falls over. This will be related to all kinds of things like how your session is setup to work and whether the client has cookies enabled etc. You might have to write a test page to at least see if PHP sessions work on the server at all with your browser.

    The second reason is related and occurs if, for example, you have finished the authentication in a different browser than you started in. I have seen this where the user has reset their OAuth2 account during sign-in and returns to the browser from somewhere else. The session is different per-browser, so the plugin fails again and gives the same error. I don’t know if this is a design decision or whether it is just a big related to the way the plugin is designed.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘406. The session identifier is missing.’ is closed to new replies.