Facebook API 2.3的新publish_pages权限 - 我需要吗？ [英] Facebook API 2.3's new publish_pages permission - do I need it?
问题描述
我的Facebook应用程序允许我们的CMS用户通过我们的CMS，摆在页面上。
我们已经（通过登录审核流程）授予了 manage_pages 和 publish_actions 权限。
API更改日志指出：
publish_pages权限 - 此新权限需要作为页面发布。以前需要publish_actions。在v2.3之前授予manage_pages和publish_actions的人已被自动授予publish_pages。如果有人通过v2.3登录，除了manage_pages之外，还需要明确地请求publish_pages。
我们还没有被授予publish_pages权限自动。
对于页面开发者，我们增加了通过实时更新（RTU）在页面上提供更多内容的功能。现在需要一个新的登录权限publish_pages，用于代表Pages发布应用程序;以前，这需要publish_actions。
所以这听起来像我们升级到使用API 2.3，我们的服务将不再工作，因为我们还没有被授予publish_pages。
文档说明：
具有publish_actions权限的用户访问令牌可用于发布新的代表该人的职位。帖子将以用户的声音出现。
可以使用publish_pages权限的页面访问令牌代表该页面发布新帖子。帖子将出现在页面的声音中。
我们要发布在页面，正如我们现在所做的那样。
因此，我打开了一个新的登录审核请求，并总结了上述所有内容，引用他们的更改日志。 Facebook的回应是这样的：
您不需要publish_pages权限，因为您已经授予了publish_actions和manage_pages权限。 Publish_pages是一个新功能，允许应用程序发布到受管理的Facebook粉丝页面，但您之前授予的权限已包含此功能。
只是我，还是那个回应与他们写的其他一切冲突呢？
所以我的问题是简单的，我们是否需要这个新的权限，而不是自动将它们授予我们？
很明显，Facebook的支持响应在某种程度上是错误的。
如果你想以页面的形式发布用户 manage_pages 和 publish_actions 发布权限可以通过发布操作。
如果你想要发布代表您还需要的页面 publish_pages 权限，没有这个所有v2.3 api调用将返回 OAuth错误。
可能还有其他权限来管理您的网页
I'm quite confused about Facebook's new publish_pages permission.
My Facebook app allows our CMS users to post to their Facebook pages via our CMS, posing as the page. We have been granted (via the login review process) the manage_pages and publish_actions permissions.
The API change log states this:
publish_pages Permission - This new permission is required to publish as a Page. Previously publish_actions was required. People who granted manage_pages and publish_actions before v2.3 have automatically been granted publish_pages. If anyone logs in via v2.3, you'll need to request publish_pages explicitly in addition to manage_pages.
We have not been granted the publish_pages permission automatically.
The blog post here states:
For Page developers, we've added the ability to deliver more content on a Page via real-time updates (RTUs). A new Login permission, publish_pages , is now required for apps to publish on behalf of Pages; previously, this required publish_actions.
So it sounds to me like if we upgrade to use API 2.3, our service will no longer work, because we haven't been granted publish_pages.
The documentation states this:
A user access token with publish_actions permission can be used to publish new posts on behalf of that person. Posts will appear in the voice of the user.
A page access token with publish_pages permission can be used to publish new posts on behalf of that page. Posts will appear in the voice of the page.
We do want to post in the voice of the page, as we do currently.
Therefore I opened a new login review request and summarised all of the above, quoting their changelog. Facebook's response was this:
You don't need the publish_pages permission because you already have the publish_actions and manage_pages permissions granted. Publish_pages is a new feature that allows an app to publish to a managed Facebook fan page, but your previously granted permissions contain this functionality already.
Is it just me, or does that response conflict with everything else they've written?
So my question is simply, do we need this new permission going forward or not, and have they wrongly not automatically granted it to us?
Well apparently Facebook's supports response is in some manner wrong.
If you want to post on Page on behalf of the user manage_pages and publish_actions publish permissions are passable for post action.
If you want to post on behalf of the page you also need publish_pages permission, without this all v2.3 api calls will return OAuth Error. There might be other privileges for managing your pages under this permission i don't know
这篇关于Facebook API 2.3的新publish_pages权限 - 我需要吗？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
