Fatal error after update to 8.8.0

  • Resolved salubritas

    (@salubritas)


    3 years, 8 months ago

    After updating to JetPack 8.8.0 on my development site I get the following fatal error, breaking the site completely (front end and admin):

    [05-Aug-2020 12:04:24 UTC] PHP Fatal error: Uncaught Error: Call to undefined method Automattic\Jetpack\Assets::add_resource_hint() in [siteroot]\wp-content\plugins\jetpack\modules\shortcodes\videopress.php:13

    Not sure what has happened there. Some sort of problem with function deprecation?

    If I comment out the code in jetpack\modules\shortcodes\videopress.php the site functions OK again.

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Jeremy Herve

    (@jeherve)

    Jetpack Mechanic 🚀

    3 years, 8 months ago

    Thanks for the report. It’s an odd one, as the add_resource_hint method is included in Jetpack 8.8.

    I wonder if some files ended up missing when you updated the plugin. Does the problem remain when you delete the Jetpack plugin, and install it back from scratch?

    Could you also let me know if you use a custom caching plugin or caching solution on your server that may cause issues here?

    Thank you.

    Plugin Author Brandon Kraft

    (@kraftbj)

    Code Wrangler

    3 years, 8 months ago

    Another possibility is opcache — PHP has an operational caching system that may be holding on to an old version of the Assets class file before add_resource_hint was added.

    WordPress 5.5 will add opcache invalidation during the plugin update process which, if my theory is right, take care of these kind of potential problems in the future.

    Thread Starter salubritas

    (@salubritas)

    3 years, 8 months ago

    Thanks for the replies.

    I already reinstalled the plugin and it did not clear the error.

    No caching plugin on this dev environment.

    However, the error has cleared now. I updated a few other plugins on my dev environment, so maybe there was some sort of clash or maybe it was PHP opcache. I’m using IIS and WinCache in dev.

    Plugin Author Brandon Kraft

    (@kraftbj)

    Code Wrangler

    3 years, 8 months ago

    I betcha that’s it! I’m not familiar with WinCache, but reading https://www.iis.net/downloads/microsoft/wincache-extension it definitely sounds like an opcache solution that may be involved.

    Something along the lines of when the Assets class was included, it pulled the compiled copy from active memory instead of checking the file system for a fresh copy.

    Glad things are back up for you and thanks for reporting it.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Fatal error after update to 8.8.0’ is closed to new replies.