Critical Error: require(): Failed opening required

  • Resolved dmbrooking

    (@dmbrooking)


    4 years, 10 months ago

    This error is happening on 9.7, 9.7.1, and 9.8. We have not done a deploy in probably a week at least and it just started happening this morning.

    We are getting the following error over and over again that is bringing down our site:

    require(): Failed opening required ‘/nas/content/live/mokeloke/wp-content/plugins/jetpack/vendor/automattic/jetpack-assets/src/class-assets.php’ (include_path=’.:/usr/share/pear/php:/usr/share/php’)

    Can someone help?

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Contributor Stef (a11n)

    (@erania-pinnera)

    4 years, 10 months ago

    Hi @dmbrooking,

    Thanks for reporting this!

    This error usually indicates that some files are missing from your installation of Jetpack. This sometimes happens when your site fails to complete a plugin update, because of limited resources during the update process.

    To solve this issue, log in to your site via FTP or CPanel, delete the existing Jetpack plugin folder, and reinstall the plugin manually as explained here:

    http://codex.wordpress.org/Managing_Plugins#Manual_Plugin_Installation

    You’ll find the Jetpack plugin folder here:

    wp-content
   plugins
     jetpack - DELETE THIS FOLDER

    If you’re not sure how to do this, you can ask your hosting company for help. They should also have documentation explaining how to edit or remove files from your site using FTP or a File Manager in your admin panel.

    Hope that helps! Let me know how you get on.

    Thread Starter dmbrooking

    (@dmbrooking)

    4 years, 10 months ago

    Awesome.. I had the exact same issues with out staging site as well and over the weekend thought to do exactly what you mentioned above. I did that and monitored for errors over the weekend and saw none – just updated our prod site the same way and it’s looking good.

    Not sure how files disappeared… must have been a faulty upgrade in my local env or weird merge conflit on git that I handled poorly.

    But all good now, thanks!

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

The topic ‘Critical Error: require(): Failed opening required’ is closed to new replies.