Entity Processor branch: Default author of entity not overidden by mapping to uid

I'm having same problem.
It would be better if matching is done using either username or email.

Same problem here using the latest dev version of feeds. Anybody found a solution yet?

I was able to work around this by copying the setTargetElement function from FeedsNodeProcessor.inc and putting it into FeedsEntityProcessor.inc then modifying it as I needed. My function ended up looking like this:

  public function setTargetElement(FeedsSource $source, $target_node, $target_element, $value) {
    switch ($target_element) {
      case 'author':
          $target_node->uid = $value;
        break;
      default:
        parent::setTargetElement($source, $target_node, $target_element, $value);
        break;
    }
  }

I have a column of uid's so I simply set the uid of the node to the mapped value.

I'm having the same problem to import the type Profile2 entities. The code #4 worked to me, I only had to change the line "case 'author':" to "case 'user':"

public function setTargetElement(FeedsSource $source, $target_node, $target_element, $value) {
    switch ($target_element) {
      case 'user':
          $target_node->uid = $value;
        break;
      default:
        parent::setTargetElement($source, $target_node, $target_element, $value);
        break;
    }
  }

Moving to the Feeds entity processor project, the new home for the generic entity processor.

Here's a patch for #5 which is also working for me.

This is now broken with the last commits to 7.x-1.x. We end up with setTargetElement() being declared twice.

With this in the dev branch

  /**
   * {@inheritdoc}
   */
  public function setTargetElement(FeedsSource $source, $target_item, $target_element, $value, array $mapping = array()) {
    $properties = $this->entityProperties();
    if (isset($properties[$target_element])) {
      $plugin = feeds_entity_processor_plugin($target_element, $properties[$target_element], $this->entityWrapper($target_item), $this);
      $plugin->setValue($value, $mapping);
    }
    else {
      parent::setTargetElement($source, $target_item, $target_element, $value);
    }
  }

This issue can probably be considered fixed and closed.

@ctrlADel: Can you elaborate on how the two are related?

In #2659900: Support for property type "entity" mapping to entity properties was improved. This module now has support for the following data types:

• Text
• Boolean
• Date (though limited to timestamps currently, see #2708243: Add date formats support.)
• Entity
• Any entity type (user, node, taxonomy term, etc.)

Other data types are handled the same as if it were text, so not all data types are supported yet.

If the property 'author' or 'user' (as used in the code examples) are declared as type 'user' by the module that provided the property (using an implementation of hook_entity_property_info() or hook_entity_property_info_alter()), then importing values for that property should work (at least in theory).

It is a good idea to verify first if importing these values for the reported entity types indeed works now before closing this issue. Behaviour per entity type could vary, because each entity type can have their own specific logic for operations on the entity.