Contrib.social

Automatic translation affects non-translatable fields

Open on Drupal.org →
Created on 31 October 2023, 8 months ago
Updated 13 November 2023, 7 months ago

Problem/Motivation

When creating automatic translations, fields that are not configured to be translated still get translated which causes the original piece of content to have translated values.

Steps to reproduce

Configure a Content Type to have (at least) one non-translatable field. Run automatic translation for a node of that content type and the non-translatable field will still get translated therefore changing the value of the original content as well.

Proposed resolution

Only fields configured for translation get translated. I've quickly created a patch proposition attached in the files section.

Issue described above. Screen shots show original content before and after automatic translation.
Kind of seems odd to me that this wouldn't be included in the, otherwise, really amazing module so please feel free to instruct me if I'm missing something. Cheers

🐛 Bug report
Status

Fixed

Version

2.1

Component

Code

Created by

🇭🇷Croatia abaudoin

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

Comments & Activities

contrib.social Blog FAQ Discussions
Production build 0.69.0 2024