Fatal error
-
Uncaught Error: Class 'WP_Widget_Block' not found in /home/2/t/teppe/www/wp-includes/class-wp-widget-factory.php:61 Stack trace: #0 /home/2/t/teppe/www/wp-includes/widgets.php(115): WP_Widget_Factory->register('WP_Widget_Block') #1 /home/2/t/teppe/www/wp-includes/widgets.php(1802): register_widget('WP_Widget_Block') #2 /home/2/t/teppe/www/wp-includes/class-wp-hook.php(303): wp_widgets_init('') #3 /home/2/t/teppe/www/wp-includes/class-wp-hook.php(327): WP_Hook->apply_filters(NULL, Array) #4 /home/2/t/teppe/www/wp-includes/plugin.php(470): WP_Hook->do_action(Array) #5 /home/2/t/teppe/www/wp-settings.php(560): do_action('init') #6 /home/2/t/teppe/www/wp-config.php(99): require_once('/home/2/t/teppe...') #7 /home/2/t/teppe/www/wp-load.php(50): require_once('/home/2/t/teppe...') #8 /home/2/t/teppe/www/wp-blog-header.php(13): require_once('/home/2/t/teppe...') #9 /home/2/t/teppe/www/index.php(17): require('/home/2/t/teppe...') #10 {main} thrown in /home/2/t/teppe/www/wp-includes/class-wp-widget-factory.php on line 61The page I need help with: [log in to see the link]
-
Did this error appear after updating WP to 5.8?
If so, try MANUALLY updating. Please read the Manual Update directions first.
BACKUP: If you haven’t already done, always backup everything (including your database) before doing any actions, just in case something really goes wrong. You can never have enough backups! See https://ww.wp.xz.cn/support/article/wordpress-backups/
This happend 02:33 so maybe an automated update?
Okay, looking at your site, I noticed the following error displayed in Norwegian language: Google Translation:
A critical error has occurred on this site.
Errors like this are logged. Check the error log on your server. If you can’t find the log, please contact your host. Meantime, enable wp_debug and wp_debug_log and after an error, look at wp-content/debug.log to see if anything gets logged there. https://ww.wp.xz.cn/support/article/debugging-in-wordpress/
You can also try this:
– Try manually resetting your plugins (no Dashboard access required). If that resolves the issue, reactivate each one individually until you find the cause.
– If that does not resolve the issue, access your server via SFTP or FTP, or a file manager in your hosting account’s control panel, navigate to/wp-content/themes/and rename the directory of your currently active theme. This will force the default theme to activate and hopefully rule-out a theme-specific issue (theme functions can interfere like plugins).The debug I used for the error report.
I have activated it again.
The debug log I can`t find where to change to true…The debug log I can`t find
Contact your hosting provider for assistance.
I can`t find this:
define( ‘WP_DEBUG_LOG’, true );
in the wp-config.php
Where van I find it?
Try reviewing https://kinsta.com/knowledgebase/wordpress-error-log/
[24-Jul-2021 07:30:49 UTC] PHP Fatal error: Uncaught Error: Class 'WP_Widget_Block' not found in /home/2/t/teppe/www/wp-includes/class-wp-widget-factory.php:61 Stack trace: #0 /home/2/t/teppe/www/wp-includes/widgets.php(115): WP_Widget_Factory->register('WP_Widget_Block') #1 /home/2/t/teppe/www/wp-includes/widgets.php(1802): register_widget('WP_Widget_Block') #2 /home/2/t/teppe/www/wp-includes/class-wp-hook.php(303): wp_widgets_init('') #3 /home/2/t/teppe/www/wp-includes/class-wp-hook.php(327): WP_Hook->apply_filters(NULL, Array) #4 /home/2/t/teppe/www/wp-includes/plugin.php(470): WP_Hook->do_action(Array) #5 /home/2/t/teppe/www/wp-settings.php(560): do_action('init') #6 /home/2/t/teppe/www/wp-config.php(100): require_once('/home/2/t/teppe...') #7 /home/2/t/teppe/www/wp-load.php(50): require_once('/home/2/t/teppe...') #8 /home/2/t/teppe/www/wp-login.php(12): require('/home/2/t/teppe...') #9 {main} thrown in /home/2/t/teppe/www/wp-includes/class-wp-widget-factory.php on line 61 [24-Jul-2021 07:31:28 UTC] PHP Fatal error: Uncaught Error: Class 'WP_Widget_Block' not found in /home/2/t/teppe/www/wp-includes/class-wp-widget-factory.php:61 Stack trace: #0 /home/2/t/teppe/www/wp-includes/widgets.php(115): WP_Widget_Factory->register('WP_Widget_Block') #1 /home/2/t/teppe/www/wp-includes/widgets.php(1802): register_widget('WP_Widget_Block') #2 /home/2/t/teppe/www/wp-includes/class-wp-hook.php(303): wp_widgets_init('') #3 /home/2/t/teppe/www/wp-includes/class-wp-hook.php(327): WP_Hook->apply_filters(NULL, Array) #4 /home/2/t/teppe/www/wp-includes/plugin.php(470): WP_Hook->do_action(Array) #5 /home/2/t/teppe/www/wp-settings.php(560): do_action('init') #6 /home/2/t/teppe/www/wp-config.php(100): require_once('/home/2/t/teppe...') #7 /home/2/t/teppe/www/wp-load.php(50): require_once('/home/2/t/teppe...') #8 /home/2/t/teppe/www/wp-blog-header.php(13): require_once('/home/2/t/teppe...') #9 /home/2/t/teppe/www/index.php(17): require('/home/2/t/teppe...') #10 {main} thrown in /home/2/t/teppe/www/wp-includes/class-wp-widget-factory.php on line 61 [24-Jul-2021 07:32:17 UTC] PHP Fatal error: Uncaught Error: Class 'WP_Widget_Block' not found in /home/2/t/teppe/www/wp-includes/class-wp-widget-factory.php:61 Stack trace: #0 /home/2/t/teppe/www/wp-includes/widgets.php(115): WP_Widget_Factory->register('WP_Widget_Block') #1 /home/2/t/teppe/www/wp-includes/widgets.php(1802): register_widget('WP_Widget_Block') #2 /home/2/t/teppe/www/wp-includes/class-wp-hook.php(303): wp_widgets_init('') #3 /home/2/t/teppe/www/wp-includes/class-wp-hook.php(327): WP_Hook->apply_filters(NULL, Array) #4 /home/2/t/teppe/www/wp-includes/plugin.php(470): WP_Hook->do_action(Array) #5 /home/2/t/teppe/www/wp-settings.php(560): do_action('init') #6 /home/2/t/teppe/www/wp-config.php(100): require_once('/home/2/t/teppe...') #7 /home/2/t/teppe/www/wp-load.php(50): require_once('/home/2/t/teppe...') #8 /home/2/t/teppe/www/wp-blog-header.php(13): require_once('/home/2/t/teppe...') #9 /home/2/t/teppe/www/index.php(17): require('/home/2/t/teppe...') #10 {main} thrown in /home/2/t/teppe/www/wp-includes/class-wp-widget-factory.php on line 61-
This reply was modified 4 years, 10 months ago by
Yui. Reason: formatting
Anyone?
I get the same error message on my site. Have you found a solution?
@kjelsberg no, sorry!
-
This reply was modified 4 years, 10 months ago by
The topic ‘Fatal error’ is closed to new replies.