Added by Boone Gorges over 2 years ago. Updated over 2 years ago.
Ray, I have a vague memory of debugging this in the past. Do you recall? It looks like statpress is basically abandoned, so we can probably fix it right in the plugin.
The plugin dev on the wp.org forums suggests deactivating and reactivating the plugin to update the DB schema upgrade.
Hopefully that fixes the problem. Not sure why this doesn't happen transparently.
Is the error message posted by Lihua only specific to site ID 695? Or are there more sites affected by this?
Thanks, Ray. I don't have access to the full logs, but I'm assuming it's not limited to that one site.
Here's a quick script for wp-cli.
Couldn't use StatPress' built-in DB function since it uses a constant to set the DB table prefix.
For the $site_ids variable, I installed the Plugin Activation Status plugin (not in Git), activated it on the development server and copied the site IDs. Dev server should use the most recent DB data, so we should be safe here right?
I just ran the routine and it appears to have worked. At least, it succeeded in changing the schema on some out-of-date tables. I assume this means that the notices will no longer appear. Let's mark resolved.