I have a Drupal 8.6.3 site that is using translations. English and Arabic are the only two languages as of now. I'm having a problem with paragraphs not translating between the original, English node and then translated (Arabic) node.

Example: I have an "Info" page that has three fields: body, custom content, and sidebar. I enter English text in to each of the three fields and publish. On the published node, I click Translate and create an Arabic translation. I edit the translated node and enter Arabic in each of the three fields. When I publish the translated node the body shows in Arabic, but the other two fields are showing English text from the original node... I was expecting an all Arabic node.

If I go back and edit the Arabic node, the Arabic text is still visible in each of the three fields.

I've gone through /admin/config/regional/content-language and turned on Translations for the related paragraphs, but that doesn't seem to make any difference.

Should this work as I'm expecting?

EDIT: We're using panels/panelizer and just found this: https://www.drupal.org/project/panelizer/issues/2838638

  • Do not enable translation for the paragraph field itself (on the host node), only enable translation for the sub fields on the paragraph entity. – Hudri Dec 4 at 15:01
  • Also install this (fresh today) patch for ERR if you don't want your revisions to go missing from the UI: drupal.org/project/entity_reference_revisions/issues/3017718 – Clive Dec 4 at 15:02
  • @Hudri - If I'm understanding you correctly, I have done what you're suggesting. Example: For my "Body Custom" paragraph... if I go to /admin/config/regional/content-language, I have not checked the box next to Body Custom (* unsupported) under the Content group. However, If I scroll further down the page, under Paragraph > Content, I have checked the box next to Content (which is used in Body Custom). – pburgh Dec 4 at 15:41
  • This seems to be configured correctly. If you are not rendering your paragraphs "normally" (not something like {{ content.field_my_paragraph }} in your Twig template), make sure you are loading the correct language (e.g. Twig tweak module might have problems with entities in other languages). Otherwise it should work out of the box. – Hudri Dec 4 at 15:54
  • We do have a paragraph.html.twig in our theme, but it's pretty basic: {% block paragraph %} <div{{ attributes.addClass(classes) }}> {% block content %} {{ content }} {% endblock %} </div> {% endblock paragraph %} – pburgh Dec 4 at 16:02

Your Answer

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Browse other questions tagged or ask your own question.