Though I am not blogging much during this period, I’m checking my email daily, along with the game stats, and removing vasts amount of spam that come in each day. Keeping all the updates updated, and so forth.
Utter horror filled me when I attempted to log in today. Instead of my normal wordpress login screen, I was greeted with a rather scary looking set of error messages :
Warning: Cannot modify header information - headers already sent by (output started at
/path/greenslimegames.com/blog/wp-content/plugins/add-to-any/services.php:2) in
/path/greenslimegames.com/blog/wp-login.php on line 337
Warning: Cannot modify header information - headers already sent by (output started at
/path/greenslimegames.com/blog/wp-content/plugins/add-to-any/services.php:2) in
/path/greenslimegames.com/blog/wp-login.php on line 349
Warning: Cannot modify header information - headers already sent by (output started at
/path/greenslimegames.com/blog/wp-content/plugins/add-to-any/services.php:2) in
/path/greenslimegames.com/blog/wp-includes/pluggable.php on line 690
Warning: Cannot modify header information - headers already sent by (output started at
/path/greenslimegames.com/blog/wp-content/plugins/add-to-any/services.php:2) in
/path/greenslimegames.com/blog/wp-includes/pluggable.php on line 691
Warning: Cannot modify header information - headers already sent by (output started at
/path/greenslimegames.com/blog/wp-content/plugins/add-to-any/services.php:2) in
/path/greenslimegames.com/blog/wp-includes/pluggable.php on line 692
Warning: Cannot modify header information - headers already sent by (output started at
/path/greenslimegames.com/blog/wp-content/plugins/add-to-any/services.php:2) in
/path/greenslimegames.com/blog/wp-includes/pluggable.php on line 890
Terror filled my heart – had my blog been hacked? Had I started blogging about how certain pills had increased the size of my manhood by many inches, along with giving me a six pack and made me able to automatically date every girl on facebook?
I checked the front page of the site, and thankfully, I saw no posts like that. Unable to log in, I went to the next best thing – I loaded up my FTP client and opened the offending file ( services.php ). To my great relief, I saw the problem. For some strange reson, upgrading the addtoany plugin to version .9.9.7.3 caused a tab followed by a \n to appear on line one of this file. PHP sent this tab and newline to the browser, which meant it couldn’t send cookie info first. Which caused everything to fall on it’s head.
Quickly deleting this, and making sure that <? appeared on the first line solved the problem, and I could log in post. Let this be a lesson to everyone who uses the automatic update features of wordpress – make sure you check everything works properly before signing off for the night. The login screen being down isn’t the world’s biggest problem. But what if it had been something the prevented my front page from being accessed?
UPDATE : After a quick google, I found the problem was resolved very quickly by the addtoany team. LINK
lamentconfig
