Earlier quoted context omitted.
A version history sounds great, but it's not really the problem I'm talking about. I'm adding features and content to legacy Wordpress websites where the clients are liable to change config and add and alter content themselves via the admin portal. There seems no easy way to automate deployment from local development into production without accidentally erasing someone's changes, and to keep up to date with productio…
Do those client edits get persisted to files on disk? If so I'd be tempted to have a really shonky system - basically run a "git commit -a -m 'Updates' && git push" on an hourly cron, purely to capture their changes. Merging in changes made elsewhere would still be hard, but at least you would know what was changed by them and when.
Re: WordPress Core to start using SQLite
#71In Wordpress those changes get persisted to a MySql database, and now... SQLite? Seems like a lateral move. If they were files, it would be at least possible to diff against the production server, and to abort if there's differences since the last 'snapshot' (forcing the developer to pull them down at a later snapshot position)