Provide a "complex" widget instead of "Primary" and "Secondary" fields.

Is it available in latest dev?

I tested another way to build a nice widget to set content to one or more groups....
Autocomplete Deluxe module! Works fine! Also with tag style! So groups can added and removed a nice way to content.

What is missing is a widget to add other users a simple and nice way to one or more (own) groups ;)

Updated issue summary.

Is this just waiting on your patch being committed to ctools, or are there still specific problems with the new widget that need work?

Thanks for this. It's very exciting; should make things much better!

Testing out the patch in #6, one bit of feedback is that this is still confusing for administrators when there is an entityreference prepopulate widget in play, since this fails to populate the new widget if the administer is not part of the group.

Also, unless I've misconfigured my widget, I'm getting ajax errors due to this code in og_entityreference_autocomplete_callback() always returning access denied (throwing a browser error since this isn't returned as json) for groups the administrator is not a member of.

  if ($entity_id !== 'NULL') {
    $entity = entity_load_single($entity_type, $entity_id);
    if (!$entity || !entity_access('view', $entity_type, $entity)) {
      return MENU_ACCESS_DENIED;
    }
  }

When trying to edit *any* og content, an exception is thrown since $other_groups_ids is always false, thus $valid_ids is always empty.

          // Keep only the hidden group IDs on the entity, so they won't
          // appear again on the "admin" field, for example on an autocomplete
          // widget type.
          $valid_ids = $other_groups_ids ? entityreference_get_selection_handler($field, $mocked_instance, $entity_type, $dummy_entity)->validateReferencableEntities($other_groups_ids) : array();
          $valid_ids = $field['cardinality'] == 1 ? reset($valid_ids) : $valid_ids;
          $wrapper->{$field_name}->set($valid_ids);

Also, if I comment out the call to the set() method from #14 to bypass the unhandled exception, when editing, both the 'Default' and the 'Administrator' values are filled in:

resulting in this error when saving:

FIELDNAME: this field cannot hold more than 1 values.

This also happens on node creation when using the entityreference prepopulate widget as an administrator.

I've filed a new issue against jhedstrom's problem from #15: #1781674: For new Complex Widget, Entityreference Prepopulate populates both Default AND Administrator values