Hi All,

Came into the office today to do some more work on my nearly completed Facebook Connect website application.

And i have discovered for some reason, the "onlogin" event of the fb:login button FBML control is no longer getting fired!!?!

To anyone else that has a Facebook Connect FBML app (and using the JavaScript API for authentication), i would advise you test your application to make sure it's still working.

A friend of mine's app (which is live) has also stopped working as of today.

What's happening is you click on the "Connect to Facebook" button, it shows the FB login dialog, you log in.

Yes, they are being logged in to Facebook correctly (thankfully), but the "onlogin" callback event is not getting fired anymore, so the page just sits there (where before the "onlogin" event would redirect to the homepage, for example).

Of course if you refresh, you are logged into Facebook.

Seriously, WTF - what have those developers at Facebook done now?!?!.

Any ideas? Has anyone read any updates/threads on this issue?


8 hours and still no fix in place. I've tried to do some workarounds (there is also an onclick event of the FBML Login Button), but it's all too early in the authentication cycle.

We need to be able to hook into a post-login callback to do things like redirects, permission popups, authentication logic, etc.

Nothing we can do without Facebook fixing this.

I just hope when i come in the office tomorrow this will be 'magically' fixed, much like this issue 'magically' appeared.

Well judging by the comments here i'm not alone. It's obvious at this point that Facebook have made a change somewhere, without telling us.

I just hope they rectify this issue ASAP as there is no workaround i can see for this.


Yep - (drum roll), its yet ANOTHER bug from that team of world-class developers at Facebook: (thanks Anon for finding link)

I love it how the comment from the FB guy Marc says "Only seems to be happening on old Facebook Javascript SDK", well, enable us to do server-side authentication with your Graph API (instead of just for retrieving user details/posting), and we wont have to use the old JavaScript API!

Fun and games.


Facebook have (seemingly) fixed this.

Let's hope it stays fixed.

Given the 'correct' answer to Anon (as he found the link).


Same problem here.....onlogin event is not triggered....was working fine till yesterday

I propose the next StackExchange site to be "", and the FB developers should all get emailed whenever a question is raised. =)

Same problem. I am using it for last 8 months and all of a sudden it stopped working... suggestions are welcome. please help

i would if i could. unfortunately without the callback there is not a lot we can do. facebook control the client-side event.

same problem, but today fails FB.init("xxx", "xd_receiver.htm", { "reloadIfSessionStateChanged":true, "permsToRequestOnConnect": "photo_upload" });

just a note, make sure your xd_receiver file is registered as '/xd_receiver.htm', not 'xd_receiver.htm' - otherwise Facebook will look for that file relative to any page that makes a request. I assume you put the xd_receiver file in the root of your app. I fell into this gotcha. Not saying this is your issue, just be aware of it.

same problem here, it's a joke. faceobook is a piece of crap.

@rick - i concur.

Please confirm and vote on this bug... this should be fixed asap!!

Hehehe, well at least we have confirmation. Now we play the waiting game.

This is a bug and they are about to fix it


I am still having this problem.. does the bug strikes again ?

Gokhan B.
They're making changes, i can tell - because random things are happening. I now get a popup with my own website and the session id in the URL??? idiots.
old api sucked way too much.. I'm switching to new graph api. hope they wont break it without notification :)
Gokhan B.

related questions