The relevant place in functions.php is used to load data from plugins. Therefore, my guess would be that something in your project is trying to retrieve data for the plugin, which does not exist.
To find the cause, I would recommend deactivating all plugins. Does the message still appear in the log? If not, one of the plugins was to blame.
A test change of theme could also be useful to rule this out as the cause.
By the way, the plugin mentioned is a completely outdated plugin for displaying weather information. Perhaps this will also help with the search.
@threadi Thank you for your response.
Your suggestions were all tried before making a post.
The warning log messages all point to plugins that DO NOT exist in the system. I do not get these warnings about currently installed plugins either activated or deactivated.
It has been suggested that WordPress has not correctly recorded the removal of these plugins years ago when they were removed from the system. This would have been at least 4+ years ago before my time, so I cannot confirm how they were removed back then.
So far, the best suggestion I have gotten was to add the plugin back onto the system and then remove it the standard way to see if it updates the WP plugin tables in the database.
Where would I even look in the WP database for old plugin install records?
Thank you,
-
This reply was modified 1 year, 11 months ago by
Battlecat.
There is an options table in the WordPress database. This should contain a data record with the option_name ‘active_plugins’. You can take a look at its value. But this should actually correspond to what you see in the plugin list in the backend.
My guess would be that some plugin or the theme is calling the function directly. That would be unusual, but unfortunately you come across a lot of things in the WordPress world. You would have to search through the files of your project (download them all and search for the plugin name in them).
@threadi Thanks for the advice.
I went the other route suggested to me, which was to re-install the plugin network wide and then disable and then remove the plugin. So far, for the plugins I have done this to, the errors / warnings have stopped popping up in the logs. At least at this time. We shall see.
I realize that this is the new fast technical way of dealing with it, but it seems to be the most time efficient and that is more important at this point.
Best,