Drupal core 8.4.2

Updated field_group module from 8.x-1.0-rc6 to 8.x-3.0-beta1. The form with two field groups displays and works as nicely as before. However:

When looking in admin/structure/types/manage/my_content_type/form-display:

Notice: Undefined index: name in Drupal\field_ui\Element\FieldUiTable::reduceOrder() (line 228 of core/modules/field_ui/src/Element/FieldUiTable.php). Get that two times because have two field groups configured. Seems similar to https://www.drupal.org/project/field_group/issues/2897967.

Fields that where previously under a field group are now listed on top without being under field groups anymore, still with indentation, and the two field groups are listed under Disabled.

However, as already said, the form displays and works as nicely as before!

For the sake of curiosity, even after saving these weird form display settings, the actual form displays nicely as before! And still I get these two PHP notice messages.

Then I rearranged things as they should be, by moving the disabled field groups back up in place. Interesting to observe was that the fields which were under field groups "magically" moved back in their right place -- if I correctly remember -- and upon saving the configuration also the PHP notice messages disappeared.

When I refreshed the actual form it still displayed nicely as it did before the module update. Again, the actual form was always displayed correctly, only in the "manage form display" configuration I observed above described weirdness.

Between all changes and observations I cleared all caches, but that never made a difference.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

hd created an issue. See original summary.

hd’s picture

Issue summary: View changes
Anonymous’s picture

Same issue Following

Maks’s picture

Same issue

Stefan Looij’s picture

Same issue (following):

I also have upgraded the field_group module from 8.1.x to 8.3.0-beta1 and experience the same behaviour.
Screenshot provided.

The edit-page display stays intact but the Manage form display is rendered in incorrect order, making it unmaintainable.
The fields are still indented, but the field-groups are all disabled.

I've tried to completely uninstall the module, losing all the field-groups and rebuilding the structure. Again with the same result.

I've tried to restructure everything to the new desired structure. Moving disabled field-groups to active again and place all fields back in the correct order. The field-structure gets stored correctly, but after saving the Manage form display, the page is back to the incorrect order.

I assume some related modules affect this display. Since i'm not experiencing this behaviour on other D8 projects that are using this field_group version. My complete setup is provided with the second screenshot.

vurt’s picture

Same issue here. I had to go back to version 8.x-1.0.

alxbridge’s picture

I was seeing this issue too: adding a region property to the config for all my field groups (as per this post) and reimporting config fixed it for me.

Thib’s picture

Same issue here. Field groups moved to disabled on admin/structure/types/manage/my_content_type/form-display but nothing changed on content form...

jim22’s picture

Same issue here when updating field_group from 8.x-1.0-rc4 to 8.x-3.0-beta1.

_dcre_’s picture

Same issue here

ABaier’s picture

Same issue for me.

ABaier’s picture

Solved it also by adding the region property to all fieldgroups, according to #7

sgurlt’s picture

Priority: Normal » Major
FileSize
144.02 KB

I have this issue even without upgrading from 1.0 to 3.0.
I just installed 3.0 and I am not able to move my field groups from Disabled to any region.
After moving them into a specific region and saving the manage form display form, the groups are moved back to the disabled area. I am setting the Priority to "Major" since this makes field groups unusable for me.

Watchdog does not show me any errors.
But the console shows me some errors, see the attached screenshot. I am wondering if this is my local error since: ERR_BLOCKED_BY_CLIENT ?

Update: I also just realised that in version ~1.0 the field groups got created directly within an active region while in ~3.0 they are created in the disabled region.

sgurlt’s picture

Priority: Major » Normal

Update 2: Wow seems like this was really a locale issue since my Adblock somehow blocked Ajax stuff ...

nils.destoop’s picture

Status: Active » Closed (duplicate)