简体   繁体   English

Facebook Connect <fb:login-button>不再激活回拨(截至今日)

[英]Facebook Connect <fb:login-button> No Longer Firing Callback (As of today)

Came into the office today to do some more work on my nearly completed Facebook Connect website application. 今天来到办公室,在我近乎完成的Facebook Connect网站应用程序上做了一些工作。

And i have discovered for some reason, the " onlogin " event of the fb:login button FBML control is no longer getting fired!!?! 而且我发现由于某种原因, fb:登录按钮FBML控件的“ onlogin ”事件不再被解雇!!?!

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. 对于拥有Facebook Connect FBML应用程序(并使用JavaScript API进行身份验证)的任何其他人,我建议您测试您的应用程序以确保它仍然有效。

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. 发生了什么事情是你点击“连接到Facebook”按钮,它显示了FB登录对话框,你登录。

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). 是的,他们正在登录到Facebook(幸运的是),但是“onlogin”回调事件不再被解雇,所以页面就在那里(例如,“onlogin”事件将重定向到主页之前) 。

Of course if you refresh, you are logged into Facebook. 当然,如果你刷新,你就登录了Facebook。

Seriously, WTF - what have those developers at Facebook done now?!?!. 说真的,WTF - 现在Facebook的开发人员做了什么?!?!。

Any ideas? 有任何想法吗? Has anyone read any updates/threads on this issue? 有人在这个问题上阅读过任何更新/主题吗?

UPDATE: 更新:

8 hours and still no fix in place. 8个小时仍未修复到位。 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. 我试图做一些变通办法(FBML登录按钮也有一个onclick事件),但在认证周期中还为时尚早。

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. 没有Facebook解决这个问题我们无能为力。

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. 在这一点上显而易见的是Facebook在没有告诉我们的情况下在某处做出了改变。

I just hope they rectify this issue ASAP as there is no workaround i can see for this. 我希望他们尽快纠正这个问题,因为我没有找到解决办法。

UPDATE 2 更新2

Yep - (drum roll), its yet ANOTHER bug from that team of world-class developers at Facebook: (thanks Anon for finding link) http://bugs.developers.facebook.com/show_bug.cgi?id=11733 是的 - (鼓滚),这来自Facebook的世界级开发团队的另一个错误 :(感谢Anon寻找链接) http://bugs.developers.facebook.com/show_bug.cgi?id=11733

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! 我很喜欢FB家伙Marc的评论如何“只在旧的Facebook Javascript SDK上发生”,好吧,使我们能够使用您的Graph API进行服务器端身份验证(而不仅仅是用于检索用户详细信息/发布) ,我们不必使用旧的JavaScript API!

Fun and games. 有趣和游戏。

FINAL UPDATE 最终更新

Facebook have (seemingly) fixed this. Facebook(似乎)解决了这个问题。

Let's hope it stays fixed. 让我们希望它保持不变。

Given the 'correct' answer to Anon (as he found the link). 鉴于Anon的'正确'答案(因为他找到了链接)。

if in FB.getLoginStatus you are passing second parameter as true, pls make it to false. 如果在FB.getLoginStatus中您将第二个参数传递为true,请将其设为false。 I resolved callback issue using this trick. 我使用这个技巧解决了回调问题。

Thx 谢谢

Please confirm and vote on this bug... this should be fixed asap!! 请确认并对此错误进行投票......这应该尽快修复!!

http://bugs.developers.facebook.com/show_bug.cgi?id=11733 http://bugs.developers.facebook.com/show_bug.cgi?id=11733

这是一个错误,他们即将修复它

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM