Incomplete field type definition caused tokens or token types missing name property

You can add (patch) in "yearonly.module" with the next code, but it's not dynamic :-(

/**
 * Implements hook_token_info_alter().
 */

function yearonly_token_info_alter(&$info) {
  $info['tokens']['node-field_my_node_field_type1_year']['value'] = array (
    'name' => t('yearonly: type1'),
    'description' => t('Yearonly for the type1'),
  );
  $info['tokens']['node-field_my_node_field_type2_year']['value'] = array (
    'name' => t('yearonly: type2'),
    'description' => t('Yearonly for the type2'),
  );
[...]
}

It looks like the Heading Field module figured out how to do this dynamically within the module.

See how they did it in patch #10 at #2934662: TOKENS OR TOKEN TYPES MISSING NAME PROPERTY after update.

Shamelessly taken from Heading Field module at #3.

Patch attached.

It may be shameless, but it works! :)

The root cause is that the filed type definition is incomplete

Run `drush updb` to get it updated

The patch https://www.drupal.org/files/issues/2019-08-01/token_missing-2951179-7.p... doesn´t work for 1.3.0, the warning still apearing on the status report page after apply the patch and run updb.

Thanks,

Thanks waverate. #4 works.

Drupal 8.8.5
yearonly 8.x-1.3

Patch #4 works on Drupal 8.9

#4 works for nodes but not for paragraphs.

I used patch #4 but slightly modified it to work with my custom content entities that were throwing the missing name property warning. This should work with paragraph entities as well though i haven't tested that.

/**
 * Implements hook_token_info_alter().
 *
 * This adds the missing token info for automatically detected tokens.
 */

function yearonly_token_info_alter(&$info) {
  $entities = \Drupal::service('entity_field.manager')->getFieldMap();
  foreach ($entities as $entity_key => $entity) {
    foreach ($entity as $field_key => $field) {
      if ($field['type'] !== 'yearonly' ) {
        continue;
      }

      $token_key = sprintf($entity_key . '-%s', $field_key);
      $info['tokens'][$token_key]['value'] = [
        'name' => t('Year Only'),
        'description' => t('Year only value.'),
      ];
    }
  }
}

#4 patch did not apply for me with latest 8.x release, but #7 did and fixed the issue once I ran updb.

It looks like the patch excludes every entity type except nodes—is that necessary for this solution? I've seen this warning for fields in taxonomy terms and paragraphs, would a more generic solution like that proposed by @skumararatne work, or are there potential unintended consequences?

#7 fixes $info['tokens']['term-field_year']['value'] warning that #4 did not.
Thanks jungle!

Drupal 8.9.13
yearonly 9.0.0

Updated patch with code from #13

Drupal 9.3.9
yearonly 9.0.0

+1 for #17

+1 for #17

Drupal 9.4.1
yearonly 9.0.0

+1 for #17
Drupal 9.4.2
yearonly 9.0.0

I've applied #17 using the 'cweagans/composer-patches' composer.json patching method.

gist available at https://gist.github.com/josephdickson/5178979b3b67c3cc14c84f3ff33746de

+1 for #17

New co-maintainer here 👋. Moving to the 9.x branch, as all new development/fixes will occur there. Thanks!

#11 RTBC'ed #4 but I don't think #4 should be RTBC'ed. And #17 does resolve the issue, but I do not think it's the right way.

#14: #4 patch did not apply for me with latest 8.x release, but #7 did and fixed the issue once I ran updb.

#16: #7 fixes $info['tokens']['term-field_year']['value'] warning that #4 did not.

I still think #7 is the right fix with the confirmation from #14 and #16, thanks!

Implement foo_token_info_alter() to alter the tokens provided by module foo itself, which is weird and does not make sense at all.

Hi @jungle. Yeah, I was just looking at this, and I tend to agree that your solution (#7) is likely the way to go. I'm going to do a bit more testing. Thanks for the additional feedback!

I committed #7 to the 9.x-dev branch because:

1. The field definition updated is needed regardless of the token warnings.
2. #4 works for nodes only.
3. #17 doesn't work for taxonomy terms.
4. In my testing, #7 resolves the token warning for all entity types.

Please test with the dev branch if you are able. Be sure to run updates (drush updb)! 😀

Updating credit. Thanks to everyone for pushing this forward.

Thanks @justcaldwell for reviewing and committing!

Included in 9.1.0 release.