Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Hi all, I recently ran in to an issue involving a cck node export using the Features Module. The node type had several field groups containing multiple form elements. All of the field groups exported in the correct structure into the regular 'somefile.[*].inc' format as well as a separate file for all the form elements.
Here's the problem: when I add the module that 'features' generated (somegeneratedmodule.module) I get all my form elements back but not a whisper of a field group, I looked at the generated code and discovered that the exported field groups are all coded correctly but never referenced. A note to add is that their declaration is as objects that are passed into arras as opposed to arrays being passed into arrays (as in former drupal versions).
Hope there is someone with any insight out there as I'm hoping to include this in a live project. Cheers in advance :)
Comments
Comment #1
helmo commentedA bit late, but moving to the correct queue.
Comment #2
mpotter commentedFieldGroups can definitely have issues, but it seems like this was fixed recently. Confirm that you are using the latest version of FieldGroups module. You might also need to post this to their issue queue since it's a contrib module issue and not sure it's a bug in Features itself.
Comment #3
mpotter commentedComment #4
windmaomao commentedI had the same issue, the fieldgroup is exported correctly as far as i can see, it has all the information about which group contains which items, however the content type page doesn't show any group.
I'm using fieldgroup 1.1, and will try their dev version
Comment #5
kevinquillen commentedI am experiencing that sometimes you can export a content type and get the field groups. Other times, you don't get anything at all.
Comment #6
jhodgdonThis issue is actually a duplicate of #1619154: Fieldgroup exported feature reports as Overridden just after creating the feature, which has a lot more information about debugging the problem... I don't think it's been resolved yet.