Field group Multipage with profile2 errors - simple hack fix [#2185819]

When using Field Group Multipage with Profile2 Entities, there is an error as Field Group is checking in #groups but the groups are in #fieldgroups. This causes errors to display and the count of total pages to be 0.

I've tested all versions and the problem persists.

I know the fix needs to be universal but for now I just needed a patch to make this work. I also haven't done much testing, so there may be other problems with this. Attached so other people may use it in the meantime.

Patch against 1.3

Comment	File	Size	Author
#4	field_group-multipage_profile2-2185819-2.patch	853 bytes	jami3z
#2	field_group-multipage_profile2-2185819-1.patch	734 bytes	leex

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Comment #1

leex CreditAttribution: leex commented 31 January 2014 at 00:45

Status:

Needs work

» Active

Comment #2

leex CreditAttribution: leex commented 31 January 2014 at 00:46

File	Size
field_group-multipage_profile2-2185819-1.patch	734 bytes

Comment #3

crystaldawn CreditAttribution: crystaldawn commented 13 June 2014 at 02:14

This exact same issue shows up when you have Profile2 displaying on the registration page. The issue there is that the multi-page form will not show AT ALL. This is because as the original poster here explains, profile2 uses fieldgroups rather than groups for an element. This was my quick hack to the field_group.module file right at the top of the field_group_fields_nest() function:

function field_group_fields_nest(&$element, &$vars = NULL) {

   //This is gives field_group.module compatibility with profile2 on the User Registration page -RyanC
   if (!empty($element['#fieldgroups']))
   {
      $element['#groups'] = $element['#fieldgroups'];
   }

  // Create all groups and keep a flat list of references to these groups.
  $group_references = array();
  foreach ($element['#groups'] as $group_name => $group) {
    $element[$group_name] = array();
    $group_references[$group_name] = &$element[$group_name];
  }

I use a custom module to monitor hacks like this, so hopefully the original poster's comments are taken seriously because it is definitely an issue. One could say that this is an issue with Profile2, but then Profile2 will just come back and say it's a field_groups issue, and then the vicious cycle never ends. I dont know who should take care of the issue, but it needs to be fixed by one of these modules.