WordPress, and how internet coding can suck a dick.

Just spent about an hour trying to fix a crashed database table, and in the process ended up breaknig my admin panel by leaving 2 blank lines at the end of a php file.

Im typing this up, and who knows, perhaps some other poor soul will stumble upon it through the miracle which is google if they have the same problem.

———————-

How do I solve the Headers already sent warning problem?

Description: You get a warning message on your browser that says:

Warning: Cannot modify header information - headers already sent by (output started at

Reason and Solution :

It is usually because there are spaces, new lines, or other garbage before an opening tag or after a closing ?> tag, typically in wp-config.php. This could be true about some other file too, so please check the error message, as it will list the specific file name where the error occurred (see "Interpreting the Error Message" below). Replacing the faulty file with one from your most recent backup or one from a fresh WordPress download is your best bet, but if neither of those are an option, please follow the steps below.

Interpreting the Error Message:

If the error message states: Warning: Cannot modify header information - headers already sent by (output started at /path/blog/wp-config.php:34) in /path/blog/wp-login.php on line 42, then the problem is at line #34 of wp-config.php, not line #42 of wp-login.php. In this scenario, line #42 of wp-login.php is the victim. It is being affected by the excess whitespace at line #34 of wp-config.php.

-------------------

The blog is back and working now, and is paid for until September 2011. Who knows, maybe you can actually expect some updates since im going back to university soon (end of this week most likely)