Add option to not report Deprecated warnings

  • Resolved enghell

    (@enghell)


    1 year, 5 months ago

    Hello thanks for the great work with QM.

    We currently are upgrading one of our client’s sites to php 8.2 but we have noticed that the high number of deprecated warnings triggers a 502 error from QM.

    I notice a big number of these headers because of the deprecated warnings:

    2023/10/02 19:08:29 [debug] 56411#56411: *350 http fastcgi header: "X-QM-php_errors-error-57: {"key":"6e57729632e4b00fa3aedd22210f75d8","type":"deprecated","message":"Creation of dynamic property nggLoader::$nggAdminPanel is deprecated","file":"wp-content\/plugins\/nextgen-gallery\/products\/photocrati_nextgen\/modules\/ngglegacy\/nggallery.php","line":225,"stack":["nggLoader->load_dependencies()","nggLoader->__construct()","M_NggLegacy->initialize()","C_Component_Registry->initialize_module()","C_Component_Registry->initialize_all_modules()","C_NextGEN_Bootstrap->_load_pope()","C_NextGEN_Bootstrap->__construct()"],"component":"Plugin: nextgen-gallery"}"

    There isn’t much we can’t do but wait for plugins to start fixing their deprecated warnings, but we’d like to keep the usual error report from QM that’s very helpful, but without the deprecated register.

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

    (@johnbillion)

    WordPress Core Developer

    Deprecated errors are annoying aren’t they! You can silence them on a per plugin or theme basis, instructions here: https://querymonitor.com/blog/2018/07/silencing-errors-from-plugins-and-themes/

    Plugin Author John Blackbourn

    (@johnbillion)

    WordPress Core Developer

    Actually this might not fully solve your problem because the errors still get included in the PHP Errors panel in QM, just the corresponding warning in the admin toolbar gets hidden.

    Perhaps I need to introduce another method of hiding these.

    Thread Starter enghell

    (@enghell)

    Hello, sorry for the late reply, yeah this won’t clear the errors in the debug log but, will help with possible timeout generated by the plugin when sending the errors to the plugin’s frontend, I haven’t had a chance to review your solution based on the hook, since we solved the 502 errors by disabling the whole error reporting in QM.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Add option to not report Deprecated warnings’ is closed to new replies.