Louis’ point (correct me if I’m wrong) is ‘forced updates might trigger data loss’. Annoying, if not critical, for our client base (being businesses who dislike data loss).
James’ point (cmiiw) is ‘security is very important and should be forced in small updates’, which is for the same client base equally valid (being businesses who need a secure website and framework).
As the environment has seen plenty of back-up plugins and services, I wondered whether this could be a feature / important plugin in the ClassicPress environment to do this.
ACTION: If there’s an update that’s forced or pushed, it will first run a back-up based on settings user has defined first, then run the update.
Back-ups could be to a connected Dropbox / Google Drive / back-up-to-server, whichever. In my conception it could be something like https://nl.wordpress.org/plugins/all-in-one-wp-migration/ (which works for me as a back-up service as I periodically download the file to harddisk, and could restore with a clean WP installation + the plugin + the file. All themes, plugins and data are packaged.)
What do you guys think? Is it feasible? How does it play into ClassicPress’ strengths?