• Resolved Thaddeous

    (@theig072)


    Getting a fatal error on wp-optimize settings page when I update the plugin from 3.0.12 to 3.0.13. I can deactivate all plugins except wp-optimize and still the error remains. Here is total error:

    Fatal error: Uncaught Error: Call to a member function show_current_notice() on bool in /nas/content/staging/theme/wp-content/plugins/wp-optimize/wp-optimize.php:625 Stack trace: #0 [internal function]: WP_Optimize->display_admin(”) #1 /nas/content/staging/theme/wp-includes/class-wp-hook.php(286): call_user_func_array(Array, Array) #2 /nas/content/staging/theme/wp-includes/class-wp-hook.php(310): WP_Hook->apply_filters(”, Array) #3 /nas/content/staging/theme/wp-includes/plugin.php(465): WP_Hook->do_action(Array) #4 /nas/content/staging/theme/wp-admin/admin.php(253): do_action(‘toplevel_page_W…’) #5 {main} thrown in /nas/content/staging/theme/wp-content/plugins/wp-optimize/wp-optimize.php on line 625. The site is experiencing technical difficulties. Please check your site admin email inbox for instructions.

Viewing 9 replies - 1 through 9 (of 9 total)
  • Thread Starter Thaddeous

    (@theig072)

    I should also add that we don’t use your image compression or cacheing. It’s all turned off.

    Hi,

    What version of PHP is your site running on?

    Marc

    Thread Starter Thaddeous

    (@theig072)

    7.3

    Thanks. I’m not sure why this is happening to you, but we’ll add a fix to prevent it in the next release.

    Marc.

    Thread Starter Thaddeous

    (@theig072)

    Hello. When is the next release? Still getting fatal error.

    Hi,

    I’m hoping for a release in the coming week.

    I’m curious about your error though, as according to my tests, the only way it could happen is if the action ‘admin_init’ is called twice, which shouldn’t really happen.

    Thread Starter Thaddeous

    (@theig072)

    Nice. That was happening in the functions.php file. I’ve combined the action and am calling it once. Fixed. Thanks!

    Thread Starter Thaddeous

    (@theig072)

    Solved

    Great.

    So you were calling do_action( 'admin_init' ) in your functions.php?

    Unless if you’re doing some heavy dashboard modifications, this is called by WordPress admin and should only be so. You can hook there by using add_action( 'admin_init', 'do_something_here' );, but calling it directly might break things or slow things down.

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘Fatal Error on update from 3.0.12 to 3.0.13’ is closed to new replies.