Allow having multiple group-audience type fields

Looks very interesting - happy to help test it out!

Looks interesting. I checked out the repository and gave the branch a try but am getting an error when I try and edit the audience field after attaching it to a group content node type:

EntityMetadataWrapperException: Missing data values. in EntityMetadataWrapper->value() (line 83 of /Users/ssetvik/Sites/h/public/sites/all/modules/contrib/entity/includes/entity.wrapper.inc).

Tested a few demo use cases with the new branch and they worked for me. I'll try it with real world use cases later on.

Making use of different membership types definitely makes sense to me. From what I can see so far, several API functions and integrations (like Rules) need to be adapted to support different membership types and maybe we should have several 'og_membership' entity properties, but these changes can happen once the basic code is committed.

Great job. I am waiting impatiently for the results.

Hm... I don't really get it. My use case: I want to different membership types:

1.) followers of a group who can't post new content
2.) members who can post content.

How can i achieve that?

That use case is unrelated to this issue I think, but what you describe is quite possible using the OG 7.x group roles and group permissions (you can set these globally, or delegate so that each group can set their own).

baaah. Hitting me hard for using dev in production :) I reverted to 1.3 using the script (i did some changes). And i needed to add the name field to the og_member table

Updating status. To confirm, this is why one can't currently restrict a user to posting content in just one group if they have creation rights in another? Will try looking at Prepopulate and hiding the form element as a temp solution for this.

What's up with this issue? Is it still the way #1269176: Limitation of Group Audience? is supposed to be fixed one day?

OK, thank you for your answer. Then I'll try to set a custom validation handler in a form alter, as 2.x is not ready for production.

Does this give multiple audience (by contenttype) selections when creating node?
Case:
I have two (group)content types region, city.
Now when I have a region and city with the same name I can't see witch one is region or city.

For 2.x I don't know, but for 1.x you can use this hook:

/**
 * Implements hook_og_audience_options_alter().
 */
function YOUR_MODULE_og_audience_options_alter(&$options, &$opt_group, $account) {
  $allowed_types = array(
    'city' => array('school', 'stadium'),
    'region' => array( 'university'),
  );
  $content_type = _YOUR_MODULE_get_type();
  $gids = &$options['content groups'];
  foreach ($gids as $key => $gid) {
    $group_node = og_load_entity_from_group($gid);
    if (is_object($group_node)) {
      $group_type = $group_node->type;
      if (!in_array($content_type, $allowed_types[$group_type])) {
        unset($gids[$key]);
      }
    }
  }
}

/**
 * Helper function to know what the group audience field refers to.
 */
function _YOUR_MODULE_get_type() {
  $args = arg();
  if ($args[0] == 'node') {
      if ($args[1] == 'add') {
        return str_replace('-', '_', $args[2]);
      }
      else if (intval($args[1]) && $args[2] == 'edit') {
        $node = node_load($args[1]);
        return $node->type;
      }
  }
  return FALSE;
}

Not with 2.x, can't find something similar :(

Since #1342632: Deprecate OG group entity has gone into 2.x, would it be possible to get this back into 1.x? I'm trying to create memberships between an entity and any subgroups of the group that the entity was created for and I want to use a different membership type so that I can tell which group is the actual "owner" of the entity and which ones it is simply "visible" to. I have some additional features to implement in the near future where I would like to be able to use different membership types and it seems like this is required to make that possible.

Hi, on post #5 a patch is mentioned to allow users to join with different membership types (by means of a plungin for panels).

Has this patch been included in 7.x-2.0-beta3 or 7.x-2.x-dev?
It seems not or am I not able to use this feature?

Where can I find the patch? I don't find it in Git.

Many thanks in advance.
Tommaso

Anybody have any idea what happened with this? I've tried adding multiple group-audience fields and it has issues loading permissions/roles at this point for the second field. I get

Warning: Invalid argument supplied for foreach() in element_children() (line 6370 of /includes/common.inc).

on the OG permissions page, and "Access Denied" on the OG roles page.

In the second group's permissions page (from the group), I get:

Notice: Undefined index: map in og_context_handler_node() (line 417 of /sites/all/modules/contrib/og/og_context/og_context.module).

Ok, this is sort of working, but to get it to work I had to create a group, add permissions and roles, add it as a reference to a group-post-type that wasn't doing double-duty, THEN add it as a second field to a different group-post-type, at which point roles/permissions worked fine. It seems it doesn't build the role-map properly otherwise.

Updated issue summary.