Problem/Motivation

The D8 content translation model allows to create per-language variants of a single entity, as opposed to the D7 model that groupes separate entities (nodes) with different languages in translation sets.

When we come to revision support, the D8 approach is less flexible than the D7 one, as it can support only per-revision translations, while the D7 approach allows to have independent revisions for each translation.

Currently revision handling with multilingual entities is not working properly, both on the functional side and on the UI side, mainly because of the inability to deal with revisions independently for each translation.

Proposed resolution

Emulate per-language revisions at UI level by tracking which translations were affected for each revision, which allows to implement per-language revision listing, reverting, and comparing.

Remaining tasks

We identified the following issues:

User interface changes

TBD

API changes

None foreseen at the moment, just additions.

Comments

plach’s picture

Title: [meta] Make entity revision translation work » [META] Make entity revision translation work
Issue summary: View changes
plach’s picture

Issue summary: View changes
miro_dietiker’s picture

Possibly postpone the following issue?
#607396: Killer feature: Fieldable Fields in core

plach’s picture

Issue summary: View changes

I'm not sure I see how they are related, could you expand on that?

plach’s picture

miro_dietiker’s picture

Some more details about the reference #607396: Killer feature: Fieldable Fields in core
There are many projects like field_collection or paragraphs. They are introducing one new thing that is previously not seen in Drupal core UIs: A composite relationship with editability in one single form. None of these solutions completed both complexity dimensions revision and translation in its implementations, because it is a nontrivial task. All the implementation i've seen partially break revision or translation support.

Similarly, we should postpone the following issue until we have a working implementation for all the minimal revision + translation processes:
#1776796: Provide a better UX for creating, editing & managing draft revisions.

All decisions here (and in the sub issues) will affect how a proper solution in the two domains referred should be designed.

plach’s picture

Oh, ok, you were proposing to postpone the other issue, not this one. Sorry for the confusion :)

plach’s picture

plach’s picture

Issue summary: View changes
hchonov’s picture

#2428795: 'created' and 'changed' timestamps not correctly updated is now taking care only of the changed timestamps.

I created a new issue for the created timestamps with provided patch: #2472621: Translatable entity 'created' and 'uid' fields not initialized properly during content translation 'Add'

hchonov’s picture

Issue summary: View changes
plach’s picture

matsbla’s picture

Issue summary: View changes

I'm adding a new issue to make it able to save translations per language

plach’s picture

Issue summary: View changes

Removed the issue, as it was closed. See #2562759-2: Nodes revision cannot be saved per translation for details.

plach’s picture

Saving to see colors

plach’s picture

And again :)

plach’s picture

Category: Task » Plan
matsbla’s picture

One question:
Would it not make sense to see changes of statuses for the different translations in the revision log? Like if the translation is marked as outdated, or if the translation change their published/unpublished status.

Gábor Hojtsy’s picture

Issue tags: -sprint

Removing from sprint so it reflects what is currently being worked on.

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

moshe weitzman’s picture

Priority: Major » Normal

based on the little work remaining here (hurray!), I'm downgrading. Feel free to change it back if I am mistaken.

xjm’s picture

#2465909: Implement per-language locking at entity form level is the only remaining child issue, so maybe this one can be marked closed?

plach’s picture

Status: Active » Fixed

Agreed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.