I noticed that there are several FB.getSession calls that still on FB.js, I read the documentation on FB Developer site that they removed FB.getSession. I hope we can remove it in the future in favor og FB.getAuthResponse()
And also as of Feb 1, 2012 I noticed that FB._oauth always returns "undefined" now and this is consistent, because of this FB.getSession will be called and that is not available anymore and on chrome it throws "Uncaught TypeError: Object #
has no method 'getSession'". And as of standing this module is broken because if this.
As for the quickfix on my site I removed the condition that checks FB_oauth and it will always run the statement IN IF condition that is to run FB.getAuthResponse() and I commented/removed the statements on ELSE that calls FB.getSession.
I hope this helps...
Thanks!
Comments
Comment #1
euphoric_mv commentedI have the same problem. In which file i suppose to change that you describe and on which line? I found fb._oauth in fb.js file but there are 2 if (FB._oauth) statement.
Thank you a lot!
Comment #2
euphoric_mv commentedI just did what you said and i dont get "Uncaught TypeError: Object # has no method 'getSession'" in console anymore. But facebook connect still doesnt work. This began to happens today. I dont know what to do. Did facebook change some code or what, i realy dont get it...
Comment #3
ervindm commentedYou need to do that for both. That willforce them to use FB.getAuthResponse(). Thanks!
Comment #4
pdouglas commentedThis works for me, but isn't the correct solution.
I generated a patch.
Tanks for this quick fix ervindm!
Comment #5
r2b2 commentedHello,
Im having infinite reload loops when logging out if I remove the oauth lines as posted originally.
Comment #6
r2b2 commentedActually it works when I tick :
"Append hash on javascript page reload" on admin/build/fb/settings.
Thanks a lot for this hack!
Comment #7
aleada commentedwith the above settings the facebook connect works fine.
If anyone has problem with the logout link please take look at http://drupal.org/node/1364394
Comment #8
hate90 commentedthanks armatech your txt worked perfectly
Comment #9
Shven commentedthe module works as expected after applying armatech's patch. Tnx!
Comment #10
miccelito commented@amatech
Referring to your post #7
Using your suggestion I succeed to login without any problem or errors in the db report log.
But when I logout I need to click the logout link twice to be able to logout as well I get this db report log message:
Comment #12
msti#3 worked for me.
Thanks ervindm
Comment #13
Dave Cohen commentedI believe this is fixed in latest release. Please correct me if I am wrong. Tell me exactly how to reproduce.