I was trying to configure different settings for phpbb block but when clicking on configure link which is pointing to http://www.mysite.com/admin/build/block/configure/phpbb/0, I get a blank screen
Has anyone else ran into the same issue?
I was trying to configure different settings for phpbb block but when clicking on configure link which is pointing to http://www.mysite.com/admin/build/block/configure/phpbb/0, I get a blank screen
Has anyone else ran into the same issue?
Comments
Comment #1
arkepp commentedYeah, it has been up. Which link did you use to download the module?
Comment #2
mike15 commentedFound more details on this in Apache log file...
[Tue Jul 24 23:49:43 2007] [error] [client 192.168.10.1] PHP Fatal error: Cannot use string offset as an array in /htdocs/www.mysite.com/includes/form.inc on line 676, referer: http://www.mysite.com/admin/build/block
Comment #3
mike15 commentedOn the front page of the module, the Official release 5.x-1.1, downloaded today.
http://ftp.drupal.org/files/projects/phpbb-5.x-1.1.tar.gz
Comment #4
arkepp commentedThought I had messed up in CVS again, reverting sfurman's patch, but it appears to be in the release.
I cant reproduce it on my site right now, I will look at it tomorrow and maybe fix up the old module a bit.
Comment #5
arkepp commentedI still can't reproduce it, can you get to the phpBB settings page in the admin section?
The closest thing I can think of is if you give the wrong relative path to phpBB in phpBB settings and have disabled the display of errors.
Also please check the PHP or error logs of your webserver, should say there.
Comment #6
mike15 commentedThe phpBB settings page loads without any issues.
My settings are as follows:
Location of phpbb: forum/
Absolute path to phpbb: /htdocs/www.drupal.com/forum/
The only error I see is in apache_error.log file which I've provided earlier...
Is there a place where I can enable more debugging?
Comment #7
arkepp commentedIf the forum resides in http://www.drupal.com/forum , then the absolute path is /forum/
But there is no point in debugging this until you have resolved your other eAccellerator issue.