• Resolved tunyk

    (@tunyk)


    I received an automatic email from the built-in WordPress function about an error after the update. There is also an error in the site’s PHP logs.

    An urgent fix release is required.

    WordPress 6.9.1
    WooCommerce (10.5.0)
    PHP 8.3.25

    PHP Fatal error: Uncaught Error: Failed opening required ‘…/www/wp-content/plugins/woocommerce/vendor/wordpress/abilities-api/includes/rest-api/endpoints/class-wp-rest-abilities-run-controller.php’ (include_path=’.:/usr/local/pear/php83′) in …/www/wp-content/plugins/woocommerce/vendor/wordpress/abilities-api/includes/rest-api/class-wp-rest-abilities-init.php

    PHP Warning: require_once(…/www/wp-content/plugins/woocommerce/vendor/wordpress/abilities-api/includes/rest-api/endpoints/class-wp-rest-abilities-run-controller.php): Failed to open stream: No such file or directory in …/www/wp-content/plugins/woocommerce/vendor/wordpress/abilities-api/includes/rest-api/class-wp-rest-abilities-init.php on line 25

    An error of type E_ERROR occurred on line 25 of the file .../www/wp-content/plugins/woocommerce/vendor/wordpress/abilities-api/includes/rest-api/class-wp-rest-abilities-init.php. 

    Error message: Uncaught Error: Failed opening required '.../www/wp-content/plugins/woocommerce/vendor/wordpress/abilities-api/includes/rest-api/endpoints/class-wp-rest-abilities-run-controller.php' (include_path='.:/usr/local/pear/php83') in .../www/wp-content/plugins/woocommerce/vendor/wordpress/abilities-api/includes/rest-api/class-wp-rest-abilities-init.php:25
    Stack trace:
    #0 .../www/wp-includes/class-wp-hook.php(341): WP_REST_Abilities_Init::register_routes(Object(WP_REST_Server))
    #1 .../www/wp-includes/class-wp-hook.php(365): WP_Hook->apply_filters(NULL, Array)
    #2 .../www/wp-includes/plugin.php(522): WP_Hook->do_action(Array)
    #3 .../www/wp-includes/rest-api.php(636): do_action('rest_api_init', Object(WP_REST_Server))
    #4 .../www/wp-includes/rest-api.php(594): rest_get_server()
    #5 .../www/wp-includes/rest-api.php(2981): rest_do_request(Object(WP_REST_Request))
    #6 [internal function]: rest_preload_api_request(Array, '/jetpack/v4/con...')
    #7 .../www/wp-content/plugins/woocommerce/src/Internal/Admin/Settings.php(148): array_reduce(Array, 'rest_preload_ap...')
    #8 .../www/wp-includes/class-wp-hook.php(341): Automattic\WooCommerce\Internal\Admin\Settings->add_component_settings(Array)
    #9 .../www/wp-includes/plugin.php(205): WP_Hook->apply_filters(Array, Array)
    #10 .../www/wp-content/plugins/woocommerce/src/Internal/Admin/WCAdminSharedSettings.php(73): apply_filters('woocommerce_adm...', Array)
    #11 .../www/wp-content/plugins/woocommerce/src/Blocks/Assets/AssetDataRegistry.php(274): Automattic\WooCommerce\Internal\Admin\WCAdminSharedSettings->Automattic\WooCommerce\Internal\Admin\{closure}()
    #12 .../www/wp-content/plugins/woocommerce/src/Blocks/Assets/AssetDataRegistry.php(390): Automattic\WooCommerce\Blocks\Assets\AssetDataRegistry->execute_lazy_data()
    #13 .../www/wp-includes/class-wp-hook.php(341): Automattic\WooCommerce\Blocks\Assets\AssetDataRegistry->enqueue_asset_data('')
    #14 .../www/wp-includes/class-wp-hook.php(365): WP_Hook->apply_filters('', Array)
    #15 .../www/wp-includes/plugin.php(522): WP_Hook->do_action(Array)
    #16 .../www/wp-admin/includes/template.php(2226): do_action('admin_print_foo...')
    #17 .../www/wp-admin/update.php(53): iframe_footer()
    #18 {main}
      thrown
Viewing 8 replies - 1 through 8 (of 8 total)
  • Thread Starter tunyk

    (@tunyk)

    Is a production site

    Hi @tunyk,

    Thanks for sharing the detailed error logs. This helps a lot.

    The error you’re seeing indicates that the WooCommerce 10.5.0 update did not complete cleanly, and a required file from the abilities-api vendor package is missing. We’re seeing a few similar reports where the update process was interrupted, or files were not fully extracted, which results in this fatal error.

    Since this is a production site, we recommend restoring functionality first by rolling back to the previous stable WooCommerce version.

    After that, please try the following steps on a staging or test site:

    1. Update all other plugins and your theme first.
    2. Re-download the WooCommerce 10.5.0 ZIP file from WordPress.org and manually re-upload it to ensure all files are properly extracted.
    3. Clear any server, object, CDN, and browser caches.
    4. Update WooCommerce as the final step.

    If the issue still occurs after a clean reinstallation, please share your System Status Report and confirm whether any security, caching, or deployment tools (e.g., Composer, CI/CD, atomic hosting) are involved in the update process.

    We understand how disruptive this is on a live site and appreciate your patience while we continue to investigate these reports.

    Thread Starter tunyk

    (@tunyk)

    The site does not have a test version and there are no ways to roll back the update. The only way to fix it is to release a plugin update

    Thread Starter tunyk

    (@tunyk)

    The theme and all plugins have been updated for a long time. I only see this error in the logs, but I don’t see it visually in the functionality. Can I just do nothing and wait for the next update? Will this fix this error?

    Pinging in to say that I had the exact same error in my production site , but im not noticing any issue regarding functionalities

    @tunyk, @romancc, @saivutukuru,

    I hit the same bug. It’s a filename mismatch in WooCommerce 10.5.0. The file class-wp-rest-abilities-init.php at line 25 requires class-wp-rest-abilities-run-controller.php, but the actual file is named class-wp-rest-abilities-v1-run-controller.php. To fix it, edit wp-content/plugins/woocommerce/vendor/wordpress/abilities-api/includes/rest-api/class-wp-rest-abilities-init.php line 25 and change class-wp-rest-abilities-run-controller.php to class-wp-rest-abilities-v1-run-controller.php or wait out the Automattic patch.

    Plugin Support Frank Remmy (woo-hc)

    (@frankremmy)

    @romancc @steveneray thanks for sharing.

    @tunyk we completely understand your situation.

    If you need to restore your site before the patch is released, you can roll back by downloading the previous WooCommerce version (10.4.3) from the Advanced View.

    After downloading, you can manually install it over the current version, and that will effectively roll things back.

    Right now, the team is actively investigating the issue. Since this is a fatal error affecting a large number of users, it’s very likely being prioritized internally. Until a permanent fix is published, rolling back, or alternatively deactivating, deleting, reinstalling WooCommerce, and then clearing any PHP/opcache has been resolving the issue for most users.

    If everything on your site appears to be functioning normally, you can also wait for the upcoming patch.

    I hope that helps. Let us know if you need anything else.

    Plugin Support Kay U a11n

    (@kingsleyinfo)

    It seems we haven’t heard back from you for a while, so I’ll go ahead and mark this thread as resolved. Feel free to reach out whenever you’re ready to continue.

    If you have time, we’d be grateful for a review: https://wordpress.org/support/plugin/woocommerce/reviews/

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

You must be logged in to reply to this topic.