Can’t open my site to edit

Hm, I thought we would fix that by replacing the file. I suppose a plugin conflict could be causing the problem. Try resettings your plugins. If that resolves the issue, reactivate each one individually until you find the cause.

I tried the second option of creating a new plugins folder and renaming the original one to plunings.hold then logging in then going back and deleting the newly named plugins folder and re-changing the name or the original back to plugins. I tried this twice and it did not work. I get the exact same warnings that I got before. I also went to the phpMyAdmin function on Bluehost and could find the folders, but I was really not sure which lines under option_values was suppose to change and I figured I could really mess things up with MyAdmin, so I didn’t go that route. I could try, but the layout or order of things in the Bluehost MyAdmin was a little different than that mentioned in the howto article. Do you think I should give it a try? Is there a way to make a backup of the script so if I mess things up I can reinstall all the info?

Definitely give the phpMyAdmin method a try, but backup your database first.

I used phpMyAdmin and found the different items mentioned in your post and changed the value of the active_plugins to a:0:{}. I then tried to logon to the web site and it get the same warnings. No change.

I tried login in again this morning and something has changed. When I first try to log in, for a fraction of a second, and I mean it is just a short flash, it looks like the normal login screen appears and then is replaced by the login with the warnings on it. When I type in my info, I get the second warning page and can’t go anywhere after that. Well, at least something is different. I’m going to count that as progress, but then again I’m an optimist.

I just tried going into my Bluehost site and renaming the plugins.php and plugins-install.php folders, one at a time to see if that would make a difference. I didn’t.

I just checked my web site again and will all the fooling around, the links, plugins and photos don’t work. I think it is time to delete the entire site and start over. Macmanx, thanks for your help.

I have the same problem when i moved my website online. The problem is solved, locate functions.php around line 325-327, you will find a closing ?> and opening <?php, they are not needed. I removed both and now i can login.

Donloftus, this happened to me too, usually when I’m moving a site from a development server to the live server. I’ve found it easier to replace the file than looking for the white spaces, which sometimes works and sometimes doesn’t.

Check out this thread:
https://www.ads-software.com/support/topic/394349?replies=2

Basically, what I did is replaced the offending file from a backup (WARNING: make sure it’s your latest version, as you may have modified settings or styles, as in a stylesheet attached to a plugin, for example). Be sure you are replacing the correct file, as the error message is confusing:

Warning: session_start() [function.session-start]: Cannot send session cookie - headers already sent by (output started at /home/content/p/a/s/site/html/wp/wp-content/plugins/nextgen-gallery/lib/rewrite.php:557) in /home/content/p/a/s/site/html/wp/wp-content/plugins/si-contact-form/si-contact-form.php on line 1691

In my example above, you need to change the FIRST plugin file mentioned (nextgen=gallery) and not the second one (si-contact-form). Line 1691 refers to the first plugin (nextgen).

Once you replace that individual plugin file, reload your site. You will probably get the same error again, but with different files. Repeat the process. At some point, (probably 3 or 4 times) you will have removed the corrupted files and you should be able to get back to your site/admin interface again.

Let us know if that works.

I had this same problem:

Warning: Header may not contain more than a single header, new line detected. in …/wp-login.php on line 349

I was able to solve it by going to the wp_options table in phpmyadmin, finding the row with option_name ‘home’ and removing the hard enter after the url. This was introduced when I migrated the site from one host to another and I entered a test domain in this row.

I hope that saves someone some frustration!

– Brian