Add rule action to create OG Vocabulary

I was trying to do this as well, and could not find any incantation to persuade rules to do this. So, I created a rule action for adding a new OG vocab to a group that meets the use case suggested by OP.

Thanks, but the rule action should be against OG 2.x

setting status - really the rule should have a way to affect the widget options too, but I don't have time work on adding that...

Ok, sorry thought it was against 1.x. Back to needs review.

#1 patch works

for me too.
thanks

Has anyone figured out how to set the status to Enabled?

I had to hack the actual og_vocab module to do this as I couldn't determine how to override $og_vocab->is_new.

My issue now is that whenever I create a new og node, it displays EVERY vocabulary on the screen. It seems like it's adding the Entity Reference to OG_vocabulary back to the content type every time I save. I've deleted it from the content type itself as well as from the admin/config/group/fields screen.

Nevermind, it was how I was setting the status to 1 that was causing an issue. I removed that from this patch and just hard coded the default value of status to enabled and that seems to be working. I don't anticipate disabling it so I won't work on a work-around at this point.

Update:

Nevermind, it still shows any OG Vocabularies when I use the rule to create them. It also automatically adds the OG Vocabularies widget to the group content type.

--James

Thanks so much for the patch. I'm currently testing it out now. Would it be possible to also include a rule to automatically delete the vocab and all terms when the OG gets deleted?

I'm currently using https://drupal.org/project/OG-Delete to delete all associated nodes already.

Thanks in advanced.

NWOM: let's try and get this patch reviewed and in on its own merits, and deal with any other rules as separate feature requests.

Do you think it should separate the Name/Machine Name in the action, not just automatically generate the machine name?

#1 patch worked for me

Would be extra awesome if this action also provided a variable for the created vocab too!!

Patch #1 will associate a vocabulary to the group but the use of this vocabulary on group content editing will require manual enabling.
Correct if I'm wrong, but unless in the specific case of nested groups, this is useless:

  // Create the OG Vocabulary.
  $group_type = $entity_type;
  $og_vocab = og_vocab_create_og_vocab($vocab->vid, $entity_type, $entity->type);
  $og_vocab->save();

The OG vocabulary entity reference field should be associated to the group type but to the group content type.

What about adding a parameter to the rule to define the entity type/bundle that should use OG vocabulary?
Something like this in hook_rules_action_info :

     'group_content_types' => array(
        'type' => 'list<text>',
        'label' => t('Group content types'),
        'wrapped' => TRUE,
        'options list' => 'og_vocab_rules_group_content_types_options',
      ),

and this code instead of the previously quoted code:

function og_vocab_rules_action_create_vocab($group, $name, $description = '', $group_content_types = array(), $settings) {
(...)
  // Create the OG Vocabularies.
  foreach ($group_content_types->value() as $option) {
    list($group_content_entity_type, $group_content_bundle) = explode(':', $option);
    $og_vocab = og_vocab_create_og_vocab($vocab->vid, $group_content_entity_type, $group_content_bundle);
    $og_vocab->save();
  }

and this function as options callback:

/**
 * Options callback for create OG Vocabulary Rules action.
 */
function og_vocab_rules_group_content_types_options() {
  $options = array();
  foreach (entity_get_info() as $entity_type => $entity_value) {
    foreach ($entity_value['bundles'] as $bundle => $bundle_value) {
      if (og_is_group_content_type($entity_type, $bundle)) {
        $options[$entity_type . ':' . $bundle] = check_plain($entity_value['label']) . ' - ' . $bundle_value['label'];
      }
    }
  }
  return $options;
}

PS: I don't provide a patch because providing the entire .rules.inc file as a patch would not highlight the change, and I'm not very comfortable with patches of patches.

Path with GaëlG's suggestions attached

There was an error in GaëlG's logic, fixed in attached patch

Added ability to configure widget settings

it is possible to have a widget for adding terms in node-form?
I add your rule when the group is created, but the user can't not add term whatever the widget.
i tested "Autocomplete term widget" "hierarchical select", and "entity reference tree".