Site logo

Archived topic

Debugging (talked to you via Twitter earlier)

5 replies · Started by Laura Brown on September 1, 2015

Viewing posts 1–6 of 6

Notice: register_uninstall_hook was called incorrectly. Only a static class method or function can be used in an uninstall hook. Please see Debugging in WordPress for more information. (This message was added in version 3.1.) in /wp-includes/functions.php on line 3622

Warning: Cannot modify header information - headers already sent by (output started at
/wp-includes/functions.php:3622) in
/wp-includes/pluggable.php on line 1207

Warning: Cannot modify header information - headers already sent by (output started at
/wp-includes/functions.php:3622) in
/wp-includes/pluggable.php on line 1207

This also comes up from the admin side. I looked it up but I don't want to mess with the functions file. I can't even find the uninstall code it mentions.

These errors are usually a result of a poorly code/old plugin.

Do they persist even with no plugins activated?

Yes! It was worse before I did some cleaning in the database and tables. But, I don't know what I'm doing enough to go through bit by bit and it is an old site so there is a lot to go through. This is why I think I will just start a new db and move only the posts and my images over to it. I can get fresh files for core, plugins I use and GP.

Will that be all I need though? If I use the export with WP will that just give me my posts or will I risk having old plugin files stuck in with it?

Will be a big job to put it all together again I think. Demolition is always easier.

Those errors will typically not be caused by anything in the database.

This is a plugin error: Notice: register_uninstall_hook was called incorrectly. Only a static class method or function can be used in an uninstall hook.

For example: https://wordpress.org/support/topic/register_uninstall_hook-was-called-incorrectly

This is also a plugin error (because pluggable.php is involved): Warning: Cannot modify header information – headers already sent by...

These errors are caused by code running on your site - not the database.

Do you have caching? If so, deactivate all of your plugins and clear the cache.

I'm 90% certain that this is because of plugins.

Let me know :)

Hi Laura. Here are some links that discuss moving only specific data from one site to another.

Thanks Tom and bdbrown (funny, my initials are ld brown). Will look at your suggestions Tom. Hope that works.

This archived topic is closed to new replies.