Cannot login to dashboard on latest version

Check your wp-config.php for spaces and newlines: https://codex.www.ads-software.com/FAQ_Troubleshooting#How_do_I_solve_the_Headers_already_sent_warning_problem.3F

Not really sure if I understand 100% what that’s telling me but it looked like there was no “?>” at the end of the wp-config.php file. I added it but it didn’t help at all.

I replaced again every file mentioned in any of the errors from a fresh download of 3.3 and it has no effect.

functions.php seems even from teh fresh download seems to have a line break after ?> at the end but removing it doesn’t change anything. Try both the one straight from the download and with the removed line break.

I had a similar issue & found that it was caused by the xhtml-content-negotiation-for-wordpress plugin.

I disabled this by moving the directory so it couldn’t find it & login proceeded ok after.

It gave different results depending on the browser. Internet Explorer just gave a blank page (although you could view the full page if you displayed the source). Firefox & Chrome gave an XML error & refused to display the page.

In my case it was linked to (or at least it was the first error on the page) the &rsaquo character, which for some reason seemed to not be liked when parsing HTML 5 (I’m assuming that this is what broke it with this update.

That’s ok, that file doesn’t need a closing “?>” php tag. Download a fresh copy of wp-config.php and copy all relevant info in to it. And re-upload. Or try removing all spaces and newlins before “<?php” and after require_once(ABSPATH . 'wp-settings.php');

Also try replacing the twentyeleven theme from a fresh download of WordPress. and switch to it by renaming your current theme’s folder in wp-content/themes.

Mat8iou,

I don’t have that plugin installed and I already disabled all my plugins to no avail.

Kessiemeijer,

There were no spaces before the opening tag. I took the ?> closing tag out and deleted app spaces after require_once(ABSPATH . ‘wp-settings.php’); It doesn’t change the errors at all.

Alright so I took the sample and copied the data in and then the error changed:

Warning: Cannot modify header information – headers already sent by (output started at /home7/singledu/public_html/wp-content/themes/atahualpa/functions.php:1) in /home7/singledu/public_html/wp-includes/pluggable.php on line 866

I don’t understand how the file cold f’d like that and unable to fix it. There were no spaces. I’m using notepad++ which is supposed to be for editing this kind of stuff. So now it says the problem is in atahualpa functions.php and I got the same thing there. There is nothing visibly wrong with that file at all.

I took functions.php from atalaupa and set it back to default. Now i’m getting all of this when I try and login:

Notice: wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or init hooks. Please see Debugging in WordPress for more information. (This message was added in version 3.3.) in /home7/singledu/public_html/wp-includes/functions.php on line 3578

Warning: Cannot modify header information – headers already sent by (output started at /home7/singledu/public_html/wp-includes/functions.php:3578) in /home7/singledu/public_html/wp-login.php on line 349

Warning: Cannot modify header information – headers already sent by (output started at /home7/singledu/public_html/wp-includes/functions.php:3578) in /home7/singledu/public_html/wp-login.php on line 361

Warning: Cannot modify header information – headers already sent by (output started at /home7/singledu/public_html/wp-includes/functions.php:3578) in /home7/singledu/public_html/wp-includes/pluggable.php on line 669

Warning: Cannot modify header information – headers already sent by (output started at /home7/singledu/public_html/wp-includes/functions.php:3578) in /home7/singledu/public_html/wp-includes/pluggable.php on line 670

Warning: Cannot modify header information – headers already sent by (output started at /home7/singledu/public_html/wp-includes/functions.php:3578) in /home7/singledu/public_html/wp-includes/pluggable.php on line 671

Warning: Cannot modify header information – headers already sent by (output started at /home7/singledu/public_html/wp-includes/functions.php:3578) in /home7/singledu/public_html/wp-includes/pluggable.php on line 866

All of those files have been updated (repeatedly) to stock files from 3.3

If I’m reading and understanding the help you linked correctly it’s saying that something is wrong on line 3578 of wp-includes/functions.php. I have replaced this file over and over and over from a fresh download of 3.3 but it doesn’t make any difference. I can’t see anything wrong with the file.

Any other ideas?

try replacing the twentyeleven theme from a fresh download of WordPress. and switch to it by renaming your current theme’s folder in wp-content/themes.

twenty eleven also got upgraded. It’s best if we troubleshoot with the default theme.

I tried that before and I just tried it again. Any attempts to do this crash even the public portion of the site. Not even the debugging works. Just a blank white screen.

Seems like this same problem is crashing thousands of other sites… but I can’t find any solutions…

https://www.google.com/#q=wp-includes/functions.php+on+line+3578&hl=en&prmd=imvns&ei=VaXwTozHNsjq8QPisZmhAQ&start=0&sa=N&bav=on.2,or.r_gc.r_pw.,cf.osb&fp=d2e74e97cb19d3e6&biw=1680&bih=949

Try this:
– renaming or deleting the .htaccess file by using FTP or whatever file management application your host provides. If you delete it make a backup first.

It’s only your front page that’s working. On all other pages I get a 404.

Actually that is what i was doing – that makes the problem worse. It was renamed. Putting it back as it was allows the site to function as normal at least on the public side + the debug message.

We need to troubleshoot with all plugins deactivated and on the default theme, even if it breaks the public site (we can always put your theme or plugins back).

There are plugin errors: wordpress-file-monitor and xml-sitemap-feed

Deactivate all plugins and switch to the default theme.