Support for feeds in the future?

No real plan. In the DEV version, you can directly map taxonomy fields to access controls, which should naturally map to Feeds.

I think that is the plan, in fact. ;-)

Ooops. sorry, setting back.

Since native taxonomy field support has already been committed, I think this is fixed.

Apologies to re-open this, however we needed the same functionality as hixster. That is, assign an access section during feeds import. Taxonomy mapping is not an option as the access section vocabulary does not appear in the list of mapping targets.

Attaching a patch to add "Workbench Access section" to the list of targets, which can then be populated with the term id or term name.

Cheers,
Dan

Excellent patch. Works well.

I tried out the patch in #9 and got the error:

Warning: trim() expects parameter 1 to be string, array given in workbench_access_feeds_set_target() (line 42 of .../workbench_access.feeds.inc).

For it to work I had to change

if ($name == trim($value)) {    
 $current_section = $id;
 break;
}

to

 if ($name == trim($value[0])) {
  $current_section = $id;
  break;
}

Maybe this will help anyone that gets the same error. Apart from that, this was a really handy patch that saved me a lot of time.

Wonderful patch on #9 zerolab. Thank you so much!

Based on #11, this needs a re-roll.

Attaching a re-rolled patch that incorporates feedback from #11
Doing the trimming and array check at an earlier stage.

Cheers,
Dan

Please enable this patch for workbench_access module.

Does that mean that the patch works as designed for you?

FWIW, we are using this patch in production for the past 4 years. But will leave it for someone else to RTBC

The patch in #14 works as intended.

Thanks!

Committed.