Content Moderation + Content Translation = Crazy

Content Moderation + Content Translation = Crazy

As part of the Drupal Workflow Initiative we have critical issue relating to Content Moderation and translations. This is not actually a Content Moderation issue, but is just surfaced by Content Moderation because it allows you to create forward revisions. The video here should explain the issue:

Forward revisions + translation UI can result in forked draft revisions and Only having one default revision per entity forces translations to be kept in sync are the related core issues.

timmillwood Fri, 28/04/2017 - 16:08

Comment

Submitted by Agnar Ødegård (not verified) on Fri, 28/04/2017 - 19:36

Permalink

You have one field (revision) in the node table and you're trying to keep tabs on two or more pieces of information. You may succeed by creating rules to keep revision number across languages to be the same, but as you point out, when reverting revision for one language you really don't know the correct revision for the other language(s).

I think we'd avoid a lot of hurt by introducing a new table translation_revision. The id in this table will replace the revision id in the node table. The new table will know which revision is current for any language.

This will for sure break BC, but in the end I think it will be the cleanest solution.

Add new comment