Co-Authors Token

You could send the mail to the author and CC to the co-authors. According to the CC field description 'multiple email addresses may be separated by commas'.

I would have expected a token like [webform_submission:source-entity:co_authors] to already exist automatically, but seems like it doesn't. We should probably look into why the Token module isn't providing a token for that field.

I've made a custom module that adds a new token like below. You're welcome to use/improve this if you think it would be helpful to others. If you decide to incorporate something like this into the main module, I'd be happy to phase out mine.

From the coauthor_tokens.module file:

<?php

/**
 * @file
 * Token functions extending node_co_author.
 */

use Drupal\Core\Render\BubbleableMetadata;
use Drupal\user\Entity\User;

/**
 * Implements hook_token_info().
 *
 * Defines tokens.
 */
function coauthor_tokens_token_info() {
  $info = [];
  $info['tokens']['node']['coauthors_email'] = [
    'name' => t("Coauthors' emails."),
    'description' => t("The coauthors' email addresses, separated by commas."),
  ];

  return $info;
}

/**
 * Implements hook_tokens().
 *
 * Defines values for tokens.
 */
function coauthor_tokens_tokens($type, $tokens, array $data, array $options, BubbleableMetadata $bubbleable_metadata) {
  $replacements = [];
  foreach ($tokens as $name => $original) {
    if ($type == "node") {
      switch ($name) {
        case 'coauthors_email':
          $node = $data['node'];
          if ($node) {
            $coauthor_emails = [];
            $coauthors = $node->get('co_authors')->getValue();
            foreach ($coauthors as $coauthor) {
              $coauthor_emails[] = User::load($coauthor['target_id'])->getEmail();
            }
            $replacements[$original] = implode(',', $coauthor_emails);
          }
          break;
      }
    }
  }
  return $replacements;
}

It seems like it's not yet possible to automatically provide all user-related tokens for an array of co-authors (see ✨ Need to figure out how to create nested tokens from the array token type Needs review ), so we'll need to define individual tokens per field as @ryanrobinson_wlu does in his example. I'll start a MR.

I added a new [node:co_authors_email] token to the MR. To get the email addresses as a comma-separated list, you can use [node:co_authors_email:join]. Can someone test the MR?

I've attempted it and had two problems so far:

1. I tried to install it with a patch in composer as I normally do. Composer keeps coming back with "Could not apply patch". I don't know why. I eventually manually updated the file so I could test further, but I would ultimately need to solve that to be able to deploy it to other environments. This one can be mostly ignored because if it gets into a stable release, it won't matter in the long run.

2. I can't figure out an allowed format for the token. In the context of the webform submission email, I can do [webform_submission:node:co_authors_email:join] which works but the elements are crammed together with no separation instead of with commas in between. I tried other varieties like [webform_submission:node:co_authors_email:join:,] and [webform_submission:node:co_authors_email:join:","] which are implied to be an option by the ? in the token browser but will not save, saying it is an invalid token value.

I can't figure out an allowed format for the token. In the context of the webform submission email, I can do [webform_submission:node:co_authors_email:join] which works but the elements are crammed together with no separation instead of with commas in between.

How are you making this work? I add an email handler, under CC email > Custom CC email address I set [webform_submission:source-entity:co_authors_email:join:,] (not [webform_submission:node:co_authors_email:join:,], because [webform_submission:node] does not exist) and when I click Save the following error message appears:

The email address [webform_submission:source-entity:co_authors_email:join: is not valid.

This implies that tokens aren't replaced in that field and that it's trying to parse the token as-is as an email address. How are you using tokens there?

Something else: I just re-read the issue description and saw this:

Create a webform and in the Email/Handlers section, set up an email. In our context, the desired token would go in the To field with a custom To email address.

The To email address can only be a single email address, so why would you try to add to co-authors there?

I am putting it in the cc field, which does accept tokens as well as multiple values. It works with the custom token I had previously made where the token is provided as a comma-separated string as opposed to an array that then needs joined. Yours also works as a token when I use join but without specifying a separator, but that means the emails are crammed together which would not work to send to them. If I try to add the comma separator, I am getting the behaviour you've described, with it claiming that it isn't valid. I'm guessing the presence of the , is what is causing it to "parse the token as-is as an email address". That would essentially mean that your token in general works, just doesn't solve my particular problem because I can't join by , in there.

That seems to be a problem with the Webform module. I checked the code and it actually skips email validation if the value contains a token, but it only does that after trying to split it into a list of mails. I created an issue and MR to fix that: 🐛 Token detection in email validation doesn't work if the token contains a comma Active .

The token does work, so I think I'm going to commit it as-is. Providing it as an array token gives it more flexibility. I propose you keep using the custom token you made for now and once that issue in Webform is fixed, you can use the new token.

🐛 Token detection in email validation doesn't work if the token contains a comma Active was just committed and will be included in the next Webform release, which will make the token included with this module work with Webform.

Thank you for helping make that happen! I've made a note that I can phase out my custom module and use your new token in our next release, assuming the webform update is stable by then.

Automatically closed - issue fixed for 2 weeks with no activity.