+1 for this. Rewriting all plugins to use the Facebook_WP
class instead of the plain Facebook
class in the PHP SDK is a royal PITA.
can we create 2 different APIs for 2 Facebook plugins?
Hi, Matt.
I’m developper of a plugin which use Facebook’s php-sdk 3.1.1(current latest) and found that Facebook plugin breaks my plugin.
http://wordpress.org/extend/plugins/gianism/
I got an error which tells Fatal error: Access to undeclared static property: BaseFacebook::$CURL_OPTS in /path/to/facebook/includes/facebook-php-sdk/base_facebook.php on line 880
on $facebook->makeRequest()
.
As it told, base_facebook.php doesn’t have static member $CURL_OPTS
.
But I see Facebook-php-sdk on github, base_facebook.php has that member.
https://github.com/facebook/facebook-php-sdk/blob/master/src/base_facebook.php
It seems that Facebook plugin uses customized base_facebook.php. Please tell me what to do for coexistence.
So if I’m using a plug in like digg digg (for floating sharers) or jetpack (for workdpress stats) even though I’m not using their facebook button, would I have issues?
It looks like the plugin is duplicating code. What can I do? I can’t get rid of the other ones.
Matt, what exactly do you mean by “Followed up in”?
I’m wondering the same question. Is there a way to make Facebook play nice with other plug-ins? Would other FB plugin developers update their plug-in to make them compatible with the official plugin?