将 Facebook Canvas 应用程序(自 2010 年 3 月以来未受影响)迁移到 OAuth 和 HTTPs 的第一步 --
我不是专业程序员。我是“厨房餐桌编程爱好者”。我的问题是在这篇叙述的最后。
2010 年 3 月,我想出了如何通过将我的 Web 应用程序转变为 Facebook Canvas 应用程序来向世界介绍我的交互式数据库驱动的 Web 应用程序。
基本上,我在 2010 年 3 月之前使用“傻瓜”书籍使用 MYSQL、PHP、HTML、JavaScript 等构建了我的 Web 应用程序。当我确信我的网络应用程序可以作为独立网站使用时,我仔细研究了 Facebook 在线文档,以找出如何将我的应用程序变成 FB Canvas 应用程序。
那是在 2010 年 3 月。当时将 Web 应用程序转换为 FB Canvas 应用程序的过程基本上涉及获取如下文件,并将它们保存到我的 Web 主机服务器上的目录中:
-- At public_html:
-- config.php
-- facebook_desktop.php
-- facebook_mobile.php
-- facebookapi_php5_restlib.php
-- fbtest.htm
-- JSON.php
-- jsonwrapper_inner.php
-- xd_receiver.htm
-- At public_html/php:
-- facebook.php
现在这是我的问题:
我的应用程序有自 2010 年 3 月以来一直运行良好,但现在(从今天早上开始)我的应用程序根本无法运行(甚至无法打开)。我怀疑这是由于与迁移到 OAuth 2.0 和 HTTPS 相关的要求发生了变化——我需要学习如何应对这些要求。
为了至少让自己能够继续在 FB 上使用我自己的应用程序,我的第一步应该是什么?一旦我们弄清楚了这一点,我将寻求有关如何再次允许其他 FB 成员使用我的应用程序的指导。
我希望有些人会觉得这个帖子有帮助。
谢谢你, FL
I am not a professional programmer. I am "a kitchen table programming enthusiast." My question is at the very end of this narrative.
In March of 2010, I figured out how to introduce my interactive database driven web app to the world by turning my web app into a Facebook Canvas Application.
Basically I built my web app prior to March 2010 using MYSQL, PHP, HTML, JavaScript, etc. using "dummies" books. Once I was convinced that my web app was functional as a standalone website, I pored through Facebook online documents to figure out how to turn my app into a FB Canvas App.
That was in March of 2010. Back then the process for turning a web app into a FB Canvas App basically involved getting files like the following, and saving them to the directories on my web host server:
-- At public_html:
-- config.php
-- facebook_desktop.php
-- facebook_mobile.php
-- facebookapi_php5_restlib.php
-- fbtest.htm
-- JSON.php
-- jsonwrapper_inner.php
-- xd_receiver.htm
-- At public_html/php:
-- facebook.php
Now here is my question:
My app has been working fine since March 2010, but now (since this morning) my app doesn't work at all (doesn't even open). I suspect this is due to requirements that changed related to migration to OAuth 2.0 and HTTPS -- requirements which I need to learn how to respond to.
What should be my first step toward at least enabling myself to continue using my own app on FB? Once we have figured that out, I will be seeking guidance on how to once again enable other FB members to use my app.
I hope some will find this thread helpful.
Thank You,
FL
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(2)
这里有一个概述: https://developers.facebook.com/docs/oauth2-https -migration/ 链接到文档和博客文章,其中提供了如何迁移的示例
There's an overview here: https://developers.facebook.com/docs/oauth2-https-migration/ which links to the docs and the blog posts which gave examples of how to migrate
太感谢了!
我已经开始审查您提到的材料。我将继续深入研究,但我想让您知道,目前,我看到这些短语在我的脑海中提出了问题:
基于我原来帖子中的详细信息,能够确定我当前是否已经实现了 PHP SDK 还是 JavaScript SDK?我不知道我是否使用过 SDK 来建立我的身份验证和授权方法。我只知道我的方法是申请一个FB App ID、App Secret并将一组文件复制到我的服务器。我2010年3月的实现方法是否太旧了,既不是PHP SDK也不是JavaScript SDK?
“更新 SDK”是否要求我首先实现某种 SDK?
如果事实证明我没有使用 SDK 作为我古老的身份验证和授权方式的一部分,那么哪组指令真正适用于我迁移到 OAuth2.0?
我担心如果没有看到一步一步的说明,我的服务器上最终会出现无关且冲突的文件。
有谁知道任何迁移说明,例如“用这些文件(文件 E、文件 F、文件 G 和文件 H)替换 Web 主机服务器中的这些文件(文件 A、文件 B、文件 C 和文件 D)”
谢谢,
佛罗里达州。
Thank you, so much!
I have begun reviewing the material you have referred. I will continue to dig in, but I'd like to let you know that for now, I see these phrases which raise questions in my mind:
Based on details in my original post is one able to determine whether I have currently implemented a PHP SDK or the JavaScript SDK? I don't know that I ever even used an SDK for establishing my means for Authentication and Authorization. I only knew my method as applying for a FB App ID, App Secret and copying a set of files to my server. Was my implementation method from March 2010 so old that it is neither PHP SDK nor JavaScript SDK?
Doesn't "updating an SDK" require that I had first implemented some sort of SDK?
If it turns out that I haven't used an SDK as part of my archaic means for authentication and authorization then what set of instructions is really applicable for me to migrate to OAuth2.0?
I am concerned that without seeing a step by step set of instructions, I will end up with extraneous and conflicting files on my server.
Does anyone know of any migration instructions like, "replace these files (file A, file B, file C and file D) from your web host server with these files (file E, file F, file G and file H)"
Thank you,
FL.