Hi,

I have a very strange problem:
I've updated the field_group module to version 3.0-rc1, run the update (which adds a region setting for every field group) and after that no field groups are rendered anymore, except for one node type.

I compared the field group settings, made them 100% equal, still nothing. Tried different field group types and a lot of different setting combinations, also no success.

What does work though is, if I edit the config yml and replace region "content" with something else. It doesn't even matter what I type in there, it can be "foobar" and then it works! (EDIT: it "works" in the display, meaning it looks visually correctly, but in the "Manage form display" it's broken)

I've checked my custom code to see, if there was some form alter hook that could lead to this, but didn't find anything.

Do you have an idea how that behavior could be explained or what I should try?

Comments

alex0412 created an issue. See original summary.

alex0412’s picture

alex0412 commented
Issue summary: View changes
alex0412’s picture

alex0412 commented

I've found the problem: the machine name of a field group must not be named "content"!

I didn't look into the code yet, so I don't know at which point exactly the error happens. But I tested it several times. Basically the name of the field group can be anything, except "content".

alex0412’s picture

alex0412 commented
Title: Field groups not rendered » Field groups not rendered if machine name is "content"
Component: Miscellaneous » Code
alex0412’s picture

alex0412 commented
Issue summary: View changes
swentel’s picture

swentel commented
Status: Active » Closed (duplicate)

closing in favor of #3075264: Fix upgrade path to account for DS regions - will check also when naming it 'content', that shouldn't be a problem by default - and if those pose a problem we'll have to start prefixing.

swentel’s picture

swentel commented
Related issues: +#3075264: Fix upgrade path to account for DS regions