Need Help Debugging Drupal Errors
I'm experiencing some technical difficulties with Drupal, and I thought I'd document everything weird that's going on so that I could get some insight for how to fix it.
I beefed up my website with pictures in preparation for the Personal Democracy Forum, and suddenly one morning the interview page was filled with errors (screenshot) instead of what it should look like error-free (screenshot). (more details below)
I sent my Drupal helper Moshe Weitzman an emergency message, and he said:
- that error message indicates that the php security settings won't let the module access that file in the way that it wants to. you ought to send the error message to your web host to see if he can lower the security settings for your site. that would get rid of the error messages. if the web host refuses, you have to work with the module author.
My web administrator wrote back saying:
- I'm not sure what this means because I'm not a PHP expert. I'd need to know what exactly I need to change and then look into what problems are associated with it. My setting are the default setting...
There are lots of settings. I would need to know specifically which setting needs to be changed.
UPDATE: I asked Moshe for more details and he said to change these settings:
- http://us3.php.net/manual/en/ref.filesystem.php#ini.allow-url-fopen
allow_url_fopen is the setting
UPDATE: My web administrator changed these settings and I'm still having all of the same problems. I'm still receiving errors on the interview page with the inline module is enabled (screenshot) -- as well as all of the other problems listed below.
UPDATE: Moshe says that it looks like the inline module is doing something wrong, and that I need to contact the module developer to fix it. I'm going to track down the module author and pass along this web page. Moshe also has some ideas for some of the other module problems listed below.
UPDATE: The Inline problems are solved. The GD Toolkit install was finally solved the problem. The web server had to be reset, and then my php settings now displays the following GD configuration.
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
I've aggregated all of the Drupal anomalies and I'm posting screenshots and the error messages to below. I need to brainstorm ideas from the Drupal community in order to figure out exactly what I need to do eliminate these errors.
*** IMAGE ANOMOLIES ***
First of all, I'm seeing the following error message on the Administer Settings page: (screenshot)
The built-in GD image toolkit requires that the GD module for PHP be installed and configured properly. For more information see http://php.net/image.
UPDATE: Moshe says that my PHP settings on my web server need to have a GD section that looks something like this -- (screenshot). My web admin currently doesn't have this GD module installed or configured, and I need to figure out how to make this happen.
When the Inline module is turned on, the following error pair repeats for every inline image trying to be displayed on the page. This error behavior disappears after turning off the Inline module: (screenshot)
warning: getimagesize(): URL file-access is disabled in the server configuration in /www/echochamberproject/modules/inline/inline.module on line 131.
warning: getimagesize(http://www.echochamberproject.com/files/0plante.jpg): failed to open stream: no suitable wrapper could be found in /www/echochamberproject/modules/inline/inline.module on line 131.
The odd thing about these inline errors is that they came about AFTER exhibiting stable behavior. It was when I looked at the site from a laptop on the road when I started seeing this behavior.
UPDATE: These problems have been fixed with a proper GD toolkit install.
*** ERRORS FROM SPECIFIC MODULES ***
UPDATE: Moshe writes back about the following module errors saying:
- those 'table x does not exist' are likely happening because you or i omitted the database setup part of module activation. to install some modules, you have to run a sql script. you can do so by going to your admin page and clicking on 'database' and then 'run script' tab. see each module's readme file for install instructions.
I'm going to look into these module scripts to see what I need to run in order to fix the following errors.
- - - -
The following errors appear at the top of the screen when I enable the Flexinode module: (screenshot)
user error: Table 'drupal_echochamberproject.flexinode_type' doesn't exist
query: SELECT * FROM flexinode_type in /www/echochamberproject/includes/database.mysql.inc on line 66.
The following errors appear at the top of the screen when I enable the Trackback module: (screenshot)
user error: Table 'drupal_echochamberproject.trackback_received' doesn't exist
query: SELECT * FROM trackback_received WHERE nid = 170 AND status = 1 ORDER BY created DESC in /www/echochamberproject/includes/database.mysql.inc on line 66.
user error: Table 'drupal_echochamberproject.trackback_node' doesn't exist
query: SELECT * FROM trackback_node WHERE nid=170 in /www/echochamberproject/includes/database.mysql.inc on line 66.
The following errors appear at the top of the screen when I enable the Organic Groups (OG) module : (screenshot)
user error: Table 'drupal_echochamberproject.og_uid' doesn't exist
query: SELECT na.*, n.title, ou.mail_type FROM node_access na INNER JOIN node n ON na.nid = n.nid LEFT JOIN og_uid ou ON n.nid=ou.nid WHERE gid = 2 AND realm = 'og_uid' AND grant_view = 1 in /www/echochamberproject/includes/database.mysql.inc on line 66.
warning: Cannot modify header information - headers already sent by (output started at /www/echochamberproject/includes/common.inc:385) in /www/echochamberproject/includes/common.inc on line 192.
UPDATE: I'm also experiencing some problems with the img_assist module -- but only when it is enabled and after I submit a new node of content. The node's content is posted fine, but immediately after submitting it, I receive the following error message (screenshot)
query: SELECT na.*, n.title, ou.mail_type FROM node_access na INNER JOIN node n ON na.nid = n.nid LEFT JOIN og_uid ou ON n.nid=ou.nid WHERE gid = 2 AND realm = 'og_uid' AND grant_view = 1 in /www/echochamberproject/includes/database.mysql.inc on line 66.
warning: Cannot modify header information - headers already sent by (output started at /www/echochamberproject/includes/common.inc:385) in /www/echochamberproject/includes/common.inc on line 192.
*** OTHER PROBLEMS ***
I'm also having problems with the following modules that may or may not be related to those listed above:
* Blogroll doesn't appear -- I can't seem to configure it.
UPDATE: From the Blogroll Help:
- The blogroll block must be enabled and should contain a path.
If you are vewing a blog and are the owner you may click \"Edit.\"
Okay. I thought I specified a path. I'm not sure I've ever seen the \"Edit.\" anywhere. I'll look again.
- UPDATE: grohk writes, "blogroll has its edit control right on the block itself on a per user basis."
* The HTMLArea toolbar isn't showing up in the blog entries.
* I can't verify that the ping module is working -- Technorati doesn't seem to be getting updates from the Drupal initiated Ping-O-Matic route.
How can I set this up or debug this?
UPDATE: In the ping help file, I found this: "The ping feature requires crontab." I have no idea what crontab is.
- UPDATE: crontab is evidently something to do with a cron job.
grohk writes, "also, you need to setup a cron job to run the maintenance script http://www.echochamberproject.com/cron.php -- this is essential for Drupal to function properly. Ask you host to help you setup a cron job for this. Run it every six hours."
UPDATE: I'm also having trouble setting the site's time zone. I'm on Eastern Standard time which is the "-0400 option" on the settings page. I set the date settings to reflect this (screenshot), but it doesn't seem to be taking effect -- all of my blog entries and other pages that I create all add four hours to the time. What am I missing here?
I'd appreciate any insights.
- UPDATE: grohk writes, "Your host systems clock should be set to UTC in order for the site wide time to be correct, if it is not, then ignore the -0400 and pick the correct *time* instead. Actually, from reading you post, I think you need to pick -0800."
