Fatal error when updating to 3.2.20

  • Resolved andytela

    (@andymoonshine)


    1 year, 4 months ago

    When I update to the latest version it throws a fatal error

    Tried on staging sites with all plugins disabled and 2023 theme

    ————————————-

    PHP Fatal error: Uncaught Error: Call to a member function is_exists() on null in /wp-content/plugins/wp-optimize/webp/class-wp-optimize-webp.php:244
    Stack trace: 0 /wp-content/plugins/wp-optimize/webp/class-wp-optimize-webp.php(160): WP_Optimize_WebP->add_webp_mime_type() 1 /wp-content/plugins/wp-optimize/webp/class-wp-optimize-webp.php(330): WP_Optimize_WebP->save_htaccess_rules() 2 /wp-content/plugins/wp-optimize/webp/class-wp-optimize-webp.php(307): WP_Optimize_WebP->run_self_test() 3 /wp-content/plugins/wp-optimize/includes/class-wp-optimize-updates.php(230): WP_Optimize_WebP->reset_webp_serving_method() 4 /wp-content/plugins/wp-optimize/includes/class-wp-optimize-updates.php(51): WP_Optimize_Updates::update_3218_reset_webp_serving_method() 5 /wp-content/plugins/wp-optimize/wp-optimize.php(1034): WP_Optimize_Updates::check_updates() 6 /wp-content/plugins/wp-optimize/wp-optimize.php(554): WP_Optimize->run_updates() 7 /wp-includes/class-wp-hook.php(308): WP_Optimize->plugins_loaded(”) 8 /wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters(NULL, Array) 9 /wp-includes/plugin.php(517): WP_Hook->do_action(Array) 10 /wp-settings.php(480): do_action(‘plugins_loaded’) 11 /wp-config.php(100): require_once(‘/Users/xxxxx/Do…’) 12 /wp-load.php(50): require_once(‘/Users/xxxxx/Do…’) 13 /wp-admin/admin.php(34): require_once(‘/Users/xxxxx/Do…’) 14 /wp-admin/plugins.php(10): require_once(‘/Users/xxxxx/Do…’) 15 {main}

    thrown in /wp-content/plugins/wp-optimize/webp/class-wp-optimize-webp.php on line 244

    ————————————-

    Cheers
    Andy

Viewing 10 replies - 1 through 10 (of 10 total)

  • Hello – thank you for reporting this. I have passed this on to the plugin development team for further investigation.

    Yes. I also got a fatal error when updating the plugin yesterday.

    =============
    Error Details
    =============
    An error of type E_ERROR was caused in line 244 of the file /home2/…/…/…/wp-content/plugins/wp-optimize/webp/class-wp-optimize-webp.php. Error message: Uncaught Error: Call to a member function is_exists() on null in /home2/…/…/…/wp-content/plugins/wp-optimize/webp/class-wp-optimize-webp.php:244
    Stack trace:
    #0 /home2/…/…/…/wp-content/plugins/wp-optimize/webp/class-wp-optimize-webp.php(160): WP_Optimize_WebP->add_webp_mime_type()
    #1 /home2/…/…/…/wp-content/plugins/wp-optimize/webp/class-wp-optimize-webp.php(330): WP_Optimize_WebP->save_htaccess_rules()
    #2 /home2/…/…/…/wp-content/plugins/wp-optimize/webp/class-wp-optimize-webp.php(307): WP_Optimize_WebP->run_self_test()
    #3 /home2/…/…/…/wp-content/plugins/wp-optimize/includes/class-wp-optimize-updates.php(230): WP_Optimize_WebP->reset_webp_serving_method()
    #4 /home2/…/…/…/wp-content/plugins/wp-optimize/includes/class-wp-optimize-updates.php(51): WP_Optimize_Updates::update_3218_reset_webp_serving_method()
    #5
    =============

    I have disabled the plugin for the site to work again.


    Hello @andymoonshine @moggyone

    Thank you both for reporting this. It would be very helpful if you could confirm please:

    – The version of WP-Optimize you were using prior to the attempted update.
    – If the WebP feature was turned on or off while updating to v3.2.20 as per this screenshot https://prnt.sc/xE-gOjG-DVvt located in WP-Optimize > Images > Compress images > WebP conversion.

    Hi,
    I was updating from v3.2.19, and the WebP feature was turned off while updating.
    Hope this helps

    Thread Starter andytela

    (@andymoonshine)

    Hi

    We were updating from 3.2.15 and the Webp feature is turned off

    Thanks

    great thank you @moggyone @andymoonshine

    Hello @moggyone?@andymoonshine

    This issue has now been fixed in v3.2.21, please could you try the new version.

    Hi,
    It’s now working great for me.
    Thank you very much for the prompt fix and update.

    You’re welcome

    Thread Starter andytela

    (@andymoonshine)

    Yep all good here
    Thanks for the quick turnaround

    Cheers
    Andy

Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘Fatal error when updating to 3.2.20’ is closed to new replies.