Just changing the original line:
'id' => $element['#id'],
with:
'id' => $group->id,
fixed the error for me.
| Comment | File | Size | Author |
|---|---|---|---|
| #7 | htmlids-2276443-7.patch | 1.26 KB | ethanhinson |
| #6 | htmlids-2276443-6.patch | 1.2 KB | ethanhinson |
| #3 | #id-field_group_pre_render_foundation_group_section_item.patch | 714 bytes | thim |
Comments
Comment #1
thim commentedHi Interdruper,
I have the same error but changing it didnt fixed it for me, any more ideas, that I can try-out?
Comment #2
thim commentedAny news on this?
Comment #3
thim commentedI have created a patch for this issue.
Since there is not always an 'id' => $element['#id'],
I took the $group->name to have a proper ID tag available
Comment #4
ethanhinson commentedChanges in the field_group module's processing of html IDs has caused this issue to surface itself on a number of sites we maintain at Bluetent. To keep a mix of both legacy support, and changes being adopted in the field_group module. I'd like to propose the following patch. First, we'll make the ID configurable via the admin UI. Next, if no ID is set, use the format of entity_type-bundle-view_mode-group_name. Note that what would have been underscores previously, now adheres to the field_group pattern of using dashes.
Comment #5
ethanhinson commentedAdded patch.
Comment #6
ethanhinson commentedPatch that applies against 7.x-2.3
Comment #7
ethanhinson commentedRerolled against dev head.
Comment #8
kevinquillen commentedHey Ethan, I went ahead and gave you commit access to this project. I'm juggling a bit at the moment and would take me some time to pivot around to this.