WordPress 2.8 bleeding-edge and WordPress_Module::_weak_escape()

After upgrading to 2.8-beeding-edge I got the following error:

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

Disabling Redirection plugin solved the problem. Could it be that Redirection also defines _weak_escape() or escape()? Server ir running PHP 5.2.6.


  1. Mr. Serge says:

    To get a 2.8 version I should be a beta tester or I can get a direct link also?

  2. Kaspars says:

    Mr. Serge, to test WordPress 2.8 simply change $wp_version inside /wp-includes/version.php from 2.7.1 to 2.8-bleeding-edge and do an automatic upgrade as you normally would when a new version is released.

  3. Mr. Serge says:

    Thank you. Great tip.

  4. jamEs says:

    How do I disable the plugin if I can’t get to anything on my blog? I tried just pulling it out of the plugins directory and that just opened up a whole other can of worms.

    • Kaspars says:

      jamEs, just delete the plugin folder and refresh any of the front-end pages for two times — first, it will display an error while the core disables the plugin, and at the second time the error should be gone.

  5. Hari Bhajan says:

    Thanks for the simple solution!

  6. Andy says:

    Had this same problem. Solution:

    Rename “plugins” to “plugins.old”
    Create new dir: plugins
    Refresh page, 2.8 should be installed and working fine.
    Copy old plugins from plugins.old to plugins one by one, refreshing every time, to pinpoint which plugin is causing the problem.

  7. ravi says:

    deleting redirection plugin helped. thanks for the simple solution

  8. Sandy Kumskov says:

    renaming redirection plugin folder was perfect, thanks very much :)

  9. Jon Milani says:

    This page just saved me from having many major headaches with my WP upgrade! Thank you so much!

    As a side note, there is a new version of the plugin available (as of today – June 20, 2009), so hopefully the new version won’t break WP 2.8.


  10. Jeremy Blake says:

    It was the redirection plugin for me too. Thank you for the help. Worked like a charm! :)

  11. JC says:

    Thank you for the simple solution. Brilliant

  12. Andy says:

    Redirection plugin was the problem for me to. I just deactivated it, upgraded it, and then reactivated it and all is well now!

Leave a Reply