Warning: Cannot modify header information – headers already sent
Happens when your script tries to send a HTTP header to the client but there already was output before, which resulted in headers to be already sent to the client.
This is an
E_WARNING and it will not stop the script.
A typical example would be a template file like this:
<html> <?php session_start(); ?> <head><title>My Page</title> </html> ...
session_start() function will try to send headers with the session cookie to the client. But PHP already sent headers when it wrote the
<html> element to the output stream. You’d have to move the
session_start() to the top.
You can solve this by going through the lines before the code triggering the Warning and check where it outputs. Move any header sending code before that code.
An often overlooked output is new lines after PHP’s closing
?>. It is considered a standard practice to omit
?> when it is the last thing in the file. Likewise, another common cause for this warning is when the opening
<?php has an empty space, line, or invisible character before it, causing the webserver to send the headers and the whitespace/newline thus when PHP starts parsing won’t be able to submit any header.
If your file has more than one
<?php ... ?> code block in it, you should not have any spaces in between them. (Note: You might have multiple blocks if you had code that was automatically constructed)
Also make sure you don’t have any Byte Order Marks in your code, for example when the encoding of the script is UTF-8 with BOM.
- Headers already sent by PHP
- All PHP “Headers already sent” Questions on Stackoverflow
- Byte Order Mark
- What PHP Functions Create Output?