• Resolved justin-bigscoots

    (@justin-bigscoots)


    Fatal error: Uncaught Error: Failed opening required '/home/nginx/domains/domain.com/public/wp-content/plugins/woocommerce-services/src/StoreNotices/StoreNoticesNotifier.php' (include_path='.:/usr/local/lib/php') in /home/nginx/domains/domain.com/public/wp-content/plugins/jetpack/vendor/jetpack-autoloader/class-php-autoloader.php:102
Viewing 15 replies - 1 through 15 (of 17 total)
  • Can confirm as well.

    I’m seeing similar PHP fatals on my customer websites.

    PHP Warning:  require(/www/public/wp-content/plugins/woocommerce-services/src/StoreNotices/StoreNoticesNotifier.php): Failed to open stream: No such file or directory in /www/public/wp-content/plugins/jetpack/vendor/jetpack-autoloader/class-php-autoloader.php on line 102
    Warning: require(/www/public/wp-content/plugins/woocommerce-services/src/StoreNotices/StoreNoticesNotifier.php): Failed to open stream: No such file or directory in /www/public/wp-content/plugins/jetpack/vendor/jetpack-autoloader/class-php-autoloader.php on line 102
    PHP Fatal error: Uncaught Error: Failed opening required '/www/public/wp-content/plugins/woocommerce-services/src/StoreNotices/StoreNoticesNotifier.php' (include_path='.:/usr/share/php') in /www/public/wp-content/plugins/jetpack/vendor/jetpack-autoloader/class-php-autoloader.php:102
    Stack trace:
    #0 /www/public/wp-content/plugins/woocommerce-services/woocommerce-services.php(876): Automattic\Jetpack\Autoloader\jpf11009ded9fc4592b6a05b61ce272b3c_jetpackⓥ14_8\al5_0_8\PHP_Autoloader::load_class()
    #1 /www/public/wp-content/plugins/woocommerce-services/woocommerce-services.php(734): WC_Connect_Loader->load_dependencies()
    #2 /www/public/wp-includes/class-wp-hook.php(324): WC_Connect_Loader->pre_wc_init()
    #3 /www/public/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()
    #4 /www/public/wp-includes/plugin.php(517): WP_Hook->do_action()
    #5 /www/public/wp-content/plugins/woocommerce/includes/class-woocommerce.php(851): do_action()
    #6 /www/public/wp-includes/class-wp-hook.php(324): WooCommerce->init()
    #7 /www/public/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()
    #8 /www/public/wp-includes/plugin.php(517): WP_Hook->do_action()
    #9 /www/public/wp-settings.php(727): do_action()
    #10 phar:///usr/local/bin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php(1374): require('...')
    #11 phar:///usr/local/bin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php(1293): WP_CLI\Runner->load_wordpress()
    #12 phar:///usr/local/bin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Bootstrap/LaunchRunner.php(28): WP_CLI\Runner->start()
    #13 phar:///usr/local/bin/wp/vendor/wp-cli/wp-cli/php/bootstrap.php(84): WP_CLI\Bootstrap\LaunchRunner->process()
    #14 phar:///usr/local/bin/wp/vendor/wp-cli/wp-cli/php/wp-cli.php(35): WP_CLI\bootstrap()
    #15 phar:///usr/local/bin/wp/php/boot-phar.php(20): include('...')
    #16 /usr/local/bin/wp(4): include('...')
    #17 {main}
    thrown in /www/public/wp-content/plugins/jetpack/vendor/jetpack-autoloader/class-php-autoloader.php on line 102
    Fatal error: Uncaught Error: Failed opening required '/www/public/wp-content/plugins/woocommerce-services/src/StoreNotices/StoreNoticesNotifier.php' (include_path='.:/usr/share/php') in /www/public/wp-content/plugins/jetpack/vendor/jetpack-autoloader/class-php-autoloader.php:102

    Same fatal error!

    [21-Jul-2025 13:12:22 UTC] PHP Fatal error: Uncaught Error: Failed opening required ‘/public_html/wp-content/plugins/woocommerce-services/src/StoreNotices/StoreNoticesNotifier.php’ (include_path=’.:/opt/alt/php81/usr/share/pear:/opt/alt/php81/usr/share/php:/usr/share/pear:/usr/share/php’) in /public_html/wp-content/plugins/woocommerce-services/vendor/jetpack-autoloader/class-php-autoloader.php:102
    Stack trace: 0 /public_html/wp-content/plugins/woocommerce-services/woocommerce-services.php(876): Automattic\Jetpack\Autoloader\jp7109386222804879fea6838ada605690\al5_0_7\PHP_Autoloader::load_class() 1 /public_html/wp-content/plugins/woocommerce-services/woocommerce-services.php(734): WC_Connect_Loader->load_dependencies()
    2 /public_html/wp-includes/class-wp-hook.php(324): WC_Connect_Loader->pre_wc_init()
    3 /public_html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()
    4 /public_html/wp-includes/plugin.php(517): WP_Hook->do_action()
    5 /public_html/wp-content/plugins/woocommerce/includes/class-woocommerce.php(851): do_action()
    6 /public_html/wp-includes/class-wp-hook.php(324): WooCommerce->init()
    7 /public_html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()
    8 /public_html/wp-includes/plugin.php(517): WP_Hook->do_action()
    9 /public_html/wp-settings.php(727): do_action()
    10 /public_html/wp-config.php(106): require_once(‘/public_html…’)
    11 /public_html/wp-load.php(50): require_once(‘/public_html…’)
    12 /public_html/wp-blog-header.php(13): require_once(‘/public_html…’)
    13 /public_html/index.php(17): require(‘/public_html…’)
    14 {main}

    thrown in /public_html/wp-content/plugins/woocommerce-services/vendor/jetpack-autoloader/class-php-autoloader.php on line 102

    +1

    Upgrading to 3.0.6 caused a fatal error on our site too.

    To get it to run again: Use FTP to rename the folder “plugins” (public-html/wp-content) which will deactivate all the site plugins and give back access to the WP dashboard. Rename the folder back to “plugins” and reactivate them from the plugin page in WP. (Do NOT reactivate WooCommerce Tax in this case.)

    If you have SSH, here is a handy bash script to rollback.

    version=$(wp plugin get woocommerce-services --field=version --skip-themes --skip-plugins)
    if [[ "$version" == "3.0.6" ]]; then
    wp plugin install woocommerce-services --version=3.0.5 --force --skip-themes --skip-plugins
    fi

    Yes, downgrading fixes the issue. Not seeing 3.0.5 in the available downloads, so rolled back to 3.0.4.

    EDIT: turns out when you select 3.0.4 from the downloads, you get 3.0.5. And 3.0.5 is listed in the changelog, but 3.0.6 is not. So confusing.

    Would it be possible to share a link to where older versions can be downloaded? I’m having trouble finding them. Thanks!

    Select the Development tab of the main plugin page, then click Advanced View and scroll down.

    dito!

    I rolled back from 3.0.6 to the 3.0.5 version from the overnight backup.
    Activated that version and site works again…

    Now it’s up to Woo to fix!

    • This reply was modified 10 months, 3 weeks ago by Marko Hoven. Reason: update with 'solution'
    • This reply was modified 10 months, 3 weeks ago by Marko Hoven.
    1. Visit the main plugin page and switch to the Development tab.
    2. In the right column, click the Advanced View link.
    3. Scroll to the bottom and click the dropdown under Previous Versions.
    4. Choose the version you want and click Download.
    Plugin Support shahzeen(woo-hc)

    (@shahzeenfarooq)

    Hi there!

    We are really sorry for the disruption you’re experiencing after updating the plugin. We understand how frustrating this can be.

    We’re aware of this issue and our development team is actively working on it. A fix is already underway and will be included in the next plugin release, which will be published shortly.

    We truly appreciate your patience and understanding while we work to get this resolved.

    Thanks, everyone!

    Hey everyone 👋

    We’ve just released version 3.0.7 of the plugin, which includes a fix related to the issue reported here in 3.0.6.

    If you’ve experienced any problems after updating to 3.0.6, could you please update to 3.0.7 and let us know if the issue persists on your end?

    Appreciate your patience and feedback, it helps us improve!

    3.0.7 is working for me.

Viewing 15 replies - 1 through 15 (of 17 total)

The topic ‘3.0.6 breaks install’ is closed to new replies.