Fatal error saving translation when content moderation is enabled

I wondered why paragraphs added to the layout were no longer appearing as translatable after setting up content moderation!

This patch fixes the issue. I can translate paragraphs again. Thanks!

Thank you for the patch. It works fine.

Thanks. I hadn't been able to upgrade because when i would go to edit the translated node, the paragraph content had completely dissapeared. This patch is working on 9.5/php8.1 with dev version of layout_paragraphs. I can now see, edit and save translated layout_paragraph content.

Hi, I'm using the patch with Drupal 10.1.1, Paragraph 8.x-1.15 and Layout Paragraph 2.x-dev. Will be committed on the project? It works good. Thank you very much.

I've found a minor issue: when a field inside a paragraph is marked as untranslatable, it should be hidden because what I'm experiencing now is:

1. Create the node
2. Translate it and edit a paragraph inside a layout paragraph. This paragraph contains an untranslatable field which is visible
3. Change the untranslatable field value
4. Save the paragraph: the error is triggered
5. Undo the paragraph edit and save the node
6. Edit again the node and change the untranslatable field, this time it works but now the two paragraph (the one in the original language and the translated one) are no more in sync.

I can confirm #15. I followed the steps and experienced the same results. The hidden field shows up when i go to translate the content.

In combination with https://www.drupal.org/project/entity_reference_revisions/issues/3150084 🐛 Non-translatable fields can only be changed when updating the current revision. Needs review , the issue in #15 should be partly solved.

Looked at this issue (briefly) again today.

It looks like the the "untranslateable field" value can be edited but not actually saved, no matter how many times i tried, which is good! The field is still visible though. I should also note that i was not able to reproduce step 6 from #15 anymore, but i used to be able to. Weird.

I couldn't discern any changes after appling the patch referenced in #20 to entity_reference_revisions. Field is still visible and still unable to save. I might be missing something that it's doing though.

Added MR as patch

Noting that this solution is the same as what's suggested at https://www.drupal.org/project/layout_paragraphs/issues/3397222 🐛 Widget is hidden if untranslatable fields are hidden Needs review , where I also updated the builder.js to pass FunctionalJavascript tests on the latest 2.0.x code. Once that is merged this should be updated as fixed as well.

Automatically closed - issue fixed for 2 weeks with no activity.