Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
There are no error messages in dblog, nor on the screen. I'm guessing that somehow the page data to be rendered is wiped out. I have only fb.module and fb_devel.module enabled. The "Like" button is appearing, so that indicates that the library (2.1.2) is okay.
Usually a WSOD is some fatal PHP error or a seg fault. Try looking in apache error logs, or system logs. I'm just saying that a WSOD almost always has an error message, you just have to find it.
Are you saying the status page works fine when fb.module and fb.devel module are disabled, but WSOD when they are enabled?
I didn't mark this fixed right away because I figured there might be a way to catch the error, but no one's posted a stack trace, and now I want to clean the issue queue.
Comments
Comment #1
Dave Cohen commentedI'd like to help, but can't without some error message.
Comment #2
nancydruThere are no error messages in dblog, nor on the screen. I'm guessing that somehow the page data to be rendered is wiped out. I have only fb.module and fb_devel.module enabled. The "Like" button is appearing, so that indicates that the library (2.1.2) is okay.
Comment #3
Dave Cohen commentedUsually a WSOD is some fatal PHP error or a seg fault. Try looking in apache error logs, or system logs. I'm just saying that a WSOD almost always has an error message, you just have to find it.
Are you saying the status page works fine when fb.module and fb.devel module are disabled, but WSOD when they are enabled?
Comment #4
nancydruThat is correct. Actually, the status page worked until I installed the library (i.e., with fb api enabled).
Comment #5
nancydruAh ha! Apache: PHP Fatal error: Uncaught exception 'Exception' with message 'Facebook needs the CURL PHP extension.'
So now to my Linux guru...
Comment #6
Dave Cohen commentedYes that's your problem.
Before you fix it, can you give the stack trace of the exception? Perhaps a try..catch can fix the WSOD.
Comment #7
nancydruHow do I get that?
Comment #8
Dave Cohen commentedIn my devel environment, uncaught exceptions result in a stack trace in the log. I think it's because I have xdebug set up.
If I find time, I'll try to track this down. Until then, I'll leave the issue open in case anyone else runs into it.
Comment #9
zatarain21 commentedSame problem and same solution
I supossed that I have installed php curl
A easy way to install is:
sudo apt-get install php5-curl
Restart apache.
P.D. I am very excited about this module and its possibilities thanks Dave for share your talent.
Comment #10
sandino commented@zatarain21
Thanks a lot!
You saved an hour of my time :)
Comment #11
Dave Cohen commentedI didn't mark this fixed right away because I figured there might be a way to catch the error, but no one's posted a stack trace, and now I want to clean the issue queue.