Last updated 15 August 2017. Created on 27 May 2016.
Edited by cristiroma, kostask, adriancid, kmbremner. Log in to edit this page.


The Paragraphs module works within a multilanguage setup but there are crucial things which you need to be aware of.

Translatable paragraph fields on the parent entity are not supported. This might sound confusing or misleading, but it depends where the translatable option is enabled. It is totally legit, that the fields on the paragraphs item entity itself are translatable, but not the paragraph field on the parent entity (e.g. Node, Taxonomy term, ...).

An important note: When activating translation on the parent entity on the "Content Language" at admin/config/regional/content-language, the default setting of paragraph fields is the wrong one. You should disable the translatable option immediately.

To correctly enable the translation of paragraphs, click paragraphs on top of the page then scroll down (without saving!) near the bottom of the page and check the paragraph types you want to enable translation and each field for the paragraph type. By default all fields will be checked - which might not be correct!

Also never enable translation on the Paragraphs field (Entity reference revisions). As it will enable the possibility to add new paragraphs while translating, if an emtpy field (not containing any paragraph field) is on the translation source node - which is not supported !


I will try to highlight this with two screenshots what has to be avoided and what is the way to enable translatable paragraphs.

I will use my setup and configuration as an example. It uses a content type called "Article" (german Artikel) which fields can be found under /admin/structure/types/manage/article/fields.

In my case there are certain fields which are specific to the entity and there is a field called "Inhaltselemente" (field_article_paragraphs) which holds all paragraph elements. This field must not be translatable and therefore avoid checking "Users may translate this field" checkbox. See screenshot below.

not supported, translatable paragraph reference are not allowed

The multilanguage settings of translatable paragraphs content need to be made on the paragraph / on the paragraph fields itself.

E.g. I have a paragraph type called "Quote" (Zitat) which has certain fields. Those fields itself can be translated and is totally valid. See screenshot below.

supported, translatable paragraph field

To activate the multilanguage you need to go to: admin/config/regional/content-language check Paragraph

Search the Paragraph section and check the fields you want to make translatable.

Then go down and Save Configuration.

Looking for support? Visit the forums, or join #drupal-support in IRC.


penyaskito’s picture

See #2461695: Support asymmetric translations for an issue trying to solve this.

Christian López Espínola (@penyaskito)

divined’s picture

I get the folowing message on the the EntityReference field, not Paragraph field.

Paragraphs fields do not support translation. See the online documentation.

james.williams’s picture

Yes, that's what the screenshots show - that the error would show on the host entity's reference field to the paragraph. The fields within the paragraph are the correct place to be translated.


michaelsoetaert’s picture

I have the same problem.

I have followed this post and none of my 'Paragraph'-fields (Entity reference revisions) on my Content Types are translatable, but only the fields in my 'Paragraph'-types.

However the error is displaying on my normal 'Entity Reference'-fields (which have nothing to do with 'Paragraphs') and on my fields in my 'Paragraph'-types (which should be translatable according to this post).

Have you found a solution?

ycle’s picture

id like to check "users may translate this field" within the paragraph fields themselves - as described here.

but drupal doesnt let me do that. the respective checkbox is grey and it says "To configure translation for this field, enable language support for this type.". totally looks like screenshot 2 - but with a disabled (greyed out) checkbox.
hence i want to enable the paragraph support under /admin/config/regional/content-language - but drupal neither lets me do that. here, the respective checkbox is not grey, but is being reset after submitting the form. plus, its written "(* unsupported) Paragraphs fields do not support translation. See the online documentation." with a link directing me to this page.

so this is a loop now and i have no clue how to break out - maybe someones got a hint what im doing wrong?

mogio_hh’s picture

Same Problem here.

EDIT: CHECK FOR JS ERROR - that was my problem

marchellodepello’s picture

mogio_hh, I have exact the same problem.
Is it possible you provice some more info about what you did? I don't know what you mean bij "EDIT: CHECK FOR JS ERROR ".


I toggled 'paragraph' but this won't last, as you describe. But when I save there is a message "sucesfully saved." When I go back on this page 'paragraph' in not toggled. However, when I toggle it, and scroll down, there was a section 'paragraph'!
So I toggled the types and fields I want to translate, and save again. And what happend: this time is was saved! The toggle "paragraph" was toggled and the feelds I needed.
It works.. :-)

janes_p’s picture

Unfortunately save doesn't work in my case - getting an unspecific error:

The website encountered an unexpected error. Please try again later.

Drupal 8.3.7 with composer based installation, hosted by SiteGround.

Hints would be much appreciated.

janes_p’s picture

I tried with a minimalistic D 8.3.7 installation (SiteGround Softaculous) - this works. The issue appears to be an incompatibility with another module - any known problems? See below composer.json excerpt of my full installation:

    "require": {
        "composer/installers": "^1.0.24",
        "wikimedia/composer-merge-plugin": "~1.3",
        "drupal/core": "~8.3",
        "drupal/addtoany": "~1.8",
        "drupal/admin_toolbar": "~1.19",
        "drupal/auto_entitylabel": "~2.0",
        "drupal/bg_image_formatter": "~1.0",
        "drupal/bootstrap": "~3.5",
        "drupal/bootstrap_layouts": "5.x-dev",
        "drupal/console": "~1.0",
        "drupal/ctools": "~3.0",
        "drupal/ds": "~3.1",
        "drupal/entity": "~1.0",
        "drupal/field_group": "~1.0",
        "drupal/field_permissions": "~1.0",
        "drupal/fontyourface": "~3.0",
        "drupal/entity_reference_revisions": "~1.3",
        "drupal/paragraphs": "~1.1",
        "drupal/form_mode_control": "~2.0",
        "drupal/google_analytics": "~2.1",
        "drupal/inline_entity_form": "~1.0",
        "drupal/mailchimp": "~1.2",
        "drupal/pathauto": "~1.0",
        "drupal/page_access": "~1.1",
        "drupal/linkicon": "~1.4",
        "drupal/mollom": "~1.2",
        "drupal/fontawesome": "~1.2",
        "drupal/media_entity": "~1.6",
        "drupal/media_entity_slideshow": "~1.2",
        "drupal/metatag": "~1.1",
        "drupal/name": "~1.0",
        "drupal/rules": "~3.0",
        "drupal/social_login": "~1.3",
        "drupal/video_embed_field": "~1.5",
        "drupal/view_mode_page": "~3.0",
        "drupal/address": "~1.0",
        "drupal/views_bootstrap": "3.x-dev",
        "symfony/intl": "^3.3",
        "hoa/console": "^3.17",
        "guzzlehttp/guzzle": "^6.2"

EDIT: Could also be Drupal running low on resources

derek.deraps’s picture

As others mentioned, I check the box to enable "Custom language settings" for the Paragraph entity type, and then click save. However, on reload the box is still not checked. No JS errors for me... Hmm!

EDIT: I now understand what @marchellodepello was saying... If I re-check the Paragraph checkbox (but don't click save), the table of Paragraph fields to translate suddenly appears. Hoorah!

Derek "Hawkeye Tenderwolf" DeRaps
a Senior Architect
at Kalamuna

SoBiT’s picture

I have a content type 'page' like in your example. It holds a field 'content' which refers multiple paragraphs. Some of these paragraphs have fields referring to another set of paragraphs. These are not translated.

- Page (node, translated correctly)
- - Content (paragraph field, not translatable)
- - - Header Image (paragraph, all fields translated correctly)
- - - Row (paragraph, not translatable)
- - - - Column (paragraph, all fields set to translatable, but always overwriting the default language)

Am I the only one having this problem?

yoann.jean’s picture

I have same kind of issue here ... I don't understand why :(

yoann.jean’s picture

It appears that default language is overwritten when the parent paragraph has only 1 field, the one referencing sub paragraphs. When I add another one, the translation AND the original text are saved. Can you reproduce?

SoBiT’s picture

Unfortunately I cannot reproduce. How is your setup for that field? Is it translatable? Is the paragraphs field translatable (which seems to work sometimes and sometimes not)?

Looking forward to hear from you. We can maybe fix this :)

yoann.jean’s picture

Here is an example:
Without the field_title, elements referred through field_simple_cards were overwriting the default node ( even if its fields were marked as translatable ).

And yes, this "fake" field_title is marked as translatable, which seems to allow a specific operation on the referenced paragraph too.

I am using Paragraph Version: 8.x-1.0, Content Translation Version: 8.2.5,

SoBiT’s picture

OK, I can definitely not reproduce it. I have the exactly same setup as you, but I have the Content Translation Version 8.2.6

Also, Paragraph fields don't have the warning with '(* unsupported)' anymore. I've seen this before, but it's gone. I guess this could also be related to this issue. I'll check the release notes for the new version of Content Translation. Thank you. I'll share my results with you :)

Edit: Do you fill the field_title? Because I hide it in the form display and it's not marked as required. So it will always be empty. Maybe it needs content to trigger this strange behaviour? So do your titles have values?

yoann.jean’s picture

I did add some content, I thought it was needed to "trigger" this behavior.

SoBiT’s picture

This did work! I can now reproduce it.

I'm going to check the behaviour when setting default value, not required, hidden in form, and hidden in display. If this still works, we have a workaround - not nice, but it would help untill it's fixed :)

Edit: This did actually work too! I'm going to use this workaround. Hope it helps you too. If you have Sub-Sub-Paragraphs, remember that all Subs need to have such a field.

However, one of us should maybe create an issue for this, so that this bug can be fixed in the next version.

hugovk’s picture

Thanks for the workaround!

However, one of us should maybe create an issue for this, so that this bug can be fixed in the next version.

I've created an issue for this here:

SoBiT’s picture

Great, thank you!

stefvanlooveren’s picture

Maybe this can be useful: I have a patch for paragraphs 8.x.1.0 that supports multilanguage. Info & code:

tormi’s picture

You should use D.O issues tracker for patches to get your work reviewed and applied.

stefvanlooveren’s picture

Tnx, will do this as soon as I find the time.