By wbhart on

Several days ago I noticed that my archive only went from 2000 to 2005.
So I followed the instructions at http://drupal.org/node/44765

This seemed to fix the archive problem, but then when I tried to login under the only two accounts I have (an admin account and a test account) I get this message...

"warning: Cannot modify header information - headers already sent by (output started at /home/intercul/public_html/cms/modules/archive.module:1) in /home/intercul/public_html/cms/includes/common.inc on line 192."

I changed my archive module back to the original form, but still be the above message when logging in.

Any suggestions?

⋅ Categories: Drupal 4.6.x

Comments

wbhart’s picture

wbhart commented

Forgot to mention that I'm using 4.6.5.

heine’s picture

heine commented

You need to re-save archive.module; make sure there's no whitespace before the opening <?php-tag. Before you save, make sure the editor does NOT save the UTF-8 Byte Order Mark.
--
The Manual | Troubleshooting FAQ | Tips for posting | Make Backups! | Consider creating a Test site.

wbhart’s picture

wbhart commented

I've done some reading and think I understand what you are recommending, but I'm lost when it comes to how to do this. I'm using Ipswitch WS_FTP Professional to access the files and to edit them. WS_FTP is set to use Notepad as editor.

Speaking of editing problems, it seems that only recently have I had problems with this. I've edited other files on my server before (e.g., Drupal CSS files) and didn't have any problems. Before I remember that when editing files the files would open in Notepad with proper formating. Now all the code is ran together and there are little boxes/white rectangles every so often in the file. Please excuse my ignorance, but this is the white space that you mentioned, yeah?

Thanks for help so far. I appreciate it. Any help on how specifically to make the changes that you suggest? Again, please excuse my newbie-ness.

heine’s picture

heine commented

Anything outside of the php-tags in a file will start output to the browser, making it impossible to later send new headers. The following code would lead to that problem, because it has whitespace before <?php.

 
<?php
  // First line contains whitespace
?>

You probably have a different problem: When you save a file as UTF 8in Notepad, the editor inserts three bytes (EF BB BF) at the beginning of the file, so you get something before the php-tag, starting output to the browser (<?php).

Best you can do is get another editor (PSpad) that is more capable; this will also solve your 'run-on' problems.

--
The Manual | Troubleshooting FAQ | Tips for posting | Make Backups! | Consider creating a Test site.

mintLuff’s picture

mintLuff commented

This was happening to me, all I had to do was remove the closing ?> tage from a PHP snippet I had copied and pasted into my template.php. It's helpful to remember this as something to check in case anyone has this problem.

heine’s picture

heine commented

The cause in your situation would have been whitespace after the closing ?> tag. Always good to know that you can often identify the problem by looking at the error message:

[snip] output started at /home/intercul/public_html/cms/modules/archive.module:1 [snip]

As you can see, line 1 of archive.module is the problem; most likely whitespace / UTF-8 BOM before the opening &lt?php tag.
--
The Manual | Troubleshooting FAQ | Tips for posting | Make Backups! | Consider creating a Test site.