Hi Richard,
I just sent out an email to another user encountering the same issue. This is new to me, and as more reports spawn in I’ll be sure to find the culprit sooner.
So far, 3 out of almost 100,000 users are encountering this, that’s about 0.003%; so I’m going to treat this as a corner-case.
It’d be helpful to know if you can trigger this issue consistently, so I may be able to replicate it.
This is what my reply read:
——
This issue isn’t often occurring, but when it does, it’s indicative a database schema error or a plugin conflict.
I believe you’re using the new block editor. If you hit F12 in your browser, you’ll find a “console” tab. Open that, and try to save. See if there are red warnings.
If that leads to nothing, do you have access to PHP and SQL error logs? You might be able to find something there.
Some plugins may crash or close PHP when saving the meta-settings; this happens after the post is updated.
A known plugin to do this is ‘Essential Grid’. See if deactivating non-essential plugins may resolve this issue.
If your website is hosted on a system that doesn’t have error correction enabled, a bit may be flipped erroneously (RAM fault), and that may turn off options in the database.
You’d want to compare your wp_postmeta database’s schema to what’s displayed here: https://codex.www.ads-software.com/Database_Description#Table:_wp_postmeta
And finally, WordPress 5.0 and 5.1 had issues forwarding metadata after you hit the “Preview” button.
This should’ve been resolved in WordPress 5.2.
—–
I hope this leads you in the right direction. I’d be more than happy to know what resolved it. Cheers!
