Add test coverage for entities with unspecified language

I can confirm this bug. I just tried to add an entity reference field to a paragraphs type that references a Block entity, but it is impossible to add this paragraph due to the above stated errors.

I will also have a look at the code, but perhaps one of the maintainers has an easy fix right out of the box? ;)

Hey, just confirmed this.

• Paragraphs field on untranslatable node, uses empty Pragraphs entity.
• When trying to add anything, Console reports Internal server error.
• In the dblog, I find:

InvalidArgumentException: Invalid translation language (zxx) specified. i Drupal\Core\Entity\ContentEntityBase->addTranslation() (linje 826 i /home/foo/core/lib/Drupal/Core/Entity/ContentEntityBase.php).

Update: Setting the default node language is a confirmed workaround, though I'd love to not having to enable that :)

@farald, you can also use this workaround:

function HOOK_paragraph_create(\Drupal\paragraphs\Entity\Paragraph $entity) {
  $entity->set('langcode', Language::LANGCODE_NOT_SPECIFIED);
}

You might want to do some extra checks inside the hook to get the correct langcode if you don't want LANGCODE_NOT_SPECIFIED.

Getting this same error except on an site that is NOT multilingual.

Content of site was migrated from D7.
With the migration came a content type "Article".
Added a 2 text field Paragraph to this content type.
New "Articles", I can successfully add in Paragraphs with expected behavior.
Existing "Articles" (ones that came over in the migration), I receive this error in console when I press the add Paragraph button.

AjaxError: 
An AJAX HTTP error occurred.
HTTP Result Code: 500
Debugging information follows.
Path: /mySubdirectory/node/669/edit?destination=/mySubdirectory/admin/content&ajax_form=1
StatusText: Internal Server Error
ResponseText: {"message":"A fatal error occurred: Invalid translation language (und) specified."}

jeroen.b (#6)
I attempted to use your workaround however I am still receiving the error when editing nodes that were migrated from D7. New nodes of the same type have no issue with 'Paragraphs'.
I also tried 'LANGCODE_DEFAULT' as the language type as my site is not multilingual.
Just to verify your workaround is placed in xzy.theme file correct?

Any additional insight to get this module to work greatly appreciated!
Thanks.

@ksavoie, no, the code should be placed in a .module file.
HOOK in the function name should be replaced with the module name.

jeroen.b #6 works! Thank you!
The only addition I would add for the readers is that in your module make sure to include at the top

use Drupal\Core\Language\Language;

so your module has access to the 'Language' class.

I managed to fix this issue with the following patch. Not sure if it's the right approach. #6 didn't work for me (got the same error).

I was inspired by node module, which adds the source language as a field to add translation form and probably sets it on submit.

Well I spoke too soon. #6 didn't fully correct my paragraphs in my application and @Luxian's patch didn't work either.

I have some info that may shed some light.
In my install the majority of content came from a D7 migration. In reviewing different nodes the 'langcode' values are a mix between 'en' and 'und'. The D8 site is not configured as multilingual (Language not installed).

After some tinkering it appears this issue may revolve around this.
I enabled the Language module (with only English) and enabled language selection for content type 'page' (for which I have a Paragraph).
It appears that Paragraph fails when the the nodes langcode does not match Paragraphs default language.
When I change the nodes language to Paragraphs default it works.
b.t.w I removed both #6 and #11 fixes.

To work around the problem in my implementation, I enabled language selection on the Paragraph I created and the node types that have it implemented (/admin/config/regional/content-language) and set both Default Languages to "- Not Specified -" (which is what the majority of my nodes are). On nodes that come up as English I just update to "- Not Specified -" and Paragraphs works.

I hope this info leads to a fix!

Promoting for attention.
Still, we need test coverage for the issues identified.

Seems like a release blocking bug?

Is there anything I can provide that would assist in debug?

Here is a patch that works for me.
@ksavoie in your comment #13 it works because addTranslations is only called if your target langcode and default langcode are different so when you target to default as mentioned by you the content loads.

The patch in #11 did not work for me. The paragraph widget assumes that the parent entity is always translatable and tries to derive the paragraph language from its host entity. This does not work with ContentEntityBase. ContentEntityBase does not allow translations for locked languages. I tried to derive the paragraph language from the current language context if the parent entity is not translatable.

The patch in #11 did not work for me. The paragraph widget assumes that the parent entity is always translatable and tries to derive the paragraph language from its host entity. This does not work with ContentEntityBase. ContentEntityBase does not allow translations for locked languages. I tried to derive the paragraph language from the current language context if the parent entity is not translatable.

1. +++ b/src/Plugin/Field/FieldWidget/InlineParagraphsWidget.php
   @@ -731,7 +731,7 @@ class InlineParagraphsWidget extends WidgetBase {
          // Hide the button when translating.
   

   We should move the comment to addMoreAccess

2. +++ b/src/Plugin/Field/FieldWidget/InlineParagraphsWidget.php
   @@ -838,6 +838,14 @@ class InlineParagraphsWidget extends WidgetBase {
   +    // The from and the parent entity have a locked language
   

   Typo. The form ..

The patch in #22 fails if we try to add an untranslatable paragraph on a new node.

Now getting the paragraph language from current language if an untranslatable paragraph is added.

Also added test coverage for this.

Forgot to check whether langcode was set.

Opened a "multilingual workflow bugs only meta issue" #2698239: Multilingual workflow bugs for a "general" discussion for these kind of bugs.

This needs a recheck after the general multilingual fix.

duplicate.

It seems it has been already fixed in the Multilingual issue, but just to be sure, added tests taken from @tduong patch. Also tested manually, seems to be working fine now. :')

+++ b/src/Tests/ParagraphsTranslationTest.php
@@ -191,6 +191,12 @@ class ParagraphsTranslationTest extends WebTestBase {
+    $edit = array('langcode[0][value]' => 'und');

This should use the constant instead.

Changing to a normal task and updating title, issue summary should also be updated.

Patch fix according to #34

There we go.
I hope this is good enough :)

Good! Set to needs review for testbot test.

Rerolled.

Think looks good enough.

Thx, committed. :-)