WP Login Problems [RESOLVED]

[Haze]

HI All,

I wondered whether anyone had any problems with login for WP sites recently? I have a couple of sites using WP themes but can't get into them. On the login pages they have  typically

Code:

Warning: Cannot modify header information - headers already sent by (output started at /home/lams08/public_html/wp-includes/load.php:655) in /home/lams08/public_html/wp-login.php on line 353

Warning: Cannot modify header information - headers already sent by (output started at /home/lams08/public_html/wp-includes/load.php:655) in /home/lams08/public_html/wp-login.php on line 365

And then after submission of username and password this sort of thing

Code:

Warning: Cannot modify header information - headers already sent by (output started at /home/lams08/public_html/wp-includes/load.php:655) in /home/lams08/public_html/wp-login.php on line 353

Warning: Cannot modify header information - headers already sent by (output started at /home/lams08/public_html/wp-includes/load.php:655) in /home/lams08/public_html/wp-login.php on line 365

Warning: Cannot modify header information - headers already sent by (output started at /home/lams08/public_html/wp-includes/load.php:655) in /home/lams08/public_html/wp-includes/pluggable.php on line 737

Warning: Cannot modify header information - headers already sent by (output started at /home/lams08/public_html/wp-includes/load.php:655) in /home/lams08/public_html/wp-includes/pluggable.php on line 738

Warning: Cannot modify header information - headers already sent by (output started at /home/lams08/public_html/wp-includes/load.php:655) in /home/lams08/public_html/wp-includes/pluggable.php on line 739

Warning: Cannot modify header information - headers already sent by (output started at /home/lams08/public_html/wp-includes/load.php:655) in /home/lams08/public_html/wp-includes/pluggable.php on line 934

I've tried Googling but none the wiser, what I've read is that this represents an inclusion of white space

The fix is, obviously, to remove that whitespace from the file. Read the error message carefully. It says "output started at ..." followed by a file name and a line number. That is the file (and line) that you need to edit. Ignore the second file name - that is only a file that included the file that has the whitespace. The first file is the one you have to edit, not the second one.

But I haven't used an external editor, I've contacted the hosting company to enquire also.

[Whatever]

Andy,

I remember years ago when you got this, think it was on osCommerce, you needed to remove any space from the end of the php files, and the error message points you in the direction of those files responsible.

Go to the last character and hold delete down after it to make sure everything is gone.

[suedenem]

http://www.netmagazine.com/features/net-strip-4-give-man-fish

 

[Steve Lampkins]

Wow, netmag is still going?

[suedenem]

Just about.  Agencies need something to put on their coffee tables in reception areas.

I don't think anyone actually reads it, though.

[Dom]

I wonder if they still steal forum questions and print them as if they were postal letters sent in... oh wait, never mind.



On-topic though, the last time I saw that error it was because the PHP page had already sent some output to the screen, but was then trying to redirect the user to another page (I think). Or perhaps it was the other way round (i.e. there was some code to redirect the user, but afterwards there was some code to output some content to the browser.) Either way it wasn't happy.

[sarahA]

On-topic though, the last time I saw that error it was because the PHP page had already sent some output to the screen, but was then trying to redirect the user to another page (I think). Or perhaps it was the other way round (i.e. there was some code to redirect the user, but afterwards there was some code to output some content to the browser.) Either way it wasn't happy.

It'd be the first one. you can't have output to a page and then a redirect (well not without some other unlikely stuff, but for good practice let's just say you can't).

Files can get corrupted and cause output but as Paul (Whatever) said, most likely white space.

[JasonD]

Which is why you shouldn't put ?> after any PHP at the end of the file.

[Haze]

Turns out the account had been hacked, the same injection as mentioned in another post I am told and host made the appropriate changes to the affected pages.... it has been a busy day. Hosts have blocked access from the offending IP address.

[Dom]

Lets hope they don't change their IP address and try again.