This is a huge milestone for CB Connect. The HybridAuth API library has been completely removed in favor of our own lightweight API library. Beta 5 brings back full functionality for all the following providers.
Facebook
Twitter
Google
Foursquare
GitHub
VKontakte
LinkedIn
Windows Live
Instagram
Steam
Your existing configurations should continue to work fine. The exception being field mapping for each provider under the Registration tab of their configuration. All fields returned by a social sites user API call are now available to map. This significantly increases the number of fields available based off the provider.
Additionally permissions parameters are back. I do not recommend changing the permissions unless you need to request a field that needs it or you intend to use the new API to make your own API calls.
With the rewritten library it's significantly easier to maintain and implement OAuth1, OAuth2, and OpenID providers. So additional providers can be request at this time up until RC1 where CB Connect 7.x will be feature locked. The following providers are currently being reviewed for implementation.
Disqus
Stackoverflow
Tumblr
TwitchTV
Reddit
I highly prefer OAuth2 providers as they're easier to implement and maintain, but either of the 3 will be fine assuming the provider has well documented API. Please note if a provider is not in English and does not provide English documentation it will not be implemented, sorry.
Please note configuration instructions will be provided for the more popular providers while the others may be left to the providers own documentation. See the below for current configuration information.
www.joomlapolis.com/forum/6-news-and-publicity/229505-configuring-cb-connect-7x
NOTICE! CB Connect 7.x is a BETA. If you are not prepared for issues or can not accept the above current state of CB Connect 7.x then do not use it. If you have any issues please post to the support forums. Do not post support requests here.
krileon
