It will over-write any database updates that have been made, so anything that’s been added or updated in pages, posts, menus, comments, users, etc, will all be over-written.
At this point there’s no way to “fix” that. There’s no database versioning system that’s even semi-reliable.
The only way to do it is to manually make the updates to the live site(s) that you made on the staging site(s).
Hi there!
In general, it would probably apply for the whole multisite installation, as it would be based on the installation instead of the subsite.
Also, the plugins/themes are set for the whole installation, and all the subsites share the same files, so I don’t even see how it would make sense working otherwise.
One of the options is to filter the database tables of the subsites, but I know that it might be too complex for some folks, and would be limited as file changes such as plugin updates would still apply for the whole installation.
If that is a problem for you, maybe you need a regular WordPress installation instead.
You could as well use the staging only for testing, and replicate the changes to the live site after fully testing.
(I ended up creating a similar answer as I didn’t see that @catacaustic was replying, but it’s what they said.)
