I came to the office today to work a little more on my almost completed Facebook Connect website.
And for some reason I discovered that the onlogin event for the fb: login button of the FBML control no longer fires !!?!
For anyone with the Facebook Connect FBML app (and using the JavaScript API for authentication), I would advise you to test your app to make sure it still works.
A friend of my application (who lives) has also stopped working from today.
What you do by clicking the "Connect to Facebook" button, you will see the FB login dialog box. Log in.
Yes, they correctly logged into Facebook (fortunately), but the onlogin callback event no longer fires, so the page just sits there (where before the onlogin event goes to the main page, for example).
Of course, if you update, you are logged in to Facebook.
Seriously, WTF - what did these Facebook developers do now?!?!.
Any ideas? Has anyone read any updates / threads on this issue?
UPDATE:
8 hours and still no fix. I tried to do some workarounds (there is also an onclick event of the FBML login button), but all this is too early in the authentication loop.
We need to be able to connect to the return message after logging in to do things like redirects, pop-ups with permissions, authentication logic, etc.
Nothing can do without fixing Facebook.
I just hope that tomorrow, when I come to the office, it will be "magically" fixed, it seems that this problem has "magically" appeared.
Well, judging by the comments here, I'm not alone. Obviously, at that moment, Facebook changed something without telling us.
I just hope they fix this problem as soon as possible since there is no workaround I can see for this.
UPDATE 2
Yep - (drum roll), his another mistake from this world-class development team on Facebook: (thanks Anon for the link) http://bugs.developers.facebook.com/show_bug.cgi?id=11733
I like how a comment from a guy from FB Mark says: “It seems that this is happening on the old Facebook Javascript SDK”, well, let us do server-side authentication with your graphical API (and not just for user / posting information) , and we will not use the old JavaScript API!
Fun and games.
FINAL UPDATE
Facebook (apparently) fixed it.
Let him hope that he remains fixed.
Given the “correct” answer to Anon (since he found the link).