...
| Div | ||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||
|
...
If you are an Elgg developer, Social Connect gives you as much control as you need by triggering hooks and raising events as users are registered, connected or logged into the system. In the plugin settings you can specify the desired default response to the social_connect,user hook, at a global or per-provider level:
- Always: social connection is always allowed
- Never: social connection is never allowed (use this only if you have a plugin that could change the response)
- Once per email: the email address is checked against the Elgg user database and if it already exists the corresponding user is connected
- Only with email: same as Once per email, but if an email address is not provided by the social network (for example, Twitter) then social connection will fail.
Social Connect uses HybridAuth as the connection engine and was loosely inspired by the elgg_social_login plugin.
...