I've created a workflow with the module 'workbench_moderation' to translate nodes.
When a node (eg. book page) A gets the status 'needs translation', the translator uses the common node tab 'translate' for translating the fields.
When he saves the translation, the field data is saved in:
- the tables field_data_XX for node A (and revision 1)
- the tables field_revision_XX for node A (and revision 1)
When there is just one revision, there is no problem.
Then, revision 2 is created as a draft (not published) (summary in workbench_moderation_node_history and data in field_revision_XX). When this draft (revision 2) is again presented at the translator and he saves the translation, the field data is saved in:
- the tables field_data_XX for node A (and revision 1)
- the tables field_revision_XX for node A (and revision 1).
Expected behavior:
- only the tables field_revision_XX should be updated for node A and revision 2.
Tables field_data_XX should only be updated on publishing revision 2.
Thank you for any suggestions?
Needs review
1.0
Base system
The change is currently missing an automated test that fails when run with the original code, and succeeds when the bug has been fixed.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Assume this is a feature req. and as most of them, they are not critical. As the assigned person have not posted on about 7y, unassigned
For our use case, when doing side by side node edit form with two or more languages using the entity_translation_unified_form module (still stable for D7) comment #82 still holds.
#1707156-82: Workbench Moderation integration →
does the job.