Allow mapping to Taxonomy Term Reference Field

Not fully understanding what you're trying to do here. Why does your user field need to be a taxonomy term field? Seems like it would be fine to be entity reference field.

Is the issue here that you're not able to map to a taxonomy term reference field? (And that's why you're looking at resorting to options like Rules autotag)?

If that is the case then we can turn this into a feature request and update the summary.

Have updated issue as this should apply to all fields, not just tweet_user.

Also adding related issue that deals with not all field types being supported.

@ydahi, i was trying to do something similar. Now i'm trying to switch to an entity reference field instead, but I can't seem to get it to work. Can you post your code for how you are creating/saving those fields?

I was able to get this to work with entity reference fields, problem is it only seems to work sometimes. I'm using the entity reference module and the entity reference autocomplete module.

Here's my code:

function upup_taxonomy_social_content_settings_alter(&$type, &$form, &$settings) {
  switch ($type) {
    case 'instance':
      $form['field_up_up_client'] = array(
        '#type' => 'entityreference',
        '#title' => t('Up&Up Client'),
        '#era_entity_type' => 'node',  // Mandatory.
        '#era_bundles' => array('up_up_client'), // Optional (Any bundle by default).
        '#era_cardinality' => 1,       // Optional (1 By default).
        '#description' => 'Choose a client name.',
        '#default_value' => isset($settings['field_up_up_client']) ? $settings['field_up_up_client'] : NULL,
      );

       $form['field_up_up_contact'] = array(
        '#type' => 'entityreference', 
        '#title' => t('Up&Up Contact'), 
        '#era_entity_type' => 'node',  // Mandatory.
        '#era_bundles' => array('up_up_contact'), // Optional (Any bundle by default).
        '#era_cardinality' => 1,       // Optional (1 By default).
        '#description' => 'Enter a contact name. This is optional.',
        '#default_value' => isset($settings['field_up_up_contact']) ? $settings['field_up_up_contact'] : NULL,
      );
      break;
  }
}

/**
 * Alter the entity before it's saved.
 *
 * You have the original record so you can grab fields from it and attach it to
 *  the wrapper.
 *
 * @param EntityMetadataWrapper $wrapper
 *   The EntityMetadataWrapper with the fields in the settings set.
 * @param object $context
 *   The original record from the social network.
 */
function upup_taxonomy_social_content_import_alter(&$wrapper, &$context) {
  $settings = $context['settings'];
  if (isset($settings['field_up_up_client']) && !empty($settings['field_up_up_client'])) {
    $wrapper->field_up_up_client->set(array_values($settings['field_up_up_client'])[0]);
  }
  if (isset($settings['field_up_up_contact']) && !empty($settings['field_up_up_contact'])) {
    $wrapper->field_up_up_contact->set(array_values($settings['field_up_up_contact'])[0]);
  }
}

I created the following patch for mapping hashtags to taxonomy field terms. It works as the following proposal above and in addition creates the term if it does not exist.
This patch has only been tested with Instagram.

Committed #11 with the following:

@@ -687,6 +687,9 @@
         elseif (in_array($property_info[$field_name]['type'], array('list<taxonomy_term>', 'taxonomy_term'))) {
           $terms = array();
           $vid = taxonomy_vocabulary_machine_name_load($property_info[$field_name]['bundle'])->vid;
+          if ($value && !is_array($value)) {
+            $value = array($value);
+          }
           foreach ($value as $name) {
             $name = self::validateText($name);
             $term = taxonomy_get_term_by_name($name, $property_info[$field_name]['bundle']);

Otherwise it fails when $value is a single item.

Thanks.