kstockl,
Thanks for chipping in and letting us know what works for you. You *should* be able to leave the Import Profile Always setting at 'yes', if that's what you want. If you're having issues there, and want that feature, definitely let us know. Also, so you know, in the 6.2 release (later this summer), we're planning a way to individually select what gets imported on login. For instance, you'll be able to say that profile data is imported on registration only, but a user's avatar is always imported. I hope that makes sense.
cliffordsean,
If you're using a 3rd party profile extension, like EasySocial, JomSocial, CommunityBuilder, or even the built-in Joomla User - Profile extension, you'll need to go to the Plugin Manager and enable the appropriate "Social Profile" plugin. Those are installed with JFBConnect and let you control how data is imported into those extensions from the social networks.
what do you mean by " Those messages are hidden from standard users normally " ? you mean that debugging has to be switched on ?
When trying to authenticate, an error may be returned from Google. Usually it's an ugly message about a token or an invalid call or something. If debugging is disabled, we'll simply say "Authentication failed" (something readable by a standard user). If you've turned on the "Enable Debug Mode" in JFBConnect and we get an error message back from Google, we'll display that on the front-end as it may help diagnose the issue.
I *do* see the "Debug System" setting in the Joomla Global Configuration area is on, but that's a separate setting. Please make sure you are enabling the JFBConnect debugging setting.
Going back to your issue, I just tried to authenticate on your site with Google. I'm seeing the same issue you mention.. bascially, I'm returned to your home page with no message and not logged in. Once thing I notice from your Autotune results is that you're using a pretty old version of JFBConnect, v5.2.2. I don't recall any Google+ authentication issues specific to that release. However, JFBConnect v6.0.6 is out now and there have been vast improvements to the underlying architecture from v5.2 to 6.x. Upgrading alone may fix the issue, and it should be a pretty painless process.
Beyond that, I'd have to ask for super admin credentials to investigate further if authentication still doesn't produce an error or upgrading doesn't fix the problem.
Thanks for your patience,
Alex