Widget is hidden if untranslatable fields are hidden

I'm facing the same problem. Since we are using the content moderation workflow, I need to activate the Hide non translatable fields option. Any ideas on how we can solve this issue?

@InaW I didn't find a solution to this particular problem yet. Instead I decided that editors on our platform actually probably want asynchronous translations, that's why I enabled translation on the paragraphs field instead, despite being unsupported. However in your particular case, there's no solution for that and I think there should be.

I had a look at the paragraphs widget implementation and they solved this issue like this:

  public function form(FieldItemListInterface $items, array &$form, FormStateInterface $form_state, $get_delta = NULL) {
    $elements = parent::form($items, $form, $form_state, $get_delta);
    // Signal to content_translation that this field should be treated as
    // multilingual and not be hidden, see
    // \Drupal\content_translation\ContentTranslationHandler::entityFormSharedElements().
    $elements['#multilingual'] = TRUE;
    return $elements;
  }

I have adopted the solution to Layout Paragraphs and created a Merge Request MR!145.
This solves the problem for me and the widget is now displayed in the Translation when I have "Hide non translatable fields on translation forms" enabled.

@InaW sounds promising!
When I tried something similar, I ran into issues when I saved the node - Drupal threw an error that "untranslatable fields cannot be changed and must be changed on the original language" or something similar... Did you test that solution? Works fine?

@florianmuellerCH yes I did some testing, and the Patch works well for me so far. I can update the content of the paragraphs in the translated node and save them afterward without any issues.

I'm using for testing Layout Paragraphs 2.0.3 with Paragraphs 1.16.0 and Drupal Core 10.1.6

The snippet in #5 worked for me. I'm attaching it as a patch for the convenience of others that may need it until the MR can get merged. Thanks @InaW

@justin2pin This looked good, although I discovered that FunctionalJavascript tests were failing with the latest 2.0.x code.

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