Facebook API:通过Pages API从我的应用程序访问多个页面时出现问题
前提: 解决了永久令牌访问的奥秘之后,我已经能够从我的应用程序发布到我的Readerly.Ink页面上.
Premise: After solving the mystery of the permanent token access, I have been able to post on my Readerly.Ink page from my app.
问题: 但是,根据内容的语言,我的应用程序应该在多个页面上发布.因此,我今天创建了其他页面(Readerly-Italiano,Readerly-English等),但我无法通过该应用查看它们!
Problem: My app, however, is supposed to post on multiple pages, depending on the language of the content. Hence, I today created the other pages (Readerly - Italiano, Readerly - English etc) but I cannot see them through the app!
即使我获得了/me/accounts,我仍然只能看到原始的/第一本Readerly.Ink页面.我还尝试了:/new-page-id?fields = access_token& access_token =您的用户访问令牌(按照Pages API的说明)-但是我收到了错误消息! :-(
Even if i GET /me/accounts, the original/first Readerly.Ink page is all I see. I also tried: /new-page-id?fields=access_token&access_token=your-user-access-token (as per instructions of the Pages API) - but I get an error! :-(
问题: 如何将新页面添加到应用程序? 还是我需要为每个页面创建一个不同的应用程序?
Question: How do I add the new pages to the app? Or do I need to create a different app for each page?
据我所知,我创建的新页面与创建第一个页面的完全相同(我是管理员),并将它们全部添加到我的企业帐户中.
As far as I can tell, I created the new pages exactly as I created the first one (I'm the admin) and I added them all to my business account.
请告知.谢谢
还是我需要为每个页面创建一个不同的应用程序?
Or do I need to create a different app for each page?
不,您不需要这样做.一个应用仍然可以管理多个页面.
No, you don't need to do that. An app is still able to manage multiple pages.
过去曾经是您刚刚授予应用程序访问权限,以管理您具有管理员访问权限的所有页面.但是,由于这显然有点宽泛且充满风险,因此Facebook已经改变了一切-用户可以指定他们实际希望应用访问的页面.
It used to be that you just granted an app access to manage all pages you have admin access to. But since that is obviously a bit broad and risky, Facebook has since changed things - users can specify which of their pages they actually want an app to have access to.
在最初请求权限时,会在登录对话框中询问您这一点-但该列表稍后不会自动更新以包括在此之后创建的任何页面.
You get asked for that on the login dialog, when the permission is initially requested - but that list does not auto-update later to include any pages you created after that happened.
当前,似乎没有比将已授予的许可权先删除然后再提出要求更实用的步骤来获取新页面了-将要求用户选择其中的哪个他们要再次授予访问权限的当前页面集.
Currently, there does not seem to be any more practical procedure to get the new pages included, than removing the granted permission, and then asking for it again - upon which the user will be asked to chose which of their current set of pages they want to grant access to again.
要进行快速修复,可以使用Graph API Explorer-使用获取令牌"功能,删除授予的manage_pages
权限,然后再次提出要求.
For a quick fix, you can use Graph API Explorer - use the "get token" functionality, remove the granted manage_pages
permission, and then ask for it again.
对于由其他人管理自己页面的面向公众的应用程序,可能应在该应用程序中实施此步骤-必要时通过API删除权限 ,然后通过登录流程将其发送再次. (此时可能需要使用reauthenticate
参数.)
For a public facing app that has other people manage their own pages, probably such a step should be implemented within the app - remove the permission via API when necessary, then send them through the login flow again. (Might need to use the reauthenticate
parameter at this point.)