- Issue created by @ethomas08
For my team's project, we noticed that all fields attached to a node were checked for whether or not translation was enabled, but not fields that were used for our custom layout paragraphs setup.
We have a field called Body Components that link to different paragraph types that can be referenced by a node.
Each paragraph type is configured, field by field, whether to be translatable or not at the "admin/config/regional/content-language" route.
When submitting a job for translation using TMGMT Microsoft, there were occasionally jobs that would fail because of a character limit error. I thought it might be related to this issue, but it was not: https://www.drupal.org/project/tmgmt_microsoft/issues/3149941 📌 Allow to overcome character limit, translate only text Needs work
It looks like the actual problem is that some of the fields being translated cause database errors. When looking more closely, I can see that those fields are not enabled for translation. They do not display as translatable in the TMGMT settings form. But they are still being pulled in for translation.
Add an extra check for which fields are translatable before running a translation job?
Active
1.0
Core