Closed (won't fix)
Project:
Drupal for Facebook
Version:
5.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
11 Nov 2007 at 00:52 UTC
Updated:
17 Jan 2012 at 12:53 UTC
The comment in fb.module says the variable was introduced to avoid exceptions in PHP5.
However the cure is worse than the disease. I spent quite a bit of time trying to figure out why $fb->api_client->fql_query fails and turns out PHP4 API is the cause. Setting the variable to FALSE solves the problem.
Maybe the issue is in using outdated Facebook API libraries? They keep changing and we need to test the module against the latest and mark the date on which client API libs were downloaded.
Comments
Comment #1
Dave Cohen commentedThe problem is using PHP5 APIs leads to uncaught exceptions. My plan is to make the modules require PHP5 in Drupal 6, where (I believe) there will be better support for it.
Are you saying you can't call fql_query because of this?
Comment #2
dkruglyak commentedCorrect, fql_query fails and Apache log indicates the reason is that some function not found (sorry I have not kept it).
Perhaps your exceptions are not related to D4F ?
Comment #3
Letharion commentedSince Drupal 5 is no longer supported, I'm taking the liberty to close all FB D5 issues. Issues that haven't moved since D5 are unlikely to still be valid.