Hi. Using D8.3 on pantheon and field groups version 8.x-1.0-rc6 .

Installed the module, activated, then went to the Manage Display tab of my content type and clicked "Add Group". Selected type "HTML Element" and proceeded to name and define my group, including with a tad of custom css (style=" ").

Upon completing the add process, first thing I noticed is that the group does NOT appear anywhere on the Manage Display tab. So, I cannot place the group in a particular section. The group does appear as a parent one can select for another element, but that's it (and doing so causes an error of "Notice: Undefined index: name in Drupal\field_ui\Element\FieldUiTable::reduceOrder() (line 228 of core/modules/field_ui/src/Element/FieldUiTable.php)." . After searching, I suspect this is a result of whatever initial problem is causing the group itself to not appear in the Manage Display tab.

Of course, I also cannot edit or delete the group as another than the "parent" drop box, the group is no where to be found.

Thanks.

Comments

dwbotsch created an issue. See original summary.

michalczernik’s picture

michalczernik CreditAttribution: michalczernik as a volunteer commented

Exactly same issue here (Drupal Version: 8.3.4)

mennonot’s picture

mennonot CreditAttribution: mennonot at Congruity Works commented

I am having the same problem with Drupal 8.3.5, however I only have the problem with a new custom content type that I created. The "basic page" and "article" content types, which are provided out of the box do have the + Add Group button at the top of the Manage Form Display tab.

mennonot’s picture

mennonot CreditAttribution: mennonot at Congruity Works commented

I uninstalled Field Groups 8.x-1.0-rc6 and replaced it with Field Groups 8.x-3.x-dev and the Add groups button appears correctly as it should.

nils.destoop’s picture

nils.destoop CreditAttribution: nils.destoop as a volunteer and at Wunder commented
Status: Active » Closed (works as designed)

For drupal 8.3 and higher, you indeed need the 8.3 branch of fieldgroup. Core changed columns on the display screen, resulting in a different behaviour that is needed.

I added the documentation for this on the project page. Important to know: there is currently an issue with field layout module. An issue for this exists on #2878359: Field groups are not compatible with field layout

jimbullington’s picture

jimbullington CreditAttribution: jimbullington commented
Version: 8.x-1.0-rc6 » 8.x-3.0-beta1
Status: Closed (works as designed) » Active

I'm experiencing this problem with Drupal 8.4.4 - using the 8.x-3.0-beta version - any ideas?

jimbullington’s picture

jimbullington CreditAttribution: jimbullington commented
Status: Active » Closed (works as designed)

Nevermind - I'm stupid.

citronica’s picture

citronica CreditAttribution: citronica commented

I'm on Drupal 8.5.1 and running 8.x-3.0-beta1, and I got this to work by clearing the Drupal caches.

imperator_99’s picture

imperator_99 CreditAttribution: imperator_99 commented

Hi,

I'm also experiencing this issue on 8.5.3 and 8.x-3.0-beta1, however it only came up when I tried to nest a group in another group and saved the form.

Cheers,
Jesse.

imperator_99’s picture

imperator_99 CreditAttribution: imperator_99 commented
Status: Closed (works as designed) » Active
jchatard’s picture

jchatard CreditAttribution: jchatard at Breek commented

As imperator_99 reported, this issue still exists on:

* Drupal core 8.5.3
* Field Group 8.x-3.0-beta1

Any idea on what's happening here?

Thanks,
Jérémy

aerrasti’s picture

aerrasti CreditAttribution: aerrasti commented

Same problem here with Core 8.5.3 and Field Group 3.0-beta1.

Thanks

kamranafzal’s picture

kamranafzal CreditAttribution: kamranafzal commented

Same problem here with Core 8.5.3 and Field Group 3.0-beta1

AdamPS’s picture

AdamPS CreditAttribution: AdamPS at AlbanyWeb commented

I am also seeing an error with Core 8.5.3 and Field Group 3.0-beta1. However I don't think it is exactly the same as the original bug.

  • Matching the original bug report, I do see "Notice: Undefined index: name..."
  • However different from the original bug report, my field group was present in the "Disabled" region, and if I set it back to enabled, everything works.

The config when I had the problem was missing a line for "region:", and it was defaulting to disabled. I'm not sure how my site got in that state, but here's a guess. My memory is that in older versions of core, the region parameter was missing, and so presumably at some stage there was a migration hook to add the region parameter. I guess that field_group module did not have this migration step hence the field group was missing the region.

If I am right, then a possible fix is to write the migration hook and create a new version of this module. However there is a workaround, which is for the site admin use the manage display GUI to put the field group back into the enabled region.

Probably we should move this to a new issue, but I'm posting here for now as several others seem to have arrived here trying to debug their site.

justcaldwell’s picture

justcaldwell
he/him
Primary language English
Location Austin, Texas
CreditAttribution: justcaldwell commented
Related issues: +#2968184: The region part of entity view config isn't set for old installs

Same behavior described by @AdamPS in #14, though I think this may be a duplicate of The region part of entity view config isn't set for old installs, which has an RTBC patch.

AdamPS’s picture

AdamPS CreditAttribution: AdamPS at AlbanyWeb commented
Status: Active » Closed (works as designed)

@justcaldwell I agree, well spotted. Setting this back to the original resolution "Works as designed" as per #5 and matching comments #1-9.

Comments #10+ are actually a separate issue covered in #2968184.

grantkruger’s picture

grantkruger
he/him
Location Portland
CreditAttribution: grantkruger commented

Thanks justcaldwell for the pointer to 2968184. The patch there solved this problem for me for the 8.x-3.0-beta1 version on Drupal core 8.6.2.

BrightBold’s picture

BrightBold
she/her
Primary language English
Location Boston, MA
CreditAttribution: BrightBold commented

Another hat tip to @justcaldwell. The patch in the other issue (combined with a database update) fixed the problem for me.

jlab’s picture

jlab CreditAttribution: jlab as a volunteer commented

I am experiencing this issue again on Drupal core 8.7.10 and Field Group 8.x-3.0-rc2.

I will install dev and test if it solves the issue.

szeidler’s picture

szeidler CreditAttribution: szeidler at Ramsalt Lab commented

I also experienced various issues with the upgrade. Not on all of my sites and I actually haven't found the pattern. On the affected sites, the only option was to recreate the field groups from scratch.

lubwn’s picture

lubwn CreditAttribution: lubwn commented

Experienced that on Drupal 8.9.18 and Field group 8.3 branch. Solved by just clearing the cache as well.