Voting starts in March for the Drupal Association Board election.
This error also presents as "Cannot modify header information" depending on PHP version.
In short, it means that somewhere in the code, something was printed to the browser before Drupal had finished preparing the page. This is most often caused by custom or modified code contributed from sources outside Drupal, so inspect your uniquely added code (including themes) first..
If you get a "Headers already sent" error, there are three likely causes.
If this error is not the first error message on the page, then it is most likely a 'avalanche effect' of previous errors and you may ignore it. Instead, focus on fixing the errors before it. When you fix the first error message(s), the "Headers already sent" error(s) will most likely disappear.
Text editors sometimes insert a UTF-8 byte order mark at the top of a file. In this case, the error message will usually say that "output started" at line 1 of some file. To fix this, configure your text editor to save the file without a byte order mark.
However, if you get an error "Headers already sent" as the first error and it tells you the error is near the end of a file (check which file "output started at" points to), that probably means that there are extra spaces or lines after a closing ?> php tag. In Drupal coding standards, it is strongly recommended (for this very reason) that PHP files should not have any closing ?> tags . Delete them, and everything should work fine.
Extra whitespace being added probably is caused by a bad unpacking program and / or a non-compliant editor (Windows Notepad or Wordpad, Mac TextEdit) adding it.
Problems with "headers already sent" can also be caused by having a blank line at the end of *.inc files. Drupal or more likely PHP seem to have problems with extra spaces here and there.
Check all *.inc files to make sure there are no closing php ?> tags in any of them. Closing php ?> tags are not needed in your *.inc files. Also, check all *.php files to make sure there are no blank lines at the beginning or at the end of the file.
If the error message indicates that this is caused by a module, disable modules one by one to find out which one is causing the problem.
This can also be caused by UTF-8. If a website is coded in ASCII and php files are being saved as UTF-8, it can cause this message. If the website and DB are both UTF-8, it should be ok to save php files as UTF-8.
Additionally, this error message is related to the "output_buffering" variable in php.ini. If output_buffering is set to some cache, the server will send headers with delay (or modify them shortly after they are sent), and this error will not be tripped. But, if output_buffering is set to 0 or not at all, then headers can be sent at only one moment and, if there's bad code, it will trip this error message. To sum up, turning on the "output_buffering" variable in php.ini fixes this problem.
Don't get paranoid, but if you see this on a site that was previously working well, this could be a symptom of non-drupal code injection. It's not uncommon for hackers who have compromised a server to run scripts that automatically inject HTML code into any *.php files they can find. Often by inserting spam links into page footers etc. Occasionally, this will have the side effect of breaking the code execution, or producing this error. Though rare, this error appearing on a previously stable site has sometimes led to a hack being discovered.
To test for this fully, the only real solution is to compare your current live code with the official version. In practice, checking *timestamps* on the files on the server can provide clues also. Search elsewhere for instructions on recovering from (and preventing) such hacks.