PHP Fatal errors in server log

  • Resolved Tim Burkart

    (@bigmoxy)


    1 year, 4 months ago

    I am seeing these fatal errors in the PHP error log and do not understand why they are occurring. Can you please provide some context? All plugins, core files and themes are up to date.

    [30-Jan-2025 11:41:23 UTC] PHP Fatal error: Uncaught Error: Undefined constant “ABSPATH” in /home/refres36/public_html/wp-includes/class-wp-http.php:11 Stack trace: #0 {main} thrown in /home/refres36/public_html/wp-includes/class-wp-http.php on line 11

    [30-Jan-2025 11:41:51 UTC] PHP Fatal error: Uncaught Error: Class “WP_Dependencies” not found in /home/refres36/public_html/wp-includes/class-wp-scripts.php:18 Stack trace: #0 {main} thrown in /home/refres36/public_html/wp-includes/class-wp-scripts.php on line 18

    [30-Jan-2025 11:41:56 UTC] PHP Fatal error: Uncaught Error: Class “WP_Dependencies” not found in /home/refres36/public_html/wp-includes/class-wp-styles.php:18 Stack trace: #0 {main} thrown in /home/refres36/public_html/wp-includes/class-wp-styles.php on line 18

    [30-Jan-2025 11:43:09 UTC] PHP Fatal error: Uncaught Error: Call to undefined function get_the_block_template_html() in /home/refres36/public_html/wp-includes/template-canvas.php:12 Stack trace: #0 {main} thrown in /home/refres36/public_html/wp-includes/template-canvas.php on line 12

    [30-Jan-2025 11:46:00 UTC] PHP Fatal error: Uncaught Error: Class “WP_Widget” not found in /home/refres36/public_html/wp-includes/widgets/class-wp-widget-block.php:17 Stack trace: #0 {main} thrown in /home/refres36/public_html/wp-includes/widgets/class-wp-widget-block.php on line 17

Viewing 1 replies (of 1 total)
  • Moderator bcworkz

    (@bcworkz)

    1 year, 4 months ago

    Those errors all refer to not being able to find built-in, standard WP resources. This indicates that there is some code in your site that’s not properly initializing WP before attempting to utilize WP resources. Unfortunately those errors alone will not help isolate the root cause. One way to determine the root cause is to obtain a debug backtrace to learn what the initial code was that led to these errors.

    Another way would be to look at the timestamps and find a corresponding request in the server access log.

    Yet another way would be to deactivate all plugins and switch to a default Twenty* theme. The errors should cease. Restore your theme and plugins, one at a time. Once errors occur again, the last activated module would be the cause. For this process to be effective, you should try to find some way to reliably induce one of the errors on demand.

Viewing 1 replies (of 1 total)

The topic ‘PHP Fatal errors in server log’ is closed to new replies.