Add option to not report Deprecated warnings

[ad_1]

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.

 

This site will teach you how to build a WordPress website for beginners. We will cover everything from installing WordPress to adding pages, posts, and images to your site. You will learn how to customize your site with themes and plugins, as well as how to market your site online.

Buy WordPress Transfer