• I have not actively used my website for almost a year now. Less than six months ago I upgraded to a newer version of WP automatically through my Blue Host account. At that time I received the following fatal error:

    Fatal error: Call to undefined method WordPress_Module::_weak_escape() in /home8/unconve4/public_html/wp-includes/wp-db.php on line 515

    Tonight, I upgraded the website again to 2.9.1 using the same method and continue to get the same message.

    Fatal error: Call to undefined method WordPress_Module::_weak_escape() in /home8/unconve4/public_html/wp-includes/wp-db.php on line 515

    Is there a relatively easy way to fix this? I have been out of the loop on how to manage a site for a while now so what might be a simple fix will likely be a brain tease for me. Any help would be greatly appreciated.

Viewing 7 replies - 1 through 7 (of 7 total)
  • Im running into exact same problem. Upgraded from 2.7 to 2.9.1 and getting same error. Cannot even get into WP Admin.

    Why did it barf and what’s the fix? The Auto upgrade indicated all steps were successful.

    It isn’t wise to upgrade from an old version to a really new version. It is much better to upgrade in steps, doing an upgrade to a slightly newer version, to another slightly newer version, etc., until you catch up to the latest and greatest version.

    Re-upload all of the core files for WordPress 2.9.1 manually, following the upgrade instructions provided here: https://codex.www.ads-software.com/Upgrading_WordPress

    Before doing that, make sure to deactivate all of your plugins as they can be the cause of many things breaking. One quick and easy way to deactivate the plugins is to rename the plugins folder in wp-content.

    This error is typically caused by plugins. Try disabling or deleting all plugins until you can confirm they are compatible with version 2.9.1.

    By renaming the plugins folder I was able to get the site to basically render and login to the WP-Admin.

    Now that I can pretty much guarantee its a plug-in thats wrestling with it, how do I de-activate the plugins manually one at a time BEFORE I login?

    If I rename the plugin’s root folder will that deactivate it? If so, I can rename them all to *_hold, then one by one rename them back until the site breaks, then I’ll know which plug-in is the cause?

    You can rename the plugins folder back to plugins and then rename each individual plugin in the plugins folder and that should work.

    I was also getting the error message:

    Fatal error: Call to undefined method WordPress_Module::_weak_escape() in /home/username/public_html/wp-includes/wp-db.php on line 515

    For me the plugin causing this error to display was Redirection

    I renamed the folder for that plugin:

    plugins/redirection

    to

    plugins/redirection1

    and it let me log-in to my admin area…

    I had the same problem as described in the original post. The instructions to disable plug-ins worked for me and I also discovered that the Redirection plug-in was the culprit.

    Upgrading to the latest version of WP also fixed my 404 error on the home page, which was somehow caused by a contributor’s post to my blog.

    I appreciate the help — it has been a long day!

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Fatal error: Call to undefined method WordPress_Module::_weak_escape() in /home8’ is closed to new replies.