Title: Fatal error in debug.log – not possible to open dashboard in backend anymore Last modified: February 7, 2026 --- # Fatal error in debug.log – not possible to open dashboard in backend anymore * Resolved [fox-didl](https://wordpress.org/support/users/fox-didl/) * (@fox-didl) * [4 months ago](https://wordpress.org/support/topic/fatal-error-in-debug-log-3/) * [07-Feb-2026 09:22:11 UTC] PHP Fatal error: Uncaught Error: Call to a member function get_name() on false in /xxx/wp-content/plugins/woocommerce/templates/ dashboard-widget-reviews.php:39 Stack trace: 0 /xxx/wp-content/plugins/woocommerce/ includes/wc-core-functions.php(346): include() 1 /xxx/wp-content/plugins/woocommerce/ includes/admin/class-wc-admin-dashboard.php(517): wc_get_template(‘dashboard- widge…’, Array) 2 /xxx/wp-admin/includes/template.php(1453): WC_Admin_Dashboard- >recent_reviews(”, Array) 3 /xxx/wp-admin/includes/dashboard.php(280): do_meta_boxes( Object(WP_Screen), ‘column4’, ”) 4 /www/xxx/wp-admin/index.php(204): wp_dashboard() 5 {main} * thrown in /xxx/wp-content/plugins/woocommerce/templates/dashboard-widget-reviews. php on line 39 AND/xxx/wp-content/plugins/woocommerce/vendor/wordpress/abilities- api/includes/rest-api/class-wp-rest-abilities-init.php verursacht. Fehlermeldung: Uncaught Error: Failed opening required ‘/xxx/wp-content/plugins/woocommerce/ vendor/wordpress/abilities-api/includes/rest-api/endpoints/class-wp-rest-abilities- run-controller.php’ (include_path=’.:/usr/share/php:..’) in /xxx/wp-content/plugins/ woocommerce/vendor/wordpress/abilities-api/includes/rest-api/class-wp-rest-abilities- init.php:25 - This topic was modified 4 months ago by [fox-didl](https://wordpress.org/support/users/fox-didl/). Viewing 5 replies - 1 through 5 (of 5 total) * [Sai (woo-hc)](https://wordpress.org/support/users/saivutukuru/) * (@saivutukuru) * [4 months ago](https://wordpress.org/support/topic/fatal-error-in-debug-log-3/#post-18813507) * Hi [@fox-didl](https://wordpress.org/support/users/fox-didl/), * Thanks for reporting this and for sharing the full error logs, that’s very helpful. * The fatal error coming from `woocommerce/templates/dashboard-widget-reviews.php`(` Call to a member function get_name() on false`) indicates that WooCommerce is attempting to load recent product reviews in the admin dashboard, but one of the expected objects is not being returned correctly. When this happens, the dashboard widget fails and can block access to `/wp-admin`. * The second fatal error related to `vendor/wordpress/abilities-api`suggests that WooCommerce is also failing to load a required vendor file, which can happen if: - the WooCommerce update was incomplete or corrupted, or - files are missing due to a deployment, permissions, or caching issue. * Please try these steps: 1. **Temporarily disable the WooCommerce dashboard widgets** (if possible) by renaming the `woocommerce` plugin folder via FTP/SSH to regain backend access. 2. **Reinstall WooCommerce** by downloading a fresh copy and replacing the plugin files (do not delete the plugin settings or data). 3. Ensure there are **no missing or modified files** inside `woocommerce/vendor/ wordpress/abilities-api/`. 4. If the issue started after a recent update, rolling back to the previous WooCommerce version can be used as a temporary workaround. * Please let us know if reinstalling WooCommerce resolves the issue. * Thread Starter [fox-didl](https://wordpress.org/support/users/fox-didl/) * (@fox-didl) * [4 months ago](https://wordpress.org/support/topic/fatal-error-in-debug-log-3/#post-18813515) * Try to reinstall 10.5 again. But no change after. * [07-Feb-2026 09:53:30 UTC] PHP Fatal error: Uncaught Error: Call to a member function get_name() on false in /wp-content/plugins/woocommerce/templates/dashboard- widget-reviews.php:39 Stack trace: 0 /wp-content/plugins/woocommerce/includes/ wc-core-functions.php(346): include() 1 /wp-content/plugins/woocommerce/includes/ admin/class-wc-admin-dashboard.php(517): wc_get_template(‘dashboard-widge…’, Array) 2 /wp-admin/includes/template.php(1453): WC_Admin_Dashboard->recent_reviews(”, Array) 3 /wp-admin/includes/dashboard.php(280): do_meta_boxes(Object(WP_Screen),‘ column4’, ”) 4 /wp-admin/index.php(204): wp_dashboard() 5 {main} * thrown in /wp-content/plugins/woocommerce/templates/dashboard-widget-reviews. php on line 39 * Reverting back und everything fine again now. Waiting for bugfix 10.5.1. * [godthor](https://wordpress.org/support/users/godthor/) * (@godthor) * [4 months ago](https://wordpress.org/support/topic/fatal-error-in-debug-log-3/#post-18813609) * You can “fix” the issue (for now) by editing /wp-content/plugins/woocommerce/ templates/dashboard-widget-reviews.php and removing all code below the first ? > you encounter. So leave only line #1-27. It will make your review dashboard widget empty but at least your dashboard will load. - This reply was modified 4 months ago by [godthor](https://wordpress.org/support/users/godthor/). * [Sai (woo-hc)](https://wordpress.org/support/users/saivutukuru/) * (@saivutukuru) * [4 months ago](https://wordpress.org/support/topic/fatal-error-in-debug-log-3/#post-18814075) * Hi [@fox-didl](https://wordpress.org/support/users/fox-didl/), * Thanks for the update and for confirming that reverting to the previous WooCommerce version resolves the issue. That’s helpful confirmation. * We’re seeing multiple reports around WooCommerce 10.5.0 where the admin dashboard is blocked due to errors in the dashboard widgets and missing vendor files, even after a clean reinstall. This has been shared with the development team and is under investigation. * For now, rolling back to the previous stable version is the safest workaround on production sites. While editing core plugin files (like removing code from` dashboard-widget-reviews.php`) may unblock the dashboard temporarily, but we don’t recommend this long-term, as changes will be overwritten on update. * We appreciate your patience, and thanks again for taking the time to share detailed logs and testing results. It really helps. * Plugin Support [Kay U a11n](https://wordpress.org/support/users/kingsleyinfo/) * (@kingsleyinfo) * [3 months, 3 weeks ago](https://wordpress.org/support/topic/fatal-error-in-debug-log-3/#post-18824849) * Since we haven’t received any updates from you, I’ll mark this as resolved for now. If you need further assistance, you’re welcome to start a new thread. Viewing 5 replies - 1 through 5 (of 5 total) You must be [logged in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Ffatal-error-in-debug-log-3%2F%3Foutput_format%3Dmd&locale=en_US) to reply to this topic. * ![](https://ps.w.org/woocommerce/assets/icon.svg?rev=3234504) * [WooCommerce](https://wordpress.org/plugins/woocommerce/) * [Frequently Asked Questions](https://wordpress.org/plugins/woocommerce/#faq) * [Support Threads](https://wordpress.org/support/plugin/woocommerce/) * [Active Topics](https://wordpress.org/support/plugin/woocommerce/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/woocommerce/unresolved/) * [Reviews](https://wordpress.org/support/plugin/woocommerce/reviews/) * 5 replies * 4 participants * Last reply from: [Kay U a11n](https://wordpress.org/support/users/kingsleyinfo/) * Last activity: [3 months, 3 weeks ago](https://wordpress.org/support/topic/fatal-error-in-debug-log-3/#post-18824849) * Status: resolved