Help! Site down!

[wanderer]

I was fiddling with this plugin yesterday and now I can't sign in . I went into my host's FTP and deleted the plugin, checked the files I was working on for extra whitespace but they look normal.

Any ideas? Thanks a ton.

http://wander-argentina.com/

Warning: Cannot modify header information - headers already sent by (output started at /home/ande/public_html/wp-content/plugins/limit-title-plugin/title_limit_plugin.php:1) in /home/ande/public_html/wp-includes/pluggable.php on line 868

[Rebecca Diamond]

try clearing your cookies and your cache - I can view the site just fine. If that doesn't work for you, you may want to flush your DNS.

[wanderer]

Thanks for the quick reply. You're the one I hope to be able to pay one day to do this stuff for me! (I like that you give discounts to non-profits or charitable groups, I do the same thing).

At any rate, I did all that and still get the error message when I try to enter the admin for WP. Can see the site in Firefox but not in Safari. Calling my hosting service now. Thanks again.

[adew]

Originally Posted by wanderer

I was fiddling with this plugin yesterday and now I can't sign in . I went into my host's FTP and deleted the plugin, checked the files I was working on for extra whitespace but they look normal.

Any ideas? Thanks a ton.

http://wander-argentina.com/

Warning: Cannot modify header information - headers already sent by (output started at /home/ande/public_html/wp-content/plugins/limit-title-plugin/title_limit_plugin.php:1) in /home/ande/public_html/wp-includes/pluggable.php on line 868

I've already answered you on this problem in your other thread:
http://www.studiopress.com/support/s...ad.php?t=24431

[wanderer]

Yes, thank you. I checked all the files I was working on and they look fine as far as white space goes. I think I stayed up too late and made some other mistake. I'm on the phone with my server now. Cheers.

[adew]

Be aware that a visual check doesn't always fix this error. "Headers already sent.." errors invariably mean that there is unwanted whitespace somewhere, either after a closing PHP tag at the end of a file, or before an opening PHP tag at the top of the file.

[wanderer]

Well I called my host and everything worked again after he deleted the Plugin (I thought I had tried that, but apparently it was still there). He said it broke my WP backend.

Maybe because I was not using the latest version of WP?

Thanks.

[adew]

No, it's not a WP compatibility issue, it's the "headers cannot be sent..." issue I've described.

[wanderer]

I never opened the plugin file though.

How could it be the white space issue if deleting the plugin is what got me back in business?

Not sure, I'm the first to admit I don't understand all this, but deleting the plugin is what did the trick.