Support » Plugins and Hacks » [Resolved] Fatal error

[Resolved] Fatal error

  • I just did the automatic plugin upgrade, and I get this:

    Fatal error: Call to undefined function wp_get_current_user() in /home6/conserz6/public_html/wp-includes/capabilities.php on line 1039

    My site is now unusable and inaccessible. Thanks a lot.

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Matthew Denton


    Hi this seems to be an issue with WordPress per some other posts.

    Fix :

    You open capablities.php and add require_once(‘pluggable.php’);
    (but you need to change those quotes to single quotes) right after the opening <?php tag at the top of the file.

    As described in following Post

    All right. That works, and I reinstalled WPAA (after having to delete it to allow WordPress to function).

    Memo to WordPress.org: this is a fatal omission in capabilities.php. Somebody needs to fix this and push another upgrade right away.

    This topic is resolved, but the resolution will require a more basic fix.

    I had the same error after upgrading from a WP 3.0+ site to 3.1.2 from the automatic updater. Had Ozh’s admin plugin installed and it was showing wonky (the ‘sidebar’ menu area was there but no menu loaded, causing half the screen to dissapear), so I had to delete ozh admin and reinstall it, then got the above error when visiting the Network page. Using the tip above, I now get this error:

    Fatal error: Call to undefined function add_contextual_help() in /home/XYZ/public_html/wp-admin/network/settings.php on line 22

    Can someone help me please. This morning I uploaded:
    All In One Video Pack. I then activated it and now I cannot get into the administration area of my blog. I am not a programmer and I don’t know code. I have deactivated the plug in, but I cannot delete it because I cannot access the admin. area to do it, unless there is something I don’t know. I am not a programmer so please tell mw what to do if you know. I sure would appreciate the help.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘[Resolved] Fatal error’ is closed to new replies.