• Resolved enghell

    (@enghell)


    Hello, I spent some days debugging why one of our sites was not throwing stack traces but only Exception Thrown as the error, until we found it was not related to our php-fpm, nginx configuration but to wordpress, and then it was easy to find the culprit, your exception handler, was shutting down fatal errors, and hiding the file name, line numbers, and stack trace even with xdebug active, until we used this constant, NGG_DISABLE_SHUTDOWN_EXCEPTION_HANDLER either your exception handler should not sabotage development, in our case we are starting to upgrade this site for php 8.2, or the exception handler should be disabled by default.

    There’s a screenshot of how your exception handler displays errors.

    As you can see, there are no line number or anything, this is how it should look:

    This happened in php 8.2.9
Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Contributor Imagely

    (@imagely)

    Hi @enghell,

    This is a very valid point. The good news is that we look forward to default the exception handler to false once with the Pope framework removal release.

    Thread Starter enghell

    (@enghell)

    Hello, thank you for replying to my feedback, I’m looking forward for that update.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘The exception handler should be disabled by default.’ is closed to new replies.