09-18-2016, 11:47 PM
Check out the latest Alpha, which is a bridge to 5.0. We're not releasing a 4.1 to 4.2 update for the alpha version, but one will be available for final release. Feel free to install 4.2 and play with it. Note that the main reason social logins were never integrated in the past is that there is setup that needs to be done on the user's side in order for them to work.
Documentation is here http://userspice.org/documentation-social-logins/ to guide you through the process. Expect about 10 minutes of config for each Facebook and Google. The good news is that you can use the same keys you generate on the final release of 4.2.
Integration is kind of cool. On many sites, when you create a "traditional" account, you're locked into that login method from there on out. If you try to login with a social login, it just creates a new account. UserSpice has solved that. Regardless of whether you login traditionally, via Facebook, or via Google, your user will have ONE account and the permissions will transfer regardless of how the user signed in.
Some things could be cleaned up a little bit on the code side, but it does function nicely.
A few notes: Most people when they start developing with something like that are going to go crazy signing in from a bunch of accounts and manually removing users from the database. That's fine, but after spending a fair bit of time developing this, my suggestion would be to do your tests in incognito or private browsing mode. Also, feel free to go into Google and Facebook (as the end user) to "revoke" your sign in privileges on your own site. That will give you more of a real world experience.
Documentation is here http://userspice.org/documentation-social-logins/ to guide you through the process. Expect about 10 minutes of config for each Facebook and Google. The good news is that you can use the same keys you generate on the final release of 4.2.
Integration is kind of cool. On many sites, when you create a "traditional" account, you're locked into that login method from there on out. If you try to login with a social login, it just creates a new account. UserSpice has solved that. Regardless of whether you login traditionally, via Facebook, or via Google, your user will have ONE account and the permissions will transfer regardless of how the user signed in.
Some things could be cleaned up a little bit on the code side, but it does function nicely.
A few notes: Most people when they start developing with something like that are going to go crazy signing in from a bunch of accounts and manually removing users from the database. That's fine, but after spending a fair bit of time developing this, my suggestion would be to do your tests in incognito or private browsing mode. Also, feel free to go into Google and Facebook (as the end user) to "revoke" your sign in privileges on your own site. That will give you more of a real world experience.