Cannot modify header information

[dojo]

Sometimes you install the Nuke CMS and when you try to open the forums you get a very ugly stream of errors. The forums are functional, but still, you don't want all people to know you've got such nasty code problems, not to mention it can lead to security problems since the code displays much of your "sensitive" information.

Here is the code and how we fix it.

Warning: Cannot modify header information - headers already sent by (output started at /usr/local/apache2/htdocs/sitename/themes/DeepBlue/theme.php:85) in /usr/local/apache2/htdocs/sitename/includes/sessions.php on line 222

Warning: Cannot modify header information - headers already sent by (output started at /usr/local/apache2/htdocs/sitename/themes/DeepBlue/theme.php:85) in /usr/local/apache2/htdocs/sitename/includes/sessions.php on line 223

Warning: Cannot modify header information - headers already sent by (output started at /usr/local/apache2/htdocs/sitename/themes/DeepBlue/theme.php:85) in /usr/local/apache2/htdocs/sitename/includes/page_header.php on line 488

Warning: Cannot modify header information - headers already sent by (output started at /usr/local/apache2/htdocs/sitename/themes/DeepBlue/theme.php:85) in /usr/local/apache2/htdocs/sitename/includes/page_header.php on line 494

Warning: Cannot modify header information - headers already sent by (output started at /usr/local/apache2/htdocs/sitename/themes/DeepBlue/theme.php:85) in /usr/local/apache2/htdocs/sitename/includes/page_header.php on line 495

------

And now the step by step errors and solution.

Warning: Cannot modify header information - headers already sent by (output started at /usr/local/apache2/htdocs/sitename/themes/DeepBlue/theme.php:85) in /usr/local/apache2/htdocs/sitename/includes/sessions.php on line 222

sessions.php on line 222 - go to sessions.php and open it with your editor. EXACTLY at the line 222 just put // in front of the line =>
// and the rest of the code. That turns it in a comment.

Warning: Cannot modify header information - headers already sent by (output started at /usr/local/apache2/htdocs/sitename/themes/DeepBlue/theme.php:85) in /usr/local/apache2/htdocs/sitename/includes/sessions.php on line 223

line 223 in sessions.php same thing: // in front of the code.

Warning: Cannot modify header information - headers already sent by (output started at /usr/local/apache2/htdocs/sitename/themes/DeepBlue/theme.php:85) in /usr/local/apache2/htdocs/sitename/includes/page_header.php on line 488

page_header.php on line 488 put // in front

Warning: Cannot modify header information - headers already sent by (output started at /usr/local/apache2/htdocs/sitename/themes/DeepBlue/theme.php:85) in /usr/local/apache2/htdocs/sitename/includes/page_header.php on line 494

page_header.php on line 488 same...

Warning: Cannot modify header information - headers already sent by (output started at /usr/local/apache2/htdocs/sitename/themes/DeepBlue/theme.php:85) in /usr/local/apache2/htdocs/sitename/includes/pag[color=red]e_header.php on line 495
Same ...

After you do so, backup the previous files (so that you coud change them if you did something wrong) and upload the changed files in their place.

When you post on the forums you'll get something similar, just go and add // in front of the code.

Some people use @ in front of the lines with problems, so you could do this too. We can tell you // has worked for us, since we haven't tried the other way.

Hope that helped.

[ezrashem]

I also experience that one Paolo and until now I wonder why it happens.
Maybe there are something missing.