Platform Updates: Operation Developer Love

This week we introduced our Social Design Guidelines and unveiled some updates to the Developer App.

Blocking users from Pages via the Graph API

A much requested feature from developers who help Page owners manage their Pages is the ability to block users from Pages via the Graph API. From time to time a Page owner may want to block a user who is posting spammy or annoying content to their Page. This week we added this functionality to the Graph API. To block a user from a Page, simply issue an HTTP POST request to:

https://graph.facebook.com/PAGE_ID/blocked?uid=UID1,UID2

To see this list of users who have been blocked from a Page, simply issue an HTTP GET request to:

https://graph.facebook.com/PAGE_ID/blocked

To quickly check to see if a specific user is banned, just add their UID like so:

https://graph.facebook.com/PAGE_ID/blocked/USER_ID

And finally, to unblock a user, just issue an HTTP DELETE request to:

https://graph.facebook.com/PAGE_ID/blocked/USER_ID

For more information, check out the Graph API Page object documentation or the page_blocked_user FQL table documentation.

Breaking Change: FB.Canvas.getPageInfo now takes a callback

We’ve introduced a new implementation of FB.Canvas.getPageInfo. The old implementation caused a lot of confusion since it wasn’t clear how and when the values returned were updated. In 90 days, we will require that you include a callback with this function like so:

FB.Canvas.getPageInfo(
  function(info) {
    console.log(‘Width: ‘ + info.clientWidth +
                ‘ Height: ‘ + info.clientHeight);
  }
);

You can start using this new functionality today. Additionally, for the next 90 days, if you call the FB.Canvas.getPageInfo without a callback, it will continue to function as it has. This change should make it easier to accurately get information about canvas pages and will help speed up the experience for apps that use scrolling. For more information, check out the updated documentation or the Roadmap.

New per-app post privacy control

Last week we introduced the per-app post privacy control for users on the App Settings page. This setting defines the widest possible audience posts from your app can be made visible to and to which they will be made visible by default. You can still specify a more-restrictive privacy setting when publishing content but if you specify a less-restrictive privacy setting, this setting will be used.

Documentation activity for the last seven days

We updated the FQL documentation for the following tables:

• page_blocked_user

We updated the Page and User documentation in the Graph API and the FB.Canvas.getPageInfo documentation in the Javascript SDK to reflect the changes listed above.

88 docs under review

Fixing Bugs

Bugzilla activity for the past 7 days:

• 98 new bugs were reported
• 21 bugs were reproducible and accepted (after duplicates removed)
• 9 bugs were fixed (none of which were reported this week)
• As of today, there are 1,226 open bugs in Bugzilla (up 121 from last week)

Forum Activity

Developer Forum activity for the past 7 days:

• 198 New Topics Created
• 99 New Topics received a reply
• 25% received a reply from a community moderator or a Facebook employee