Context:
It means that user sees a node in state 'A', change it to 'B', save and then he sees 'C' immediately.
WORKS-IN-PROGRESS:
No coding works.
The best result (being "$old_node" the variable holding the previous content and "$new_node" the one with data to be saved and "field_state" the name of the field) is achieved using:
PROBLEMS:
permissions: once a "permission error" was raised... we don't want to give users the permission to set nodes to state 'C' (it shouldn't be an option when editing)... this is a secondary problem. At first it seemed this was the real problem (there are some "user has no permission to set state to 'C'" but we cannot reproduce this again), but giving all permissions doesn't solve the next (bigger) one (and reverting to original permissions raises no other errors, anyway)
saving: 'C' state is not saved. It could be a matter of module's ordering (so that "workflow" save node with 'B' before the further update) but even changing module's weight worked at all.
Any solution to this would be glad.
Active
1.0
Rules
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.