Woocommerce Error after update

Resolved nootkan
(@nootkan)

3 months, 2 weeks ago

So today I got a new version of woocommerce available notification and clicked the update button. Immediately I received this email telling me of an error. I tried to download the plugin from the download link in the wp/plugins/woocommerce market and reinstall figuring the file transfer got corrupted but the error persists. The plugin worked fine before the update with no errors so it must be something to do with the update. The website loads properly and I can login to the dashboard. Can’t seem to see any issues with either frontend or backend even though I am being told of the error.

Error Details

An error of type E_ERROR was caused in line 25 of the file /home/username/public_html/wp-content/plugins/woocommerce/vendor/wordpress/abilities-api/includes/rest-api/class-wp-rest-abilities-init.php. Error message: Uncaught Error: Failed opening required ‘/home/username/public_html/wp-content/plugins/woocommerce/vendor/wordpress/abilities-api/includes/rest-api/endpoints/class-wp-rest-abilities-run-controller.php’ (include_path=’.:/opt/cpanel/ea-php82/root/usr/share/pear’) in /home/username/public_html/wp-content/plugins/woocommerce/vendor/wordpress/abilities-api/includes/rest-api/class-wp-rest-abilities-init.php:25
Stack trace: 0 /home/username/public_html/wp-includes/class-wp-hook.php(341): WP_REST_Abilities_Init::register_routes(Object(WP_REST_Server)) 1 /home/username/public_html/wp-includes/class-wp-hook.php(365): WP_Hook->apply_filters(NULL, Array) 2 /home/username/public_html/wp-includes/plugin.php(522): WP_Hook->do_action(Array) 3 /home/username/public_html/wp-includes/rest-api.php(636): do_action(‘rest_api_init’, Object(WP_REST_Server)) 4 /home/username/public_html/wp-includes/rest-api.php(594): rest_get_server() 5 /home/username/public_html/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 /home/username/public_html/wp-content/plugins/woocommerce/src/Internal/Admin/Settings.php(148): array_reduce(Array, ‘rest_preload_ap…’) 8 /home/username/public_html/wp-includes/class-wp-hook.php(341): Automattic\WooCommerce\Internal\Admin\Settings->add_component_settings(Array) 9 /home/username/public_html/wp-includes/plugin.php(205): WP_Hook->apply_filters(Array, Array) 10 /home/username/public_html/wp-content/plugins/woocommerce/src/Internal/Admin/WCAdminSharedSettings.php(73): apply_filters(‘woocommerce_adm…’, Array) 11 /home/username/public_html/wp-content/plugins/woocommerce/src/Blocks/Assets/AssetDataRegistry.php(274): Automattic\WooCommerce\Internal\Admin\WCAdminSharedSettings->Automattic\WooCommerce\Internal\Admin{closure}() 12 /home/username/public_html/wp-content/plugins/woocommerce/src/Blocks/Assets/AssetDataRegistry.php(390): Automattic\WooCommerce\Blocks\Assets\AssetDataRegistry->execute_lazy_data() 13 /home/username/public_html/wp-includes/class-wp-hook.php(341): Automattic\WooCommerce\Blocks\Assets\AssetDataRegistry->enqueue_asset_data(”) 14 /home/username/public_html/wp-includes/class-wp-hook.php(365): WP_Hook->apply_filters(”, Array) 15 /home/username/public_html/wp-includes/plugin.php(522): WP_Hook->do_action(Array) 16 /home/username/public_html/wp-admin/includes/template.php(2226): do_action(‘admin_print_foo…’) 17 /home/username/public_html/wp-admin/update.php(53): iframe_footer() 18 {main}

thrown

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

Sai (woo-hc)
(@saivutukuru)

3 months, 2 weeks ago
Hi @nootkan,

Thanks for sharing the detailed error log.

This is a known issue affecting some sites after updating to the latest WooCommerce version (10.5.0). The error indicates that part of the bundled abilities-api package was not loaded correctly during the update, which can happen if the update process was interrupted or failed partway through.

Since your site is still loading and the dashboard is accessible, this is consistent with what others are seeing, the error is triggered during REST API initialization rather than breaking the frontend entirely.

You can try the following steps:
1. Force a clean reinstall of WooCommerce
  - Go to Plugins → Installed Plugins
  - Deactivate WooCommerce
  - Click Delete
  - Reinstall WooCommerce fresh from the WordPress plugin repository
    (This ensures all vendor files are restored correctly.)
2. Clear any server-side caches
  - If you’re using OPcache, object cache, or a host-level cache, clear it after reinstalling.
3. Check file permissions
  - Make sure WooCommerce plugin files are owned correctly and readable by PHP, especially under /vendor/wordpress/abilities-api/.
If the issue persists after a clean reinstall, the safest temporary workaround is to roll back to WooCommerce 10.4.6, which multiple users have confirmed does not have this problem.

Please let us know if a clean reinstall resolves it for you.
Thread Starter nootkan
(@nootkan)

3 months, 2 weeks ago

No the clean install didn’t work for me so I rolled back to my backup and it is all good now. Must something wrong with the update?

Plugin Support Frank Remmy (woo-hc)
(@frankremmy)

3 months, 2 weeks ago

Hi @nootkan,

Thanks for the update, and I’m glad rolling back got things working again. To confirm, yes. there was an issue introduced in WooCommerce 10.5.0 that affected some sites in exactly the way you described.

Our development team is already working on this, and WooCommerce 10.5.1 is currently being prepared to address the problem.

In the meantime, the approach you took is the correct temporary workaround: rolling back to the previous stable version until the fix is released. Once 10.5.1 becomes available, updating to that version should resolve the issue without needing any additional steps.

Thanks again for your patience and for reporting back with what worked on your end.

Thread Starter nootkan
(@nootkan)

3 months, 2 weeks ago

Okay thanks for the clarification and I’ll wait until the new update comes out.

Plugin Support LovingBro (woo-hc)
(@lovingbro)

3 months, 2 weeks ago

Hi @nootkan,

Glad we could help clarify things and point you in the right direction. Keeping an eye on the WooCommerce releases page is a great idea, as updates and fixes are announced there as soon as they are available. You can follow along here, https://developer.woocommerce.com/releases/.

In the meantime, if you have a moment and feel the support you received was helpful, we would really appreciate a review of WooCommerce. Feedback from merchants like you helps the team continue improving the plugin and support experience. You can leave a review here, https://ww.wp.xz.cn/support/plugin/woocommerce/reviews/#new-post.

If anything else comes up, feel free to start a new topic and we will be happy to help.

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

You must be logged in to reply to this topic.