• Resolved David Derby

    (@itsonlycomputers)


    After upgrading to Woocommerce 6.6.1, I received the following error:

    Warning: require([FILEPATH]/wp-content/plugins/woocommerce/src/Autoloader.php): Failed to open stream: No such file or directory in [FILEPATH]/wp-content/plugins/woocommerce.php on line 24.

    I reverted back to Woocommerce 6.6.0 which DID resolve the issue.

    FYI.

Viewing 4 replies - 1 through 4 (of 4 total)
  • Hey @itsonlycomputers

    This kind of problem is usually caused by a conflict with your theme or with another plugin.
    ?
    The best way to determine this is to:

    • Disable all plugins except for WooCommerce
    • Repeat the action that is causing the problem

    If you’re not seeing the same problem after completing the conflict test, then you know the problem was with the plugins deactivated. To figure out which plugin is causing the problem, reactivate your other plugins one by one, testing after each, until you find the one causing conflict. You can find a more detailed explanation on how to do a conflict test here.

    If the issue persists after this, could you reinstall the plugin or copy the entire plugin folder through FTP.

    Hope this helps!

    Thread Starter David Derby

    (@itsonlycomputers)

    Hi Daniel, thanks for the feedback. I did exactly this and unfortunately, the issue persisted so I had no choice but to restore to the prior version of Woocommerce which did resolve my problem.

    I also notified the template provider, we’ll see what they have to say.

    Thanks again.
    David

    Hello,

    This error could be caused by a various reasons. I’d recommend reading through this article to troubleshoot the issue: https://www.wpbeginner.com/wp-tutorials/how-to-fix-the-wordpress-failed-to-open-stream-error/

    We haven’t heard back from you in a while, so I’m marking this thread closed for now – we’ll be here if and/or when you are ready to continue.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘WooCommerce 6.6.1 Fatal Error after upgrading)’ is closed to new replies.