Only the status of the imported language is modified.

Created on 18 September 2023, about 1 year ago

acquia_contenthub_moderation's update on multi-language does not meet project expectations
If you only want to operate in the en language at the publisher site, and there are more languages at the subscriber site, it will break all other languages.
Our expected behavior is to target the content of whatever language is imported, not all languages.

💬 Support request
Status

Active

Version

3.3

Component

Code

Created by

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @leo liao
  • Open in Jenkins → Open on Drupal.org →
    Core: 10.1.x + Environment: PHP 8.1 & MySQL 5.7
    last update about 1 year ago
    424 pass, 1 fail
  • Assigned to kirti_garg
  • 🇮🇳India kirti_garg Delhi

    @leo-liao, We have gone through the description of the issue. Could you kindly clarify, what you mean by

    at the subscriber site, it will break all other languages

    .

    We have also gone through the patch that you have shared. On analysing that patch and running multiple combinations, we found that on the subscriber side after the import, forward revisions were created for the translations of the node. Please follow the below mentioned steps to replicate the issue.

    1. Create a node in en language on publisher and export it.
    2. On subscriber import the node and translate it to fr language.
    3. On publisher edit the same node and again export it.
    4. On subscriber after importing the node, for the fr translation forward revisions were created. Although they were not set as
      current revision

    After applying the patch, this issue goes away. Please confirm if the intention of the patch was to address the same issue.

Production build 0.71.5 2024