This happens when viewing admin/config/people/fbconnect/apperance

Comments

giorgio79’s picture

Status: Active » Closed (fixed)

Noticed this in the log entries
"Unable to load the required Facebook library, please check the README.txt for instructions on how to resolve this."
Investigating the library installation.

AnilM’s picture

Status: Closed (fixed) » Active

I'm running into the same problem (after updating to 7.x-2.x-dev today). I was running fb connect successfully prior to updating today.

I've got facebook-php-sdk installed under the libraries folder. Not sure why it's unable to find it. On my end, It's essentially an identical configuration to what I had prior to updating today. Is there some other different configuration in the latest update?

giorgio79’s picture

Status: Active » Closed (duplicate)

#1318296: Facebook PHP library not found This one has a more thorough issue description lets continue there.

cogniven’s picture

Would be cleaner if the code for fbconnect_user_profile where modified to be more helpfull:

function fbconnect_user_profile() {
  $user_profile = null;
  $client = facebook_client();
<strong>  if ($client) { // or include the getUser call inside try/catch to show more info about library call failure</strong>
    $user = $client->getUser();
    if ($user) {
      try {
        // Proceed knowing you have a logged in user who's authenticated.
        $user_profile = $client->api('/me');
      } catch (FacebookApiException $e) {
        $user_profile = null;
      }
    }
  }
  return $user_profile;
}
babusaheb.vikas’s picture

why is there

if ($client) { // or include the getUser call inside try/catch to show more info about library call failure

it just throws the error , and the above code is still not working.

leewoodman’s picture

Im am still getting this after the latest upgrade today

Hmmm i should have read the README.txt:

-- INSTALLATION --
1. Upload the 'fbconnect' and 'libraries' folder into your module directory and activate
the modules.

2. Upload facebook-php-sdk library (http://github.com/facebook/php-sdk/) into the libraries
folder so that it looks like 'sites/all/libraries/facebook-php-sdk/src/facebook.php'.

Lee

Itmman’s picture

Got the same error:

Fatal error: Call to a member function getUser() on a non-object in /fbconnect/fbconnect.module on line 421

downoaded last version of Libraries and uploaded facebook-php-sdk library (facebook-php-sdk-v3.1.1-25-g6c82b3f.zip) rinominated facebook-php-sdk

but still have this error

Konstantin Boyandin’s picture

Confirming. Using libraries 7.x-2.0-alpha2, the patch for fbconnect.module applied, but still the error

Call to a member function getUser() on a non-object in fbconnect.module

Any suggestions?

mrcool03988’s picture

Call to a member function getUser() on a non-object in /home/wm_demo2/demo2.webrmedia.com/sites/all/modules/fbconnect/fbconnect.module on line 421

This error is not even letting me enter my site. When I go to my site i.e demo2.webrmedia.com this error shows up.

Please help

ivanstegic’s picture

I was able to make this error go away by using the development version of the module.

Yuri’s picture

Priority: Normal » Critical
Status: Closed (duplicate) » Active

Using the latest dev version of this module, the fatal error still appears.
The libraries seem to load fine, at least no error that the library is not found. "Facebook PHP SDK library loaded" is regularly seen in the log. The admin pages do load, but any other public page gives this fatal error.
If you still think this issue is a duplicate, please indicate why, thanks.

wooody’s picture

Same problem with me too.. any way to fix that..?

Fatal error: Call to a member function getUser() on a non-object in /home/myweb/public_html/sites/all/modules/fbconnect/fbconnect.module on line 420

designotb’s picture

I am also having this exact same issue.

Downloaded the facebook-php-sdk today
Installed: Libraries 7.x-2.0-alpha2, FBConnect 7.x-2.0-beta3.

All modules and libraries downloaded Mar 24, 2012

jcisio’s picture

Status: Active » Fixed

This is fixed in the last dev snapshot. I'll roll out beta4 later today after a few more tests.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.