JFBConnect will be integrated with it later this week. That will be for Facebook, Twitter and Google+ social profile import and will add a new registration flow so that you can actually use EasySocial's registration forms instead of JFBConnect's.
LinkedIn will be integrated into the next major release of JFBConnect (due out around the end of this year). We're still evaluating if we are going to enable the social profile plugin for EasySocial for JLinked. Due to the new registration flow option we're adding, it makes it difficult.
I hope that answers your question, but your feedback, as always, is welcome!
Wanted to get back to you and let you know that the social profile plugin for EasySocial will work with both JFBConnect and JLinked. With JFBConnect, there will be extra features, including the new ability to use EasySocial's registration flow. However, the profile import, user creation, skip activation and other things will work with JLinked using the "Automatic" or "Normal" registration options that JLinked offers.
When JLinked/LinkedIn is integrated into JFBConnect early next year, then it too will be able to use the EasySocial registration flow and other enhanced features.
I hope that helps explain. Obviously, your feedback will be welcome once JFBConnect v5.2 is released on Friday.
Thanks for the update Alex. I did the setup using the plugin for easy social and now I am unable to login with jlinked. I get this message;
There was an issue logging you in through LinkedIn. Please try again." Please advised
Sorry for the delayed response. We tested a bit with JLinked and EasySocial, but all the features available for JFBConnect (specifically, the new registration flow using EasySocial) wasn't possible. When we integrate LinkedIn into JFBConnect early next year, that will be an option.
With that said, can you let me know how you're performing registration? Are you doing "Automatic" or "Normal" registration within JLinked? It's possible we missed something in one of those flows.
Another thing to test is simply disabling the Social Profiles - EasySocial plugin. When you do that, does authentication work again? That will help narrow things down for us further.
Hi Alex, I had it performing auto registration with Es plugin enable. I disable the plugin and switched to normal registration and it's still doing the same thing. Before I enable the plugin, it was working fine. I deleted Linkedin account on my site that I logged in with after I enable the plugin. I am not sure if that will cause this.
Have you tried disabling the Social Profiles - EasySocial plugin to test if that fixes things? I'm not sure how that plugin would be preventing LinkedIn login, but narrowing it down to that plugin would definitely help diagnose things further.
As for deleting the user, that shouldn't cause the problem. However, make sure that there is no trace of the user in:
* EasySocial's user manager
* JFBConnect's User Map area
The user making the connection won't show up in the JFBConnect user map area if you're logging in with LinkedIn. That will still be in the JLinked User Map area, for now. Can you check there to see if it's working correctly?
If it's not showing there *and* the EasySocial profile plugin is disabled, that means the issue isn't related to that plugin. The problem is something specific to JLinked/LinkedIn.
In that case, can you clear browser cache, disable Joomla's caching and disable any SEF extensions you have enabled and then try again? That will narrow a lot of possible issues really quickly. If that works, we can narrow down things further, if not, it means that it's likely a communication issue with LinkedIn itself (either the API/Secret key are incorrect or LinkedIn is responding incorrectly).
Let me know how the above test goes, and we'll move on from there.
Sorry for the delay. I'm honestly unsure what could be causing the token from being retrieved from LinkedIn. If it's happening even when the EasySocial plugin is disabled, that eliminates that plugin as the cause and means it's just something with our LinkedIn extension in general. However, it's not something we've heard of before and other users aren't reporting anything similar.
The only other things I'd recommend is:
* Disable any SEF extensions you have enabled. If something is altering or redirecting the requests from LinkedIn ti a different URL (like a 'better' SEF one), that could be preventing their data from making it to JLinked.
* Private Message me a set of super admin credentials, and we can dig further into the issue.
Sorry for the delayed response. I just saw that you had sent an email to us and your credentials via Private Message.
I was just able to get into your site to investigate further. The reason you can't authenticate with LinkedIn is because your servers time seems to be off by a few minutes. Generally, JLinked should automatically detect this and correct this problem. I'm not sure why it's not able to on your site. When I enable the "Display LinkedIn API Errors" setting in JLinked, the following message is shown on the front-end:
JLinked Notice: Server time not in sync with LinkedIn. Setting correction offset to: 78s
For some reason our correction isn't working.
The best solutions to fix this on your site would be:
* Adjust your servers time forward by 78s.
* Enable NTP on your server, which is an automatic time synchronization function that will ensure your clock never gets off by too much in the future.
Please let me know if that helps,