WordPress version update schedule default = always update?

markus

Hi,

is it possible to change the default when adding a new website to enhance to "update only to minor versions" other than think about it and do it manually all the time?

Thank you

DracoBlue

Orlando

DracoBlue He means if there’s a way to make it so that all new WordPress installations have updates on as default, not just a single one.

nhybgtvfr

even better, is there a way to stop wordpress auto-updates completely without manually editing the wp-config.php file?

any single core/theme/plugin update has the potential to break wordpress, and the auto-updates don't give any control over when an update is actually installed, or creates a backup prior to install, doesn't even give any notice that an update is about to, or has just been applied, leading to lots of wasted time trying to find out what changed.

much like can be done with ubuntu unattended-upgrades, i'd much rather be able to configure it so that updates are only ever applied on a known fixed schedule.

adil

nhybgtvfr

Enhance only auto update WordPress core, not the plugins/themes.

And for The WP Core you have the option to only enable auto updates to minor versions, which should be good and don't have any breaking changes in most times.

nhybgtvfr

i know, i just don't like anything changing by itself, especially at random times.

i currently use infinitewp to control wp updates, but i'll probably end up making a small bash script using wp-cli
to update and backup wordpress.

something along the lines of:
wp core version >> ~/wpupdates wp plugin list >> ~/wpudates wp theme list >> ~/wpupdates wp db export ~/db-$(date +%F).sql tar -czf ~/wp-backup-$(date +%F).tar.gz . ~/db-$(date +%F).sql rm ~/db-$(date +%F).sql tar -czf ~/wordpress-files-backup.tar.gz ~/public_html wp core update wp theme update --all wp plugin update --all wp update-db

although most probably have incremental backups running often enough to forego having to create a separate backup as part of the update script... and just have the script run on a cron.
the 1st 3 lines are just to keep track of what changes would be applied