Plugin Updating Automatically with Auto-updates Disabled

I can confirm that.

Must be a forced update fixing a severe security problem. WordPress has a mechanism for that and wp.org uses it from time to time if a plugin has a sever exploitable problem.

But it is not only this plugin which got updated. There was also a forced update to another Google Analytics plugin from the same developers last night.

• This reply was modified 2 years ago by j.hoffmann.

I also got this, I don’t use auto-update it can break the site without notice

+1 and nothing in the changelog security related.

Same for my site – it auto-updated even though I have it set for manual updates.

@crdunst they might hold off with publishing security related details until the update has been rolled out to most sites.

Same here

We also saw this behavior and are looking for an explanation.

Same here. I suspect it’s a bug due to the plugin trying to control update behavior as a setting for the plugin rather than by using the built-in WordPress plugin update setting. This allows them the flexibility to allow “minor” updates, but if you disable it completely the setting is not respected though.

Hi there,
While we didn’t change any code with regards to our auto-update setting, there is an unfortunate bug in it that caused the set value to be ignored that’s been there for years but never been hit due to the version number.

We’ll have this corrected in our next version,

While our setting does allow for the addition of the minor updates, our plugin offered the ability for users to opt into auto-updates years before WordPress had that feature built into core, so a huge amount of our users rely on that feature to get them.

-Chris

Thanks for the info. Just for reference. Is this affecting all sites with this plugin or is it only affecting sites that have been updated to WordPress 6.1 or a certain version of MonsterInsights?

The issue isn’t dependent on the version of WordPress or MI.

Notably, the bug will only auto-update MonsterInsights. Our code from the beginning was designed to ignore all other plugins on the site since our setting was only for our plugin.

What we’ll be doing is issuing a new version tomorrow (8.10.1) that fixes the comparison. After which everyone will be good to go from that point forward.

-Chris

• This reply was modified 2 years ago by chriscct7.

My apologies but want to make sure I’m following. Previously you said the following:

“there is an unfortunate bug in it that caused the set value to be ignored that’s been there for years but never been hit due to the version number.”

This seems to have started on my sites at least after updating to the latest version of WordPress.

Is it dependent on version number?

• This reply was modified 2 years ago by Marius L. J..
• This reply was modified 2 years ago by chargeup.

It’s not dependent on the version you have installed on a site, it’s dependent on what the www.ads-software.com API believes the latest version number of the plugin is, regardless of the version of MI actually installed.

Got it. Thanks for the clarification.