Problem twitter and google

It looks like you have an SEF extension on your site that is re-writing the URLs for JFBConnect. Google+, Twitter and JFBConnect in general cannot have our URLs modified because there is specific data written in the URLs that's required for authentication to be performed.

Please setup your SEF extension to 'skip' altering URLs for JFBConnect. Once that's done, the registration flow should work properly.

If not, or you run into any other issues, just let me know.

Thanks,
Alex

Alex,
Sorry you're running into issues with Google and Twitter authentication.

For Twitter, the error you're receiving is because you haven't specified a Callback URL in your Twitter Application. That URL should just be your domain name/callback, like "www.dackelclub.de/callback". That should get you past that error, and hopefully make Twitter work as expected for you.

I'm honestly not sure why Google is throwing that message. I'd recommend fixing Twitter to see if it has a similar issue getting your user information. That will help us narrow down where the problem is, depending on whether it's an issue that affects one, or both, social networks.

As for other benefits, JFBConnect allows for a more customized registration flow, including pulling data from each social network into the user's EasySocial profile. Beyond just EasySocial integration, we have Open Graph Actions, which let you post to a user's Timeline when they interact with your site (uploading photos, leaving reviews, voting for content, etc), Facebook invitations/requests, Open Graph tags for lots of different types of extensions, social sharing buttons and more.

I hope that helps get you started, but we'll figure everything out and get you going soon!

Thanks,
Alex

For Twitter, that's actually normal behavior. Unfortunately, Twitter doesn't allow any application to grab a user's email address.. so that's information that the user must type in. The password field can be hidden in our configuration settings though, so that it's automatically generated for your users. That's up to you.

Facebook, Google and LinkedIn all do allow fetching of the user's email address, which allows for automatic registration.

For Google, I'm not sure what's happening there. Would it be possible to send us admin access to your site to investigate further? We can likely get to the bottom of the issue otherwise, but that is the fastest method. If so, please Private message us the details by clicking the mail icon under my picture to the left.

Thanks,
Alex

Just wanted to let you know that we're still looking into this. When enabling the "Debug Mode" setting in JFBConnect, the following message is showing on the front-end:

Error code 400 received requesting access token: { "error" : "invalid_request" }.

That message usually means that a redirect is occurring before JFBConnect can process the authentication information from Google. The redirect strips some of the data that is supposed to be posted back to us, which makes it impossible for JFBConnect to properly authenticate the user.

If possible, can you PM me FTP access to your site? If not, we can install a file manager extension so that we can make some edits to do what we need. FTP makes things easier to really dig in and edit though, so if that's not ok, no problem.

Thanks,
Alex

Thanks for installing extPlorer. We did a lot of debugging on your site tonight, but were unable to determine what's going wrong. Everything seems perfect. The code coming back from Google is right, the request we're making back to Google is correct. We tested with a different API/Secret key as well with the same results.

We're going to continue investigating, but I really don't have any good answers for you right now as to what may be happening.

Do you have another website that you can test on? From the tests above, it seems like Google just won't respond with an authorization token for a user on your site. That's not something we've ever seen before or can understand why it would be happening. Its our best guess to test on another server though, as the API/Secret key we tried is known to work properly.. so your server is the only unknown in the equation.. but I don't know why.

Thanks,
Alex