Hi @rayeason
I might have missed something here, but when you say you don’t want the system to update anything automatically, it seems to me you could just set all the update settings to Manually update
or Disable auto updates
instead of setting them out to Disable core/plugin/theme translation updates
Thanks
Anthon
So do I select Enable all updates. Then simply select manually update for each of the update types?
I think I see what you mean.
I have set to enable updates and manually update.
Thanks.
Hello and good day.
For some reason, updates are still being automatically applied by wordpress even with the easy updater and manual updates enabled.
Does manually update not work?
Should I select disable updates instead?
Hi @rayeason
If plugins and/or themes still get updated even when Manually update
is already chosen for them, then you need to change the setting to Disable auto updates
, but please note that it’s not the Disable plugin/theme updates
. If you look at the Manually update
button settings for both plugin and theme updates, there is a question mark icon placed at the upper right corner of the button, and if you hover your mouse over the icon, you will see a tooltip saying Manually update your plugins/themes. Some auto-updates may still occur such as security patches.
. So even with the Manually update
setting, your plugins and themes could have their version updated to their latest, meaning that the Manually update
setting can be overridden by other plugins via appropriate filters.
We plan to make the Manually update
setting to be exclusive in a future release so that no other plugins can override the setting, which also means we will be going to remove the Disable auto updates
settings for both plugin and theme updates too as the setting will be just the same as Manually update
As for translation updates, I believe current release of EUM still has a bug in that area, a user reported that even when they set Manually update
or Disable auto updates
, translations will always get updated when updates are available for them. However, we already have a fix for this issue and it will be included in the next release.
Thanks
Anthon