Log in | Register
  1. Forum
  3. Discontinued Products
  5. JFBConnect Joomla 2.5 Support (CLOSED)
  7. JLinked issues sink migration

Topic-icon JLinked issues sink migration

Active Subscriptions:

None
10 years 4 weeks ago #42452 by simpre
Hi to the Forum,

Since upgrading to the latest version integrating JFBConnect and JLinked I have had an issue whereas new users are not able to register. Facebook and Twitter work fine and there is an issue my developer is looking at for Google but JLinked existing users seem to have been wiped - me being one of them. I can log in to my account manually but just not using Linked In. It just returns to the page as though I haven't pressed the Log In with Linked IN button.

Also weirdly the link with SC Login seems to now mean that unless someone logs in using social media that they can't log in at all.

Anyone found the same problems and if so any advice?

Simon
The topic has been locked.
Support Specialist
10 years 4 weeks ago #42456 by alzander
I just went to your site and logged in using LinkedIn. My account was properly created and I was logged in as expected. So, it seems like it's working for new registrations. Hopefully, you're seeing the same behavior with new registrations.

As for returning users, can you try the following and let me know your results:
* Can you go to the JFBConnect -> Usermap area and see if the mapping for LinkedIn exists between you and your Joomla user? If not, you'll need to make sure you migrated your settings from JLinked.
* When you migrated, did you create a new LinkedIn Application? You should *not* have created a new app and should be using the same API/Secret key you were using in JLinked.
* In the JFBConnect -> Configuration area, set the "Enable Debugging" setting to 'Yes'. Then try to login and see if any error messages appear.

Hopefully that will give some clarity into the issue.

Thanks,
Alex
The topic has been locked.
Active Subscriptions:

None
10 years 4 weeks ago #42466 by simpre
Hi Alex,

Thank you for the speedy response. New user registrations seem to be running fine. After my note to you I realised that on the Gantry template I had disabled system messages and this was causing some flow issues which are now resolved. New users are fine so the new set up seems OK for them.

The error message for me using an old account befe the upgrade is as below:-

We were unable to retrieve your LinkedIn account information. Please try again.

Error code 400 received requesting access token: {"error":"invalid_request","error_description":"missing required parameters, includes an invalid parameter value, parameter more then once. : Unable to retrieve access token : appId or redirect uri does not match authorization code or authorization code expired"}.

I remember that after the migration I couldn't get the log in to work so I ended up deleting my old account through the user map to than try and log in as a new user and link that way. I believe the top message relates to the fact that it can't find my old account (this was in blue) and the bottom message is because it has found a link before and it is unable to find the link again.

I followed the step-by-step process detailed on the migration information. It may be that I have done this wrong and appreciate your feedback if this is the case.

Any advice you have is gratefully received with this additional information.

Thanks,

Simon
The topic has been locked.
Support Specialist
10 years 3 weeks ago #42590 by alzander
Sorry for the delay. I'm totally stumped as to what the problem may be. The only thing that I've thought of is if you are using an older LinkedIn Application which hasn't been 'upgraded' yet. The upgrade changes how the app works slightly by allowing for more granular user permissions. JLinked worked with both types of apps (old and new), JFBConnect would only work with the new.. however, I believe all apps were auto-upgraded some time ago. Just to check and be on the safe side, can you (according to the LinkedIn instructions)

To opt-in your API key, click the Use Member Permissions checkbox in your Application Details page. Once you submit the form, it can take up to 15 minutes for this change to go live. Remember: You can opt-in anytime, but you can never leave.

Basically, go to the LinkedIn developer area and see if there are any settings to "Upgrade" or "Use Member Permissions". If so, check the box and hit save.

Beyond that, I'm not sure what would be causing that error. Can you test and/or see if there are any other previous LinkedIn users on your site that are having the same issue?

Keep me posted. We'll do everything we can to get you around this issue.

Thanks,
Alex
The topic has been locked.
Active Subscriptions:

None
10 years 3 weeks ago #42645 by simpre
Hi Alex,

I followed this route but couldn't see the button you mention to allow an upgrade. With this in mind I recreated the key from scratch (interestingly just coping exactly the same information to a new API set up) and it all has started working again now.

Appreciate your support. I guess for a set-up point it may be worth adding a note that a new key could be required with JLinked if the set-up doesn't automatically work. It may be that other users - brighter or more used to upgrades :) have discovered it without the need to ask.

Thanks again for your time.

Simon
The topic has been locked.
Support Specialist
10 years 3 weeks ago #42662 by alzander
I'm glad you got things going. However, I'd urge you to really verify that things are working how you want. LinkedIn assigns each user a unique 'user ID' based on the API key. When you change that API key, the user ID for any previous users will no longer be valid.

This generally shouldn't be an issue. If you have the "Automatically link users by email" setting enabled, the next time a user logs in, they're JFBConnect 'mapping' to LinkedIn will automatically be updated with their new ID. That's, of course, if they haven't changed their email address on your site or LinkedIn so that they still match.

Beyond that, the user will have to 'approve' your new LinkedIn application the first time they login again.

It shouldn't really cause many/any other issues, but I just want to call out the difference when creating a new LinkedIn App. It's always recommended to keep using the same key. I'm clueless as to why things weren't working on your site though.. and it likely was a problem with an older LinkedIn key since we haven't heard of that with other migrations.

I hope that helps explain, and should you need anything else, just let us know!

Thanks,
Alex
The topic has been locked.
Active Subscriptions:

None
10 years 3 weeks ago #42685 by simpre
Thanks Alex,

I have double-checked that this option is marked and it is so it will pick up previous users via email.

Appreciate your support and the additional post. Typical of the service SourceCoast is known for.

Simon
The topic has been locked.
Support Specialist
10 years 3 weeks ago #42692 by alzander
Glad to hear your positive results. I didn't really think it would be a problem, but always best to call out possible issues, or at least things to look out for, ahead of time.

As always, should you need anything else, just let me know.

Finally, if you haven't already, please consider leaving a rating and review for JFBConnect, or our support, on the Joomla Extension Directory. It certainly isn't required, but is very appreciated:
extensions.joomla.org/extensions/social-...ook-integration/7215

Thanks,
Alex
The topic has been locked.
  1. Forum
  3. Discontinued Products
  5. JFBConnect Joomla 2.5 Support (CLOSED)
  7. JLinked issues sink migration
From the Blog
Facebook | Twitter | LinkedIn | Blog RSS