Faux Facebook Connect allows Facebook users to comment on WordPress. MU compatible
// December 21st, 2009 // wordpress
I just released an initial version of a mainly JavaScript based Facebook connect plugin for WordPress to allow Facebook users to comment on a WordPress powered blog.
The script is build in a way that it can be activated also out of a theme context and does not perform any database alterations or manipulations on user tables. It simply uses the Facebook data to prefill the comment form and hides it once a Facebook user is logged in.
The initial idea for this procedure was taken from Beau Lebens and wrapped up in an easy to use WordPress plugin.
For more information check out the plugin page at: http://wordpress.org/extend/plugins/faux-facebook-connect/
Feedback Welcome!





I’m getting this error: atal error: Call to undefined function check_admin_referer() in / /wp-content/plugins/faux-facebook-connect/faux-facebook-connect.php on line 121
I tried installing on both WPMU and regular WP. What do you make of that?
never ran into this one. Which version of WordPress are you using and on which action/url do you get this error?
I get it when trying to acquire the Template Bundle ID on WPMU 2.8.6 as well as on WP 2.8.6.
That’s odd. I tested with exactly this version. Can you try deactivating/deleting and reinstalling the plugin.
Just reinstalled. Same error. I thought it might be something wrong with my WPMU install but I tried to activate the plugin on WP single user as well and get the same error. Could it be that one of the files is missing from the plugin that I downloaded?
That is not very likely. This error would usually appear if the backend_init() function is not called in a wp-admin context. Otherwise this function should be loaded and available. Could you send me a list of your installed plugins so I can test for any incompatibility.
I get the same thing when I click the save changes button this is the error that I get,
Fatal error: Call to undefined function check_admin_referer() in /home/thess/public_html/wp-content/plugins/faux-facebook-connect/faux-facebook-connect.php on line 121
[...] about it is that it doesn’t change anything in the database or add any users. Plugin author Thorsten Ott credits Beau Lebens for the initial idea, and you can visit his site for a more technical [...]
Ok then it must be one of my plugins. I will attempt to deactivate them one by one and test it out when I get a chance. Thank you!
I’m a little confused as to how to implement this in WPMU.
From what I understand I just add
add_filter( ‘fauxfb_plugin_url’, ‘fauxfb_plugin_url’ );
function fauxfb_plugin_url() {
return get_bloginfo(‘template_url’) . ‘/plugins/faux-facebook-connect’;
}
to the bottom of my functions.php file and then call on it by adding this line to the same function.php?
require_once( ‘plugins/faux-facebook-connect/faux-facebook-connect.php’ );
Is that correct?
You can generally install it like any other plugin on WPMU, but there is an option to alter it as you described in order to put the plugin in a theme context.
just commented this function check_admin_referer() and it’s works.
What it’s Template Bundle ID ?
The template bundle ID is something layout representation link that’s provided by Facebook. See http://dentedreality.com.au/2008/12/implementing-facebook-connect-on-wordpress-in-reality/ where the manual process is described. This should clear things up a little.
thanks thor.
How to change style (ex: dotted border) and resize the profile pic ?
thanks again.
That would be #fb-user if you want to style it via css. You can check the CSS file fauxfb_style.css for some basics and other than that I would recommend FireBug to examine the classes/ids of the created elements and style them via CSS
Faux Facebook Allows Facebook users to comment on wordpress, without need create user on wordpress. http://bit.ly/8v4oV4
I have exactly the same problem as Sarah.
Clean install of Wordpress MU, using the “home theme” (for now), no other plugins installed yet.
That’s really weird. Do you get the error message in the frontend or also in the admin backend?
Hi,
I have the the check_admin_referer() problem too. It happens when I click on save changes in the settings panel. I use WP 2.8.6 with the k2 theme.
I just commented the line calling the function and it’s fine.
I’m getting Fatal error: Call to undefined function check_admin_referer() on line 121
I have the latest version of Wordpress 2.9
By the way it’s in the admin backend when I try to save changes to the plugin
I followed Imbads suggestion and it works if you comment it out. The only problem is with the avatar, it scales to fit my avatar size on the template rather than just cropping nicely like on other blogs
Sorry for the comment spam.
Any idea how to change the ‘connect’ button? I wanted to use the longer version
Templates bundles developer feature has been depreciated by Facebook.
http://developers.facebook.com/tools.php?feed
“Facebook will deprecate template bundles and their related API calls December 20, 2009.
Please start using stream attachments with stream.publish, FB.Connect.streamPublish, and Facebook.streamPublish instead.”
Thanks for pointing me to this. I will incorporate this in one of the next releases.
I’m having the same issues as Murat. Had to comment out the check_admin_referer() function (I’m on WP 2.9).
Also having major issues with the layout of the avatars:
http://mattfarley.net/fbconnect.jpg (the ones on the right are Gravatars, on the left are facebook).
Lastly — is it normal that the FB avatars don’t come through until you actually do a FBConnect session? (otherwise you just see fb icons/placeholders)
Thanks for this plugin!
Update: I fixed the display issues by editing my theme’s css (and also had to edit a bit of the faux-facebook css)
Still wondering if it’s normal that FB avatars only display if you’re logged into FB. It would be nice if they’d always display even if you’re not a FB member or logged in.
Facebook avatars only showing up on being logged in seems a little weird. I will look into this and fix this in one of the next versions if needed.
Thanks to all for pointing me to this and sending over the feedback. I am currently trying to evaluate under which conditions this error occurs and why it did not occur for me yet. This will be the main subject of the next release which I hope to fire out in the coming week.