I recently came upon some old code which I didn't write. It uses WWW::Facebook::API to login via Facebook to our website. It currently only calls WWW::Facebook::API::Users to get the user's info.
Now, my doubt is if I have to update this code to support the new OAuth 2.0 method or the newer Facebook Graph. According to this, the legacy Auth method is going to stop working on September. However, I don't know if WWW::Facebook::API uses this method. As far as I can tell, it does not pass any user's information to the browser, as it does server-to-server authentication. Has anybody dealt with this before?
I have been using this CPAN module and it is still working so I would answer my question. WWW::Facebook::API does not seem to have stopped working.
Related
At the moment (and for a long time now, as far as I know) there is no way to register an app on SoundCloud. I need to use their API to access public tracks. JavaScript is used. But I always get a 401/403 error response from the server.
As far as I understand, now it is possible to work only after authentication. But for that you need to register the application.
Tell me, is it possible to access API without application registration? I looked through the threads I found, but didn't see a clear answer. SoundCloud support didn't help at all either.
I have this really odd problem. The bosses in the office decided to do facebook tracking by using the [FBSettings publishInstall:<appIDhere>] in the app delegate. This works because the graph.facebook.com/<appID>/activities, etc are called, and Facebook returned true.
However, the problem is that this is NOT showing up in the dashboard. The app_activate shows up just fine, it's just that the app install is not showing at all.
So, my questions are:
Why is it that the install is not read correctly? The call is made and facebook response. Why is it that it's not showing up in the dashboard?
Does facebook do any other filtering? For example, if I delete the app and then reinstall, should the app be counted to have installed twice? In this case, the call to graph.facebook.com/ is made twice to send the MOBILE_APP_INSTALL activity. After this, does facebook do any other filtering? e.g. they remember device tokens, etc?
I am not quite sure how facebook differentiate using the URL scheme. I presume that this is to differentiate people who upgraded compared to people who installed. How does the fb<appid> help as a URL Scheme?
Thank you in advance for all your help.
I was hoping that someone had a current example of using the Facebook Javascript SDK to login and then using te PHP SDK to handle the session the rest of the time.
I've been Googling and trawling the web for an accurate, working example but they all seem to have some limitations or bugs.
I'm finding that after logging in with JS, the PHP seems to fail to find the session more often than not. I can see a FBRS cookie has been set and is always active but this doesn't seem to help.
Really tearing my hair out with this one...
Cheers
Seems like all my problems with the sessions were because of this bug: developers.facebook.com/bugs/404450666302585
I've updated to the latest PHP-SDK version and everthing seems to be alright.
My application is running within an IFrame and has been running fine for month. Since last week, the main page keeps refreshing because it looks lie the parameters auth_token and fb_sig_session_key are not provided to my iframe content anymore.
Has anything changed on the platform lately with that regard ?
Many thanks for your support.
Jonathan.
According to the Facebook Signed Request, you are only provided oauth_tokenalong with some other data, but nothing that looks like fb_sig_session_key. Try looking through the tutorial on the signed request, as well as the other authorization tutorials on Facebook. They provide the most up to date information.
If you are still using the Legacy Canvas Auth, you'll want to read the passage there about migrating. Instead of fb_sig_session_key, you should use Use the oauth_token for all API calls.
I want my users to be able to login or register on my Site using their Facebook-Account. Could be either like the user clicks the "Login using Facebook"-Button and is automatically logged in, while his data is saved to the db or he clicks "Login using Facebook" and gets my register-page filled with his data from Facebook.
I already tried the Facebook-register, but I think it doesn't solve the problem for me, because I don't want to change my entire register-dialog to Facebook. I want it additionally.
I managed to generate the "Login using Facebook"-Button using the Java-API. I also managed to get user-data via FQL using the PHP-API. But then I run into huge problems with the token.
I guess I read the (poor) documentation on FB-Developers for 20 times now. The Tutorials I found where either outdated or treat other cases. Besides that seemingly everyone uses another way to access FB.
Does anybody know an easy way to realize that and could clearly explain which functions, APIs, ... to use? Especially I feel like I still haven't totally understood that token-thing.
If someone is stuck with the same problems... For me it helped a lot to drop the JAVA-API and only rely on PHP.
See as well this tutorial: http://thinkdiff.net/facebook/php-sdk-graph-api-base-facebook-connect-tutorial/ (It's also a bit outdated, therefore you have to delete the call to the getSession-Method.)