Troubleshooting the troubleshooting

  • yosmc

    (@yosmc)


    5 years, 4 months ago

    Hi all,

    I’m currently performing major operations on one of my sites, and errors are to be expected. No sweat – with debugging turned on, you can quickly see what went wrong, and fix it.

    Unfortunately, I’ve now run into a fatal error that doesn’t register, neither in the debugging nor in the logs. The page just says “There has been a critical error on this website.” with two lines for deprecated stuff above which I know are unrelated to my problem.

    And of course, there’s the link telling me about debugging, but since debugging is already turned on, it seems like there isn’t much else to see for the particular purpose.

    Does anyone have an idea what’s going on or what I could do? Really stuck here. Of course, I could deactivate the plugin which is causing the problems, but that’s not what I want – I want to see the broken line of code so I can fix it. Thanks!

    PS: Running the latest WP 5.6.

Viewing 1 replies (of 1 total)
  • Moderator bcworkz

    (@bcworkz)

    5 years, 4 months ago

    When you have WP_DEBUG defined as true, you will likely also want
    define( 'WP_DISABLE_FATAL_ERROR_HANDLER', true );
    Then the default PHP error handler ought to output any errors right on the page. You may then just get a blank white screen. You seem to at least know what plugin is the cause.

    You may have to resort to “divide and conquer” debugging. Remove roughly half of the plugin code. Easier said than done since what remains still has to more or less function. But this is the general concept. If the active half works, the problem is in the removed part. Restore roughly half of what was removed. continue along those lines until you zero in on the error.

Viewing 1 replies (of 1 total)

The topic ‘Troubleshooting the troubleshooting’ is closed to new replies.