Fatal error stack not showing

  • Fatal error stack not showing. Only showing “There has been a critical error”. I must disable query monitor in order to see error and error stack.

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author John Blackbourn

    (@johnbillion)

    WordPress Core Developer

    Thanks for the report. What’s the fatal error message please?

    Thread Starter Sunny

    (@frdmsun)

    The error is from a plugin. You can test this by creating a fatal error in a plugin, e.g. require 'oops';

    Plugin Author John Blackbourn

    (@johnbillion)

    WordPress Core Developer

    Yes but what’s the exact fatal error message in your case? QM should be able to show the stack trace for most types of fatals.

    Thread Starter Sunny

    (@frdmsun)

    Error with QM active

    There has been a critical error on this website.
    Learn more about troubleshooting WordPress.

    Error without QM

    Warning: require(oops): failed to open stream: No such file or directory in C:\www\hw\wp-content\plugins\ipeds\index.php on line 32

Fatal error: require(): Failed opening required 'oops' (include_path='.;C:/laragon/etc/php/pear') in C:\www\hw\wp-content\plugins\ipeds\index.php on line 32

Notice: is_embed was called incorrectly. Conditional query tags do not work before the query is run. Before then, they always return false. Please see Debugging in WordPress for more information. (This message was added in version 3.1.0.) in C:\www\hw\wp-includes\functions.php on line 5313

Notice: is_search was called incorrectly. Conditional query tags do not work before the query is run. Before then, they always return false. Please see Debugging in WordPress for more information. (This message was added in version 3.1.0.) in C:\www\hw\wp-includes\functions.php on line 5313
There has been a critical error on this website.

Learn more about troubleshooting WordPress.
Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Fatal error stack not showing’ is closed to new replies.