Starting June 30, 2010, your Facebook application will only be able to read the publically available information of a user’s profile by default, the way data read permissions are granted in the platform. While the changes are broad in scope, none of them impact backwards compatibility: all of your existing code will continue to work.
The most important changes are:
- Graph API
- Data Permissions
- OAuth 2.0
- New SDKs
- Facebook Connect Branding
To get access to user’s profile information, your facebook application must explicitly request all of the data it needs to function. For instance, if you want to incorporate a user’s events into your application, you would request the user_events extended permission.During the authentication process, the user is presented with a UI in which the user can authorize your application to access that specific part of her profile.
Following is the complete list of extended permissions for Graph API:
publish_stream, create_event, rsvp_event, sms, offline_access, manage_pages, email, read_insights, read_stream, read_mailbox, ads_management, xmpp_login, user_about_me, user_activities, user_birthday, user_education_history, user_events, user_groups, user_hometown, user_interests, user_likes, user_location, user_notes, user_online_presence, user_photo_video_tags, user_photos, user_relationships, user_religion_politics, user_status, user_videos, user_website, user_work_history, read_friendlists, read_requests.
To upgrade your require_login() authentication to Graph API authorization, please check my earlier post for how to authenticate using Facebook Graph API and simply add any extended permission that you may need in your app. Go the function “RequestforPermission” in that post and add your permissions in the