WordPress.org

Support

Support » Plugins and Hacks » [Resolved] Fatal Error – Crashes Site

[Resolved] Fatal Error – Crashes Site

  • akinschris
    Member

    @akinschris

    Received the following message: Fatal error: Call to undefined function wp_get_current_user() in /hermes/web07/b2534/as.acstrate/public_html/wp-includes/capabilities.php on line 1039

    There are others with this issue as well.

Viewing 5 replies - 1 through 5 (of 5 total)
  • You can include me in that. And by the way: scrubbing and reinstalling wp-includes doesn’t cut it.

    By the way, I checked. wp_get_current_user() is defined in wp-includes/pluggable.php. That shouldn’t have anything to do with WPAA. But now I cannot deactivate the plugin, because I cannot even get into the dashboard.

    Couldn’t wait anymore. I signed into my file manager and scrubbed WPAA completely. Now the site will run. E-mail me when you are ready to help me rebuild my shattered Amazon Associations.

    Plugin Author Matthew Denton
    Member

    @mdbitz

    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

    As incredible as it seems, the fault does lie with a fatal omission from the capabilities.php file in wp-includes. A simple require-once statement after the comments (but before the first class declaration) allows WPAA to function as before. Amazingly, my configuration remained intact.

    The only problem was that I scrubbed a bunch of Amazon Carousel Widget shortcodes from my articles before this fix came in. Now I have to decide: do I restore them? Or not?

    Anyway, now, it would appear, this topic should be resolved. But this is a rather urgent fix. And WordPress needs to implement this right away, and maybe push another upgrade.

    Plugin Author Matthew Denton
    Member

    @mdbitz

    Yes, a strange issue as it is not present for all users. I am releasing a bug fix (1.7.1) to put in a check for if the wp_get_current_user function exists and if not the Admin Localization (to view content as a locale for logged in administrator) will be disabled.

    Sorry for any problems this caused.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘[Resolved] Fatal Error – Crashes Site’ is closed to new replies.