dkilgoesc13

Agreed. Wordfence made a few vulnerabilities public this morning.
https://www.wordfence.com/blog/2022/02/critical-vulnerabilities-in-php-everywhere-allow-remote-code-execution/
Going back pre 3.0 isn’t a good option.

That’s pretty evasive. Please elaborate on the incident and the risk to any sites running this plugin.

Manually adding the columns did stop the errors.

You took the time to respond so I wanted to provide feedback on the upgrade process from 2.8 to 3.9.4

I made a new wordpress install, then installed slimstats 2.8.
That made my db tables look like the live site.
Then I manually installed slimstat 3.0 by replacing the files.
(Using the delete/install feature would have wiped out the existing tables.)
Then I activated the plug-in and it did not add those columns to my instance.

(I noticed those columns were already present in 2.8.4 so perhaps my original install was so old its not really a good test.

My fix for this issue was to do a fresh install of wordpress and slimstat and then compare the schema of my live database and the test one, making changes to live as needed.

I’m all fixed up. Thanks for the help.

Adding the columns is easier. Thanks.

I guess I did miss a step.
I did not install version 3.0 before installing 3.9.3

Is this the correct link to v3.0?
https://downloads.www.ads-software.com/plugin/wp-slimstat.3.0.zip

It was 2.8

Are the missing plugins ‘network activated’?

In my case I have 20 plugins total and only 9 of them aren’t network activated and those are the 9 that show up in the ‘plugin management’ control panel, which makes sense now.

Network enabled plugins are already being managed by wordpress. This module enables you to provides more granular control over modules in a multi-site network. In reality, if you’re using this plugin you probably shouldn’t have any plugins network activated except for ‘multisite-plugin-manager’.