Problem/Motivation
Let's have a multilingual site & node with more than 1 language (i.e. node is translatable): EN & DE.
Also enable Workflows module to have draft & published states.
We have 2 published revisions for EN & DE languages.
Then we create new revision of node with EN language but do not publish. Database containt up-to-date value for e.g. field body.
After it we create new draft revision of DE node.
Database contains value for body field for EN node from previous published (default) revision.
Drafts with different languages of one node should not revert another draft to previous state.
It also affects JSON:API.
There are a lot of possible related issues I guess:
#2875861: Optimize updating data and revision data tables
#3023194: [PP-2] Add parallel revisioning support
#2795279: [PP-2] [META] Revisions support
#2833084: $entity->original doesn't adequately address intentions when saving a revision
#2833049: ContentEntityBase::hasTranslationChanges will compare a forward revision with the default one instead of the newest forward revision
#2477419: Codify mechanism to set a forward revision as the default revision
#2960887: Do not create field revisions when field data hasn't changed
#2769741: Node revisions page might not list a default revision
#3056440: Cannot add new translation if the latest affected translation revision of the source language is older than the default revision
#3080995: EntityRepository::getActive does not return a translations most recent revision
#2815949: It is not possible to know if a revision was once the default
#2766957-176: Forward revisions + translation UI can result in forked draft revisions - potential root cause
How to reproduce
- 1. Add 2 languages to site (EN and any one).
- 2. Make "Article" node revisionable & translatable.
- 3. Create Moderation Workflow with: draft, review, published states.
- 4. Create Published revision of node with default language: body field text = "published default"
- 5. Create Draft revision of node with default language: body field text = "draft default"
- 6. Verify database table "node_revision__body", created node has body_value = "draft default" for default (en) language
- 7. Create Published revision of node with non-default language: body field text = "published translation"
- 8. Create Draft revision of node with non-default language: body field text = "draft default"
- 9. Verify database table "node_revision__body", created node has body_value = "published default for default (en) language
Visually database will look like:

Revision 9659 contains new EN content but reverts RU to previous published.
Revision 9660 contains new RU content but reverts EN to previous published.
Revision 9661 contains new EN content but reverts RU to previous published once again.
Proposed resolution
TBD
Remaining tasks
TBD
User interface changes
API changes
Data model changes
| Comment | File | Size | Author |
|---|---|---|---|
| node-revisions-translations-override.png | 98.35 KB | dmitry.korhov |
Comments
Comment #2
dmitry.korhovComment #3
dmitry.korhovComment #4
dmitry.korhovComment #5
dmitry.korhovComment #6
dmitry.korhovComment #7
dmitry.korhovComment #8
dmitry.korhovComment #9
sam152 commentedComment #10
sam152 commentedComment #11
catchMarking duplicate of #3026882: Content moderation workflow changes against one language affect translations too.
Comment #12
dmitry.korhovInstead of just closing this issue please update description in #3026882 with details from this issue
Comment #13
catchDone.
Comment #14
dmitry.korhovCool, thanks!