Notice: Undefined index: name in Drupal\field_ui\Element\FieldUiTable::reduceOrder() (line 228 of /var/www/html/docroot/core/modules/field_ui/src/Element/FieldUiTable.php)

I am working on a project that also has this issue.

Workaround (1) is very useful, thanks. I'm yet to experience (2), fields that won't stay under a tab, but it's early days.

Added patch from https://www.drupal.org/project/field_group/issues/2968184#16

Update: this doesn't fix the issue for us

I have gotten a similar error since upgrading from 8.1.0 to 8.3.0:

Notice: Undefined index: group in Drupal\Core\Render\Element\VerticalTabs::preRenderVerticalTabs() (line 82 of /usr/local/docroot/site/mysite-dev.edu/web/core/lib/Drupal/Core/Render/Element/VerticalTabs.php)

This occurs when users attempt to edit a node where I've set up a field group using vertical tabs.

Just chiming in that we also saw this when trying to update from 1.0 to 3.0-rc1. The Paragraphs patch listed as required does not affect the error and appears unrelated.

@timcosgrove, the paragraphs issue is related in a sense that it reproduces the error mentioned in this issue. The patch in that issue is indeed unrelated ;-)

Im totally unable to move a new field group out of disabled. Doesn't matter what I do. This is on a node form display.

There are a bunch of issues indeed with drag / drop and notices. I can also reproduce the tabs thing, it's super annoying .. :)
Going to fix them in #3075264: Fix upgrade path to account for DS regions
Also opened #3085858: Drag and drop acts weird, sometimes not resetting the parent, or even clearing the region value

I have been trying to follow the various related issues, but none seem to solve.

Ie, I still get Undefined index: name in Drupal\field_ui\Element\FieldUiTable::reduceOrder(). Steps to reproduce:

1. Enable paragraphs module
2. Create custom form mode for paragraph
3. Manage form for a paragraph type and enable the custom form mode
4. Manage form on the custom form mode, name is missing

Example array passed to reduceOrder

array(
  'children' => array(
    'group_conditions' => array(
      'children' => array(
        'field_condition' => array(
          'name' => 'field_condition',
          'weight' => '0',
        ),
      ),
    ),
    'group_content' => array(
      'children' => array(
        'field_layout' => array(
          'name' => 'field_layout',
          'weight' => '0',
        ),
      ),
    ),
  ),
)

So only key available is children while a key name is expected.

Should I post a new issue?

Well for now will just leave this patch here, happy to move to a new issue, but definitely still reproducible as per above. This patch just provides extra '#name' attributes for the tabs and tab FieldGroupFormatters so that core field_ui module is able to handle sorting. Not a long term fix; just avoids the notice.

Seems like it's a problem with all of the filed group formatters, Attached is a patch for the HTML Element.

D9.1.5 and field_group 3.x-dev
I am using details and I have added the '#name' key everywhere in Details.php as per #16 and #17 without luck.

Here is the core function producing the error:

 public static function reduceOrder($array, $a) {
    $array = !$array ? [] : $array;
    if ($a['name']) {
      $array[] = $a['name'];
    }
    if (!empty($a['children'])) {
      uasort($a['children'], ['Drupal\Component\Utility\SortArray', 'sortByWeightElement']);
      $array = array_merge($array, array_reduce($a['children'], [static::class, 'reduceOrder']));
    }

    return $array;
  }

My feeling is that if ($a['name']) {..} should be if ($name=$a['name']??FALSE){$array[]=$name;} or like this. This is because I can't think of a case where $a['name'] is set and not TRUE
Could it be a core bug?

I my case the 'name' key was not set (only $a['children'])

any update?

I bypassed by replacing
if ($a['name']) {
by
if (!empty($a['name'])) {

I used this fix to hide error, i continued on editing and after saving, i restored

Ive match the patch for this comment. #21

@peonboyos I used your patch in #22. Took me a second to realize to apply it to core and not field_group. It did get rid of the error. The site seems to functioning well so far with this core change.

Seems that this issue is still present, it's not a duplicate and the #22 patch it's working for me. I hope I edited the issue metadata correctly. Re-opening the issue.

+1 and thanks for the patch - works for me!

Problem experienced for me on 9.2.7 as well, while creating a new field_group. Patch applied to Drupal core without fuss. Error went away.

Thanks for the patch!

I tested with and without the patch (see screenshots). Code change is very simple and makes sense. Marking RTBC.

This could use some test coverage.

I took a crack at writing a unit test for this. It's pretty straightforward. No mocking or anything.

The third case is going to trigger a failure. I tried to make a "realistic" case by following #19:

I my case the 'name' key was not set (only $a['children'])

Changing version to 9.4.x too.

The test failed at the right place with the right message so I'm removing the Needs tests tag.

Here's a patch that includes the fix from #22.

Applied patch from #30 without hassle on 9.2.10, error gone, seems to work as expected. Thanks!

+1 patch #30, thanks for the patch.. works.

hi #30 looks to be ok for me too on

D8.9.20 thanks

Patch in #30 applied cleanly to our Drupal 9.2.9 site and resolved the warning/issue.

I believe the below has to do with our composer patch setup and not the patch itself. Please ignore below.

For anyone who does run into the issue I was having below see:
- https://github.com/cweagans/composer-patches/tree/1.x#allowing-to-force-...
- https://github.com/cweagans/composer-patches/issues/43

Scratch that. We applied the patch with the composer and the test file was placed in its own directory instead of being added to the field_ui module.

Instead of adding the new test file to: core/modules/field_ui/tests/...

It created the following path and file : core/b/core/modules/field_ui/tests/...

The change to the FieldUiTable.php file was applied cleanly in the correct directory.

Tests failed and passed as expected. Patch applies. Previous to tests was RTBC. Back to RTBC.

Committed/pushed to 10.0.x, cherry-picked to 9.4.x and 9.3.x,thanks!