This week we announced how to implement flashHideCallback to support "wmode=window". We are also announcing the following changes:
We are now providing the ability of reading a user's subscribers and subscribees list via the Graph API. To access this information, your app is required to have the user_subscriptions
permission for the user, and friends_subscriptions
permission for their friends' info. Refer to the documentation for SubscribedTo and Subscribers for more details.
To access a user's subscribers list, issue an HTTP GET request to the subscribers
connection like the following:
https://graph.facebook.com/USER_ID/subscribers?access_token=...
Similarly, to access a user's subscribees list, issue an HTTP GET request to the subscribedto
connection.
https://graph.facebook.com/USER_ID/subscribedto?access_token=...
The following PHP example demonstrates how to read the subscribed-to list:
<?php
$app_id = 'YOUR_APP_ID';
$app_secret = 'YOUR_APP_SECRET';
$my_url = 'YOUR_URL';
$code = $_REQUEST["code"];
if (!$code) {
// user_subscriptions and friend_subscriptions permissions
// are required
$dialog_url = "http://www.facebook.com/dialog/oauth?client_id="
. $app_id . "&redirect_uri=" . urlencode($my_url)
. "&scope=user_subscriptions";
echo('<script>top.location.href="' . $dialog_url . '";</script>');
} else {
$token_url = "https://graph.facebook.com/oauth/access_token?client_id="
. $app_id . "&redirect_uri=" . urlencode($my_url)
. "&client_secret=" . $app_secret
. "&code=" . $code;
$access_token = file_get_contents($token_url);
// Get request for the subcribed-to list
$subscribedto_url =
"https://graph.facebook.com/me/subscribedto?"
. "access_token=".$access_token;
$subscribedto_resp_obj =
json_decode(file_get_contents($subscribedto_url), true);
// Parse the return value and get the array of people subscribed to.
// This is in returned in the data[] array
$subscribedto = $subscribedto_resp_obj['data'];
print_r($subscribedto);
}
?>
We improved search results on the Dev Site. Search now includes Technical Q&A from Stack Overflow and Bugs. You can also filter your results to only show the type of information you are looking for (e.g., blog posts, documentation, API reference, technical Q&A, bugs).
As announced on the blog on July 29, 2011 and on the Roadmap, to read or manage a user's notifications we now require the manage_notifications
permission. The "Require manage_notifications
" migration has now been removed per our 90-day breaking change policy. For more information, see the User object documentation.
Pages Insights Metrics Deprecations. We are in the process of deprecating some old Page Insights. We announced this in a number of forums, but failed to outline this change in our Platform Roadmap per our breaking change policy. Our apologies. You can find a full list of the Insights to be deprecated from the Insights documentation. These Insights will be completely removed from API on Feb 15th 2012. Please make all necessary updates as soon as possible so that you can transition smoothly.
Throwing an Exception for Invalid filter_key
. We will throw an exception if you try to query the stream FQL table with an invalid filter key. Currently if you call stream.get
with an invalid filter_key
value, the query silently fails, and with this change we will be throwing an exception. Refer to FQL stream documentation for details on using a filter_key
. This change will take effect on May 1st 2012.
Please refer to the Platform Roadmap for more info.
Activity on facebook.stackoverflow.com this week: