Critical errors caused by W3TC
-
Had the dreaded “critical error” upon opening WP admin, followed by an email “from WordPress” indicating critical errors caused by W3TC:
Since WordPress 5.2 there is a built-in feature that detects when a plugin or theme causes a fatal error on your site, and notifies you with this automated email. In this case, WordPress caught an error with one of your plugins, W3 Total Cache.
— snip —
Error Details ============= An error of type E_ERROR was caused in line 16 of the file /[server-path]/wp-content/plugins/w3-total-cache/Dispatcher.php. Error message: Uncaught Error: Class '\W3TC\ModuleStatus' not found in /[server-path]/wp-content/plugins/w3-total-cache/Dispatcher.php:16 Stack trace: #0 /[server-path]/wp-content/plugins/w3-total-cache/Generic_Plugin.php(281): W3TC\Dispatcher::component('ModuleStatus') #1 /[server-path]/wp-includes/class-wp-hook.php(288): W3TC\Generic_Plugin->admin_bar_menu(Object(WP_Admin_Bar)) #2 /[server-path]/wp-includes/class-wp-hook.php(312): WP_Hook->apply_filters(NULL, Array) #3 /[server-path]/wp-includes/plugin.php(544): WP_Hook->do_action(Array) #4 /[server-path]/wp-includes/admin-bar.php(86): do_action_ref_array('admin_bar_menu', Array) #5 /[server-path]/wp-includes/class-wp-hook.php(288): wp_admin_bar_render('') #6 /[server-path]/wp-includes/class-wp-hook.php(3
Viewing 6 replies - 1 through 6 (of 6 total)
Viewing 6 replies - 1 through 6 (of 6 total)
- The topic ‘Critical errors caused by W3TC’ is closed to new replies.