By kpm on

Can anyone point me in the proper direction here... Sites were all working fine, I added a Image modules on the 18th and the site was still fine, but then a few days latter I noticed it started throwing the header info warning. I asked the web host if any changes to the php.ini file had occured since that seemed to win the most popular cause for this in Google quieries... They responded saying the htaccess file was changed on the 18th, but I never changed it directly, I was wondering if the modules actually changed the htaccess file and if anyone could point me to the proper solution for fixing it? I disabled the modules that were installed, but we still getting the warnings...
Thanks

⋅ Categories: Drupal 5.x

Comments

vm’s picture

vm commented

The Gallery.module adds some code to the .htaccess file (There may be others) however, you should take a look @ http://drupal.org/node/1424 which explains where headers already sent errors can come from with relation to Drupal.

xjessie007’s picture

xjessie007 commented

I had a problem with the "headers already sent" too at my www.Maxi-Pedia.com website. In my case, it was caused by a blank line at the beginning of common.inc. Drupal or more likely PHP seem to have problems with extra spaces here and there.

Check all your *.inc files to make sure you do not have closing ?> in any of them. Closing ?> is not needed in your *.inc files. Check all your *.php files to make sure you do not have blank lines at the beginning or at the end.

If the error message indicates that this is caused by some module, disable your modules one by one to find out which one causes this. It seems like this started happening after you added the image module? Then disable and enable it and experiment. Take a look inside your image.module file and look for blank lines.

This can also be caused by UTF-8. If you have your website coded in ASCII and are saving your php files as UTF-8, it can cause this message. If your website and DB are UTF-8, you should be ok with saving php files as UTF-8 though.

I heard this could also be related to blocks that do not have a title specified. Edit your blocks in Admin / Blocks.

Btw, this error message is related to output_buffering on/off in your php.ini. If you have output_buffering set to some cache, the server will allow to send headers with delay (or to modify them shortly after they are sent), and this error will not be tripped. But if you set output_buffering to 0 or not at all, then headers can be sent at only one moment, and if you have some bad code, it will trip this error message.

---------------
Everything you ever needed to know: www.Maxi-Pedia.com