- 🇬🇧United Kingdom catch
I think this is probably a duplicate of 🌱 Make pre-save entity validation more commonplace (e.g., the default) Active now - the only way we can enforce this is on validation.
user a goes to node/1234/edit
user b goes to admin/content and unpublishes node/1234 via the checkbox.
user a saves node/1234 - it's published again because $form_state['values'] wasn't and couldn't be updated from the updated node.
No idea what to do about this, it applies both for direct database updates, which still happen in some places, and using the api via node_save(). If via node_save() we could compare timestamps and issue a warning. There's some form protection for cross-edits like this but nothing at the crud level at all.
Closed: duplicate
11.0 🔥
base system
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
I think this is probably a duplicate of 🌱 Make pre-save entity validation more commonplace (e.g., the default) Active now - the only way we can enforce this is on validation.