Debug log showing thousands of errors

These are not errors, but deprecated filters notices which are triggered when a deprecated filter is used. Perhaps one of your plugins or a custom mu-plugin is using it.

No need to worry: these will continue to be supported for some time, so no immediate action is needed.

Two ways to remove the notices:

– Best practice: disable logging on the live site, as logging discloses information.
– If used in a custom mu-plugin: change the filter to the the new one at some point in the future, or, if used by another plugin, ask the plugin author of that plugin to do this.

For more information on the new filters, please see: https://complianz.io/developers-guide-for-third-party-integrations/

If you need any help with that, don’t hesitate to ask, we’re happy to help.

Thanks for the quick response. In the error it specifically states “cmplz_script_class”, which was a Complianz script, is the issue. It also states that it is since the plugin was updated to 6.0. So the only plugin that it seems is at fault is the Complianz plugin, is this not correct?

No, this informational notice (not an error) shows that some code is using the deprecated cmplz_script_class filter. This filter is not used by Complianz itself anymore, but will still work to allow other plugins and existing integrations to continue to work.

The Complianz plugin notices the usage of this filter, then adds this deprecated filter notice to the log to inform you that a deprecated function is used.

The notice informs the developers who used this code that, at some point in the future, it will need to be changed to cmplz_service_category instead.

I expect it to be included for at least a year as deprecated filter, so no need to worry about changing it immediately. When it’s finally dropped it will get mentioned in the changelog.