Fixed Facebook External Accounts wrong Profile ID

[DaveX]

I have a problem with the Facebook integration. It works, but in the profile external-accounts the link to facebook profile.php?id= shows the wrong ID.

 

[DaveX]

I could solve it.

This is the link shown in external-accounts to my facebook profile:
https://www.facebook.com/profile.php?id=1404408836545969 It is the wrong link.

Now i changed in "account_external_accounts":

http://www.facebook.com/profile.php?id=

to

http://facebook.com/app_scoped_user_id/

Now i see this link in my profile:
http://facebook.com/app_scoped_user_id/1404408836545969
The link redirects to:
https://www.facebook.com/profile.php?id=100009305989536

This works fine. But it seems like a bug?

 

[Mike]

Yeah, it likely is because of the app scoped ID change. Unfortunately, I'm not sure if we know if we have a scoped ID (grandfathered applications), so this will need more investigation.

 

[Daniel Hood]

https://developers.facebook.com/docs/apps/upgrading#upgrading_v2_0_user_ids

1. App-scoped User IDs
Facebook will begin to issue app-scoped user IDs when people first log into an instance of your app coded against v2.0 of the API. With app-scoped IDs, the ID for the same user will be different between apps.

No matter what version they originally used to sign up for your app, the ID will remain the same for people who have already logged into your app. This change is backwards-compatible for anyone who has logged into your app at any point in the past.

Should be fine to use the /app_scoped_user_id method with grandfathered applications.


[Edit]
I just tested by going to the external accounts page (which says uknown account by the way) and changing the link to be /app_scoped_user_id/{my-id} and it didn't work. So, I don't know.

 

[Mike]

This is fixed now. We're querying the FB API on this page and that returns the correct profile link.

 

[DaveX]

Since the XenForo Version 1.4.9 i have the same problem again. If i use the option i post before, it works fine.

 

[Mike]

This appears to be related to the breaking changes in Facebook's API version 2.4. I have adjusted this for the next release.