The following change will go into effect on December 5th, 2012.
We removed FBML in July of this year so any FBML code that was being used in the Static FBML Page app would have stopped working at that time. However, the Static FBML Page app is still able to render plain HTML.
On December 5th, we will remove the Static FBML Page app and any Static FBML tabs you had installed on your Page will disappear. To replace any Static FBML tabs you may be using, we recommend you either host your own content and create your own Page tab or search the web for "Static HTML Facebook Page Tab" to find a replacement.
The following change can be enabled/disabled using the "Remove offline_access permission" migration until December 5th when it will go into effect permanently for everyone.
offline_access permission is deprecated and will be removed December 5th, 2012 (originally scheduled for July 5th). Please see the Removal of
offline_access Permission doc for more details.
The following changes can all be enabled/disabled using the "December 2012 Breaking Changes" migration until December 5th when they will go into effect permanently for everyone.
We will only allow authorization codes to be exchanged for access tokens once and will require that they be exchanged for an access token within 10 minutes of their creation. This is in line with the OAuth 2.0 Spec which from the start has stated that "authorization codes MUST be short lived and single use". For more information, check out our Authentication documentation.
We will begin returning full Custom Open Graph objects (including custom-defined fields) via the Graph API when requesting them using the
id parameter (e.g.
https://graph.facebook.com/?id=YOUR_URL). Currently we only return the
shares fields for these objects.
As some Page descriptions contain HTML (e.g.
https://graph.facebook.com/107850102581157), we will begin stripping HTML tags from the
description column/field of the [Page FQL table] and the [Page Graph API object] so as to not require you to parse/render HTML when using a Page description.
We will add a
description_html column/field that will contain the description including the HTML tags (as
description used to contain). The
description_html Graph API field will not be returned by default. It will have to be explicitly requested by including a
?fields=description_html parameter in your Graph API