I am experiencing difficulties with this plug-in when I use other plug-ins that also use FB's API.
As you can see here the author of that plug-in states that it's the 'fault' of the official plug-in. So, can this compatibility issue get fixed?
+1 for this. Rewriting all plugins to use the
Facebook_WP class instead of the plain
can we create 2 different APIs for 2 Facebook plugins?
Also, one of the reasons we're using Facebook_WP is so we avoid namespace collisions.
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.
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
As it told, base_facebook.php doesn't have static member
But I see Facebook-php-sdk on github, base_facebook.php has that member.
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?
This topic has been closed to new replies.