Error messages & can't reach admin after upgrading to 3.4.1 WordPress

Question

My hosting company upgraded their php, so my site was getting all sorts of error messages. So, I make a backup of all my content, deleted the wp-admin, wp-includes and loose files in html, then uploaded 3.4.1 of WordPress.

I got a bunch of errors at that point, so via FTP I went into my plugins folder and renamed them. That caused most of the messages to go away.

Now, I'm left with just two errors.

On the front page, I get this error, even though the page loads successfully:

Strict Standards: Redefining already defined constructor for class WP_Widget in /nfs/c05/h04/mnt/73941/domains/feltbeats.com/html/wp-includes/widgets.php on line 93

When I go to wp-admin however, the page does NOT load and I see only this:

Strict Standards: Redefining already defined constructor for class WP_Widget in /nfs/c05/h04/mnt/73941/domains/feltbeats.com/html/wp-includes/widgets.php on line 93

Warning: Cannot modify header information - headers already sent by (output started at /nfs/c05/h04/mnt/73941/domains/feltbeats.com/html/wp-includes/widgets.php:93) in /nfs/c05/h04/mnt/73941/domains/feltbeats.com/html/wp-includes/pluggable.php on line 881

I was actually just on the phone with my hosting company, and he very kindly looked at this for about an hour. He was focusing on it being an actual bug in 3.4.1 - but it seems the fact that the admin doesn't load would have been noticed. =)

So I assume it is something in my set up. But since I deleted most files, I can't see what it would be.

I had a custom functions.php file in my theme, but I tried deleting it and also the php in it.

Any help or just pointing me in the right direction would help. Thank you!

Answer 1

The debug mode is on on your site. Go into wp-config.php and look for:

define( 'WP_DEBUG', TRUE );

Change TRUE to FALSE.

See Debugging in WordPress for more information.

If this doesn’t help the error_reporting level is set somewhere else.

• .htaccess: Look for …

  php_value error_reporting integer
  

  … where integer matches one of the error constants. Remove the line or set its value to 1. More information.

• Theme: Somewhere in your theme might be a line like this:

  error_reporting( E_ALL | E_STRICT );
  

  Remove that line. If you cannot find it, remove all themes, upload a fresh copy of TwentyEleven. WordPress will pick this up if there are no other themes available.

• Plugin: One of your plugins can set error_reporting() too. Rename the directories plugins and mu-plugins in your wp-content directory to disable all plugins. If that fixes the problem download both directories and search for the error_reporting directive.

• Drop-In: There is a number of files that are loaded automatically. Look in your wp-content directory for advanced-cache.php, db.php, db-error.php, object-cache.php and sunrise.php ([more information about that][5]).
  Look also for a file in your languages directory named like en_US.php or de_DE.php. These are auto-loaded too.

If you still see no change the error_reporting is set in your php.ini. Ask your web hoster how to proceed.

[5]: http://hakre.wordpress.com/2010/05/01/must-use-and-drop-ins-plugins/ "Advanced PHP Error Handling via htaccess".