Translation reference issue when cloning Site Studio enabled nodes

Created on 22 April 2024, 12 months ago

Problem/Motivation

When cloning content on a multilingual site the user is presented with the option to clone 1 or more translations ("Save cloned content with all translations").

When used with Site Studio this presents unexpected results.

Steps to reproduce

  • Create a node with a Site Studio layout canvas on a translatable node
  • Create a translation with a different number of components on the canvas
  • Clone the default translation and untick the "save cloned content..." option, do not clone translation.
  • Translate the cloned node, observe the wrong layout canvas has been loaded

Proposed resolution

tbd

🐛 Bug report
Status

Active

Version

2.0

Component

Code

Created by

🇬🇧United Kingdom 8ballsteve

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

Comments & Activities

  • Issue created by @8ballsteve
  • 🇮🇳India rajeshreeputra Pune

    I can confirm that this is not an issue with vanilla Drupal. I have conducted tests and was unable to reproduce the problem.
    Steps followed to verify:
    - install site
    - enable translations
    - download and install entity_clone
    - create & translate node
    - now clone original node with deselecting "Save cloned Content with all translations"
    - now translate cloned node.

  • Status changed to Needs work 2 days ago
  • 🇮🇳India rajeshreeputra Pune

    This issue arises when a node with translations is cloned without those translations.
    Cloning the node with all translations, then deleting and re-translating it working.

Production build 0.71.5 2024