Field groups are missing in node translation forms

Just to be sure, is it visible as user 1 ? It is for me here, just want to be able to rule that out.

Interesting, I can reproduce, checking for patch.

The thing is that I don't even see a sidebar when fieldgroup is disabled too, so core hides/ignores some detail elements if you don't have many permissions when creating a translation, not sure why or what the logic is at the moment. But it isn't necessarily a field group problem at the moment. Will check whether I can still come up with a fix though.

Yes, I've added those permissions. I can access the translate screen, so that's ok.

It's ContentTranslationHandler::entityFormSharedElements that starts hiding elements - based on translation status and permissions. Will be tricky to get around that.

So it really is a core thing, but I can get around it. Patch isn't completely right though, but it's getting close.

Well, there should be an extra condition to check if we're on the 'add translation' route. I would also add an another condition which defaults to FALSE to expose this behavior because otherwise it might 'break' a lot of existing sites out there where suddenly the sidebar starts popping up. So something like this:

if ($is_add_translation_route && Settings::get('field_group_show_sidebar_on_translation_route', FALSE)) {
  // Rest of logic
}

Ok, looks good to me. I'll leave it to zuuperman to have a second check before committing :)

I tested the patch, and everything seems to be ok. Committed it to dev

Guys, thank you for the patch, it solved the issue when adding a new translation.
Would be great if we have the same behaviour also when editing an existing translation too (route name 'entity.node.content_translation_edit')

Hi. I know this issue is closed and outdated. I opened a new one, however I wanted to call this out here so it is in context.

// Move our hook_form_alter() implementation to the end of the list.

This was very heavy handed and broke code that we needed to run after this form_alter. We had it called out with module dependencies and explicitly setting the weight. This change completely took away our ability to control when our code ran.