Temporarily switch to the default WordPress theme and re-check to see if the error changes or goes away. If it does, your active theme is the issue and you should consult the vendor for any available updates.
If the error remains, deactivate your plugins and then reactivate one by one until you find the plugin responsible for the deprecated message.
Thank you – I will try that solution. I’ve hoping to solve this without deactivating all the plugins. My concern is that when I reactivate the plugins (28) that information/settings will be lost.
Will I lose custom coding by switching to the default theme?
When/if I find that plugin causing the deprecated message, what do I do at that point? Delete the plugin and find a substitute?
Thanks –
Some info and instructions no one should be without.WordPress Backups
Also something that should be done regularly, and especially prior to doing anything that holds a potential for uncertain outcome.
Will I lose custom coding by switching to the default theme?
You won’t lose any edits you’ve made to theme files by changing themes.
My concern is that when I reactivate the plugins (28) that information/settings will be lost.
The settings should be stored in your database. Unless the plugin has a feature that explicitly uninstalls it on deactivation, you probably shouldn’t lose any settings. Be mindful of deactivating any security plugins that alter your .htaccess file or re-write your login URL. That could cause an unintended lockout. Maybe save those for last if you’re using them.
When/if I find that plugin causing the deprecated message, what do I do at that point? Delete the plugin and find a substitute?
– Look for an updated version of the plugin.
– Look for a replacement
– Turn off error reporting and ignore the deprecated message.
https://en.wikipedia.org/wiki/Deprecation
