Viewing 7 replies - 16 through 22 (of 22 total)
  • I’m getting this error even after updating to latest version.

    Fatal error: Call to undefined function get_userdata() in /home/gamebase/public_html/wp-includes/capabilities.php on line 1417

    Not using multi site

    Same here. White screen of death (generic 500 error) when selective plugin loading is turned on. WP 3.8.1, no multisite. Using 5.0.2 version of plugin.

    Following up…
    Even downgrading to version 4.1.1 breaks my WP 3.8.1 site.
    Had to remove it via FTP and all is well again.
    Really hope you find the bug and will gladly help if it’s an oddball combination of plugins (I’m running a very complex site w/ e commerce, paid registrations and phpBB). Don’t want to have to run without it.

    Plugin Author Jeff Sterup

    (@foomagoo)

    What happens if you turn on wp debug? Have you tried deleting the plugin organizer settings from the database? To do this go to the settings page and select no under Preserve plugin settings when Plugin Organizer is deactivated and then deactivate the plugin. Then activate it again.

    Thread Starter Andres Felipe

    (@naturalworldstm)

    A suggestion for those who are still having issues with 5.0.2

    After downgrading to 4.1.1 take a look at Plugin Organizer’s settings, in my case the selective plugin loading has been disabled, also check if You have done this:

    IMPORTANT: To enable selective plugin loading you must move the /wp-content/plugins/plugin-organizer/lib/PluginOrganizerMU.class.php file to /wp-content/mu-plugins or wherever your mu-plugins folder is located. If the mu-plugins directory does not exist you can create it. The plugin will attempt to create this directory and move the file itself when activated. Depending on your file permissions it may not be successful.

    If yes, try deleting and moving the file again and after doing all of this update to 5.0.2, this version solves (at least in my case) the fatal error.

    I hope this could help someone.

    Thanks for replying Jeffa nd Andres.

    wp-debug produces exactly the same result – a 500 error. It is not possible to delete the database settings the way you describe because the *instant* that the plugin is turned on, it is impossible to navigate to any other page (500 error)

    Andres – all MU files are in the correct location on installation. There is no change.

    Plugin Author Jeff Sterup

    (@foomagoo)

    If it’s only happening when selective plugin loading is enabled you can go into the database and set PO_disable_plugins to 0 in the wp_options table and it will skip the mu plugin. You could also delete the mu plugin file through ftp after activating.

Viewing 7 replies - 16 through 22 (of 22 total)
  • The topic ‘Fatal error after update to 5.0’ is closed to new replies.