In the spirit of openness and transparency and to adhere to our
Breaking Change Policy,
we publish this roadmap to help developers plan for changes that may
require code modifications. Like all roadmaps, it may shift slightly,
but we will share insight into what is happening as details become
available. We encourage developers to
subscribe to our
blog, where we announce rollout plans and timing.
March 1, 2012
Enhanced Auth Dialog - In progress
The enhanced auth dialog will launch to 5% of an app’s incoming new
users March 9, and roll out more broadly in the following weeks. You can
opt to accelerate this roll out to 100% of your incoming new users by
enabling "Enhanced Auth Dialog" in the advanced settings within the
Developer App. Asking for the publish_actions permission will also turn on the new dialog for 100% of new users, for apps that are not categorized as games. See this blog post for more information.
July 5, 2012
The following changes will go into effect on July 5, 2012:
Removing FB.Canvas.setAutoResize - Originally scheduled for January 1, 2011
We have renamed FB.Canvas.setAutoResize to FB.Canvas.setAutoGrow so
that the method more accurately represents its function.
FB.Canvas.setAutoResize will stop working on July 5th. We will completely delete the function on August 1st.
Event GETs from Graph API/FQL Will Require an Access Token
All calls to get events from the Graph API or FQL will now require an access token to be used.
The following changes can all be enabled/disabled using their specified
migrations until July 5th when they will go into effect permanently for everyone:
Removal of FBML
FBML apps will no longer work on Platform. All FBML endpoints will be removed and the "FBML Removal" migration added June 6th will be removed.
Updating Page Hours Property
The hours property of Pages will return times in the format HH:MM (e.g. "14:23") rather than the old format (a Unix time). This change can be enabled/disabled using the "Page Hours Format" migration until July 5th when it will go into effect permanently for everyone.
Batch API Exception Format
Errors from the Batch API will return errors in a new format. Previously, errors would take the format:
{"error_code": "", "error_description": ""}
With this change, they will now be formatted in-line like the rest of the Graph API:
{"error": {"message": "", "type": ""}}
This change can be enabled/disabled using the "Graph Batch API Exceptions Format" migration until July 5th when it will go into effect permanently for everyone.
Removing Timezone From Event Times
We have had a migration titled "Timezone-less Events" out for a while now which removes timezones from event
start and end times. This migration was originally created because in
the past, events have been intended to be created with start and end
times that are specific to the location of the event so including a
timezone in the API simply led to confusion. Until now, this migration
never had a date set for when it would go into full effect. That date is
now July 5th. This change can be enabled/disabled using the
"Timezone-less Events" migration.
Since this migration was originally created, we have added a timezone field to events which indicates the name of the timezone (as defined here) where the event is expected to happen. FYI, developers reading time in ISO 8601
should be supporting the full standard when reading event times. Most
events return local times (no GMT offset), but in the future events
likely will return other formats (namely date-only and precise).
The following changes can all be enabled/disabled using the "July 2012 Breaking Changes"
migration until July 5th when they will go into effect permanently for everyone:
Removing display=wap Dialogs
The wap dialog display mode will be removed.
Removing Some Event FQL Object Fields
We will be removing the following legacy fields from the event FQL object.
show_in_searchshow_wallshow_photosshow_videosshow_postsnidtaglineevent_typeevent_subtype
Coordinate-less Tags
Tags previously could only exist on photos and always included x,y coordinates. On Facebook it is now possible to tag people in photos and statuses with no coordinates (example). These people show up as being "with" the actor. The potential breaking change is that it will be possible for the tags parameter of any photo object to return objects with no x or y parameters.
Removing Bookmark.Add and Profile.AddTab Dialogs
We will be removing the bookmark.add and profile.addtab dialogs from the Javascript SDK.
These dialogs already don't do anything as the concepts of manually
adding bookmarks and profile tabs have already been removed.
Moving Type Property Into Metadata Array
When querying the Graph API with a metadata=1 parameter, we append a metadata array and a type property to the response. We will be moving the type property into the metadata array.
August 1, 2012
The following changes will go into effect on August 1st, 2012:
Deleting FB.Canvas.setAutoResize - Originally scheduled for January 1, 2011
We have renamed FB.Canvas.setAutoResize to FB.Canvas.setAutoGrow so that the method more accurately represents its function. FB.Canvas.setAutoResize will stop working on July 5th. We will completely delete the function on August 1st (if you call it you will get an "undefined function" error).
Page Post GETs from Graph API/FQL Will Require an Access Token
All calls to GET Page posts from the Graph API or FQL will now require an access token to be used.
The following changes can all be enabled/disabled using the "August 2012 Breaking Changes"
migration until August 1st when they will go into effect permanently for everyone:
Removing prompt_permissions.php and prompt_feed.php
We will be removing a very old version of the feed dialog
(/connect/prompt_feed.php) as well as a very old version of the auth
dialog (/connect/prompt_permissions(s).php). If you are one of the very
few developers still using these legacy endpoints, you should upgrade to
the current Feed Dialog and/or OAuth Dialog.
Removing Add To Timeline Plugin
We will be removing the Add to Timeline plugin. If you are embedding the Add to Timeline plugin, we will render the Login Button in its place with the publish_actions permission automatically added to the scope parameter.
September 5, 2012
The following changes can all be enabled/disabled using the "September 2012 Breaking Changes"
migration until September 5th when they will go into effect permanently for everyone:
Renaming 'likes' property of Comments and 'votes' property of QuestionOptions
We will be renaming the likes property of the Comment object to like_count and the votes property of the QuestionOption to vote_count.
Minor change to admin.getAppProperties call
When making an admin.getAppProperties call, we will now return an empty iOS Bundle ID as [] instead of [""].
Returning actual size in photo_src table
We will start returning the actual size, height, and width of photos in the photo_src FQL table instead of the dimensions of the bounding box.
October 3, 2012
Removing Bookmark URL - Originally scheduled for December 1, 2011
As mentioned on the blog,
this optional field was originally created to help developers track
user referrals from app bookmarks. We now pass a ref parameter to let
you know that the user is coming from a bookmark (i.e. ref=bookmarks).
As a result, we removed Bookmark URL. While many developers left this
field blank (defaulting to the Canvas URL), it recently came to our
attention that some developers were using this field to redirect to
Pages with the Page Tab app installed. We will restore the Bookmark URL
to the Advanced tab under Canvas Settings for 90 days. This gives you
time to edit the field before it will be removed from the Developer App.
To give you the most flexibility, we recommend that you delete the
Bookmark URL field and instead detect the ref=bookmarks parameter when
the user visits your app and take the appropriate action (either
redirect to your Page Tab app on a Page or show the user something
different).
Built-in Like/Follow Action Required
We will stop allowing the use of Custom Open Graph "like" and "follow" actions now that there are built-in "like" and built-in "follow"
actions. Please convert any custom "like" or "follow" actions you may
have created to instead use the built-in "like" or "follow" actions.
Removing Live Stream plugin
The Live Stream plugin will be removed on October 3, 2012. We recommend using the Comments Box
plugin instead. Please migrate your app as soon as possible. On
September 5th, if your app is still using the Live Stream plugin, we
will render the Comments Box plugin in its place. While it offers
similar functionality, there are a few functional differences. Please
see the Live Stream plugin documentation for more info.
offline_access Permission Removal
The offline_access permission
is deprecated and will be removed October 3rd, 2012 (originally
scheduled for July 5th). Until then, you can turn this change on or off
using the "Remove offline_access permission" migration until October 3, 2012 when it will be permanently "enabled" for all apps. Please see the Removal of offline_access Permission doc for more details.
No comments:
Post a Comment