trenttati → created an issue.
Thank you @jurgenhaas for recommending eca_tamper as a potential solution. I had a similar problem to solve and Tamper's implode worked perfectly within my model.
The Tamper: Impode event I set up looked like this:
eca_data: '[node:field_multi_term_ref]'
eca_token_name: shared_tids
glue: ','And the output is a list of TIDs separated by commas. Providing the "shared_tids" token I created via the event to the Query View event in the Arguments field results in the view receiving the expected list of taxonomy term TIDs as contextual filters.
Yes, the feature I am referring to is the combination of ACL per node and user-specific ACLs. I've included a screenshot of the user-level form element on an individual node.
On a current system I am building I would like to use ECA Content Access to automate the process of granting users edit access to nodes when those users are referenced by one of several fields available in the content type. The OG and Group modules won't work in this case because the referenced users can be anybody from the organization and all users in the organization are authorized to view all nodes of this content type.
Thank you @jurgenhaas! Your attention to clarity of communication and nuanced details is largely what is (quickly) making ECA and its ecosystem such an invaluable part of Drupal.
The feature is available in both 2.x and 8.x-1.x.
For what it's worth I verified on a dev site by removing ECA_content_access (due to declared dependency on content_access 8.x-1.x), and then installed content_access 2.0.0-alpha1 over 8.x-1.0-alpha4 with composer. The existing content_access configurations remained in place and the "Per content node access control settings" was still available.
trenttati → created an issue.
Thank you @jurgenhaas! I can only hope my insufficient searching leads to others' quicker discovery of this ECA submodule. I'm working with it now and will open new issues if I find any problems or functionality lacking.
trenttati → created an issue.