Hello,
We wanted to test the Social addon to see if we could use it with UWP and replace the other social login plugin we use.
In testing, when I click either Facebook or google icon, the following occurs:
Pop up page notice:
“You’re now signed in with your Facebook account but you are still one step away of getting into our website.
New to our website?
Create a new account and it will be associated with your facebook ID.”
{button}
But I’m NOT a new user. In fact, when I click the button (the only option to proceed) it asks for a user name (does have a prefilled option based on my facebook name, and ability to change, which is great for truly new users) and when I then click Continue, it then fails and tells me the email address already taken.
“An error occurred while creating a new user: Sorry, that email address is already used!”
That’s understandable, as indeed I am not a new user. So why doesn’t it just assign /sync this Facebook login’s email account with the user’s email already in the website?
Or at least fill that Facebook user’s username as the prefilled info?
The other social login plugin we currently use works seamlessly – even when I place their shortcode in the template where this is:
div class="form-group text-center mb-0 p-0"
do_action( 'uwp_social_fields', 'login' );
Is this a known issue? Something on the roadmap? Or doing it wrong?
I can continue to use the other plugin, but if we continue to rollout UWP in place of other plugins I just wanted to try to stay with your addons as well.
Thanks.