Hi Alex,
"...If you can explain more about the flow you want your users to have..." = For sure, I love your (Alex and Melissa) support and to share with you is always a pleasure!
Give me some attention, because my English is not the best and the explanation is articulated, simple, but articulated.
"map link" = it was an unhappy expression of mine, I just wanted to say that I can login through socials and link them to my existing Joomla account. The result can be viewed into the JFBConnect > "User Map" menu. However it doesn't matter.
Basically there are 4 cases on where we can call the Social Buttons and, right now, always to *Send them to the
Login / Register page so they can determine what they should do":
1 - JFBConnect > Configuration > General > Integrate into Joomla Login: enabled
On the "
joomla LOGIN page" will appear your Social Buttons.
When a user is into the Joomla Login page it is because he wants Login.
Clicking on them, from the joomla Login page, users should always be sent to the Social Button Login page, without the Register page part. Limit the Social Buttons feature to the Login one (to connect), hiding the "jfbc_loginregister_newuser" into the page.
2 - JFBConnect > Configuration > General > Integrate into Joomla Login: enabled
On the "
joomla REGISTRATION page" will appear your Social Buttons.
When a user is into the Joomla Registration page it is because he wants Register.
Clicking on them, from the joomla Registration page, users should always be sent to the Social Button Registration page, without the Register page part. Limit the Social Buttons feature to the Register (to automatically register the user and create an account), hiding the "jfbc_loginregister_existinguser" into the page
3 - SCLogin Module > Social Button Settings > Show Social Login Button(s): enabled.
On SCLogin module will appear your Social Buttons.
In my case when a user is using the SCLogin module it is because he wants just Login. Anyway, I understand that other users can want it run as to "Send them to the Login / Register page so they can determine what they should do".
It is not my case, but for that reason I asked to "create a setting option to have them working just as: just Login / just Register / Both (right now)
4 - by adding the SCLogin Content Tags in any place we want.
It is not my case, but it is a must to have a Content Tag attribute to choose how to open your Login / Register page, as just Login / just Register / Both (right now).
Finally,
considering what described here
, there is another question that intersects with this: when setting a Social, I should be able to choose if I want to use it just for Loging (linking an existent user) OR also for Registering (automatically creating a new user).
So, in our case we could continue to use Instagram to connect the existent users, while we'll cannot to use it for creating users (because of the email issue).
Hope it is clear now, I remain available...
Social Login buttons workflow - request
