While I still think that the revisions / content moderation support is still a hairy problem-space to tackle, maybe we should support translations out-of-the-box, based on the assumption that:

If an entity is used by any translation of the host entity, we should track that usage, pointing to the default language (non-translated entity) on the report page.

I was a bit reluctant to assume this ^^ until now, but once I see that core is doing the same for file entities (at least at this moment in time), it shouldn't be a big deal if we go the same route and provide at least the same level of functionality.

CommentFileSizeAuthor
#2 2921957-2.patch28.56 KBmarcoscano
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

marcoscano created an issue. See original summary.

marcoscano’s picture

Status: Active » Needs review
FileSize
28.56 KB

This apparently works for me.

  • marcoscano committed 855486d on 8.x-1.x
    Issue #2921957 by marcoscano: Fix the tracking on multi-lingual...
marcoscano’s picture

Assigned: marcoscano » Unassigned
Status: Needs review » Fixed

Committed #2 to have this available right now, but let's add tests for it in the follow-up #2922418: Refactor multilingual tracking.

Status: Fixed » Closed (fixed)

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