当前位置：文江博客话题详情

Facebook Connect不再触发回调（截至今天）

发布于 2024-09-12 22:36:22 字数 1423 浏览 5 评论 0原文

今天来到办公室，对我即将完成的 Facebook Connect 网站应用程序进行更多工作。

而且我发现由于某种原因，fb:login 按钮 FBML 控件的“onlogin”事件不再被触发！！？！

对于拥有 Facebook Connect FBML 应用程序（并使用 JavaScript API 进行身份验证）的其他人，我建议您测试您的应用程序以确保它仍然正常工作。

我的一个朋友的应用程序（已上线）从今天起也已停止工作。

发生的情况是，您单击“连接到 Facebook”按钮，它会显示 FB 登录对话框，您登录。

是的，他们正在正确登录到 Facebook（值得庆幸的是），但“onlogin”回调事件没有被触发不再如此，所以页面就坐在那里（例如，在“onlogin”事件之前将重定向到主页）。

当然，如果你刷新，你就登录到了 Facebook。

说真的，WTF - Facebook 的开发人员现在做了什么？！？！。

有什么想法吗？有人读过有关此问题的任何更新/线程吗？

更新：

8小时了，仍然没有修复到位。我尝试过一些解决方法（还有 FBML 登录按钮的 onclick 事件），但在身份验证周期中还为时过早。

我们需要能够挂钩登录后回调来执行重定向、权限弹出窗口、身份验证逻辑等操作。

如果 Facebook 不解决这个问题，我们将无能为力。

我只是希望当我明天来到办公室时，这个问题会“神奇地”得到解决，就像这个问题“神奇地”出现一样。

从这里的评论来看，我并不孤单。很明显，Facebook 在没有通知我们的情况下在某个地方做出了改变。

我只是希望他们尽快纠正这个问题，因为我看不到解决方法。

更新 2

是的 - （鼓声），这是来自 Facebook 世界级开发团队的另一个错误：（感谢 Anon 找到链接）http://bugs.developers.facebook.com/show_bug.cgi?id=11733

我喜欢 FB 人 Marc 的评论：“似乎只发生在旧的 Facebook Javascript SDK 上”，好吧，让我们能够使用您的 Graph API 进行服务器端身份验证（而不仅仅是检索用户详细信息/发帖），我们不必使用旧的 JavaScript API！

乐趣和游戏。

最终更新

Facebook（似乎）已经解决了这个问题。

我们希望它保持不变。

给出 Anon 的“正确”答案（因为他找到了链接）。

原文

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?

UPDATE:

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.

UPDATE 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

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.

FINAL UPDATE

Facebook have (seemingly) fixed this.

Let's hope it stays fixed.

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

分享到QQ

分享到微博