Package home | Report new bug | New search | Development Roadmap Status: Open | Feedback | All | Closed Since Version 0.2.14

Request #14351 Support for recent Facebook API changes
Submitted: 2008-07-14 22:00 UTC
From: mfonda Assigned: jeffhodsdon
Status: Closed Package: Services_Facebook (version 0.1.1)
PHP Version: 5.2.6 OS:
Roadmaps: (Not assigned)    

 [2008-07-14 22:00 UTC] mfonda (Matthew Fonda)
Description: ------------ Facebook is currently in the process of making a few updates to their API. For more information, see In addition to the link above, there is some more information provided on the Facebook Developers' Blog. In order for Services_Facebook to be used in the future, some methods need updating, and some new methods must be added. Currently, the new Facebook API can be accessed at To reflect the new changes, I'd like to propose that a new branch be created in SVN for changes relating to the new Facebook API, and once Facebook pushes their new changes live (should be within the next week or two), a new release of Services_Facebook can be made. Attached are several patches, more to come in the future.


 [2008-07-21 20:07 UTC] mfonda (Matthew Fonda)
Attached a new patch to support the following Auth API calls: * auth.promoteSession * auth.expireSession * auth.revokeAuthorization
 [2008-07-26 13:11 UTC] doconnor (Daniel O'Connor) seems a bit.. scary! Also, - $check = intval((string)$result->feed_publishStoryToUser_response_elt); - return ($check == 1); + return (intval($result->feed_publishStoryToUser_response_elt) == 1); ... is against the 'introduce an explaining var' pattern. (and in either case, the () are redundant) Aside from that, these changes look not too bad :) I don't suppose it's easy to provide a bit of test coverage around these new changes?
 [2008-07-26 20:32 UTC] jeffhodsdon (Jeff Hodsdon)
Thank you for your bug report. This issue has been fixed in the latest released version of the package, which you can download at Updates have been applied in 0.1.2. Services_Facebook_Common::$api now as a getter and setter if you would like to use any of the new beta api urls. Test coverage is hard for Facebook endpoints in general. At the moment there are tests for some endpoints that are able to be tested without much setup or prerequisites.