The following changes can be enabled/disabled using the "July 2013 Breaking Changes" migration until July 10th when they will go into effect permanently for everyone.
As announced here, this migration enables the updated comment APIs.
href
parameterSocial plugins, such as the Like Box and Like Button, will require an absolute URL in the 'href' parameter.
Query [stream_filter] table for a set of valid stream filters. The [stream] table will throw an exception if called with an invalid 'filter_key' option.
publish_checkins
permissionsPublishing a Checkin object is deprecated in favor of creating an Open Graph story with a location attached. You can also create a Post with a location attached using the publish_steam
extended permission.
page_id
changeWe are renaming page_id
to target_id
for the [Checkin] table.
version
field for GroupsWe introduced version
field to indicate whether the group was created prior to launch of the current groups product in October 2010. We are removing this field as all Groups on Facebook are now the same version. This impacts both Group Graph API and [Group FQL Table].
images
field in [photos] and [photo_src] table will no longer return image sizes larger than the original uploaded version of the photo.
comments
field from stream
FQL tableWe are deprecating the comments
field from stream
FQL table. Please select the comment_info
column to fetch the can_comment
and comment_count
fields (formerly called can_post
and count
), and use the comment table directly to retrieve the list of comments.
xid
, reply_xid
, username
and comments
from comment
FQL tableWe are removing the fields on the FQL comment
table that were used exclusively for legacy Comments Plugins -- xid
, reply_xid
, username
and comments
. We now treat comments the same across plugins and within Facebook. Please query for comment replies left on the plugin the same way as you would for other comments.
count
from comments
Graph API connectionWe are removing the undocumented count
field on the comments
connection in the Graph API. Please request {id}/comments?summary=true
explicitly if you would like the summary field which contains the count (now called total_count
)
The following changes will go into effect on July 10, 2013.
We are updating the Creative Spec parameter app_platform_type
to mobile_store
. The possible values for mobile_store
are now "itunes", "itunes_ipad", and "google_play".
We are deprecating the use of 'tracking_pixel_id' when specifying the desire to track a conversion pixel in an ad. You should instead specify the pixel in the newly launched tracking_specs
field.
We are also deprecating the use of conversion specs in bid types that are not optimized for actions (e.g. CPM, CPC, and oCPM when no bid value is placed on actions). You should instead use tracking_specs
to track conversions for these bid types.
We have changed the targeting spec parameter excluded_user_adclusters
to be excluded_custom_audiences
. Additionally, the endpoint to create and retrieve your custom audiences is now: https://graph.facebook.com/(act_adaccountid)/customaudiences
.
App access tokens will be required for accessing the [link_stat] FQL table. App access tokens will also be required for retrieving data from Graph API endpoint for link stats, ie: http://graph.facebook.com/?id=http://example.com
.
User access tokens will be required for all search Graph API calls except Posts, Places and Pages. App access tokens may also be used for Post search Graph API calls. Places and Pages search Graph API calls will still require an App access token. Search for Applications will no longer be supported.
As announced in March, any apps that previously used custom actions to represent this type of sharing will need to move common actions by July 10, 2013.
page_friends_of_fans
metricWe are removing the metric: page_friends_of_fans
from the Insights Dashboard and the Insights API.