The following token types are not defined but have tokens:

$info['types']['config-variable']

CommentFileSizeAuthor
#2 config_builder-token_problem.png11.62 KBrkeppner
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

liza’s picture

i have the same problem

rkeppner’s picture

The message reported in this issue is displayed on the status result page, under Tokens.

I'm seeing the same issue for version 7.x-1.0.

Screenshot attached:
Configuration Builder token problem

Anonymous’s picture

same problem

dvandusen’s picture

Issue summary: View changes

same problem

Jooblay.net’s picture

We are seeing this similar issue with:
$info['types']['commerce_order']
$info['types']['commerce_product']

We are looking for more tickets on this issue. rszrama from drupal commerce has stated these are from a broken module and or left over from a token install?

Did anyone instal custom_tokens

We do not want to high-jack this ticket... but wanted to show similar issue and or the same. The search continues:)

Jooblay.net’s picture

We found this:

Looking at this further, I see now that the issue is your tokens are defined using the type "commerce_customer_profile" when the token type used by core Commerce is "commerce-customer-profile." The difference is hyphens vs. underscores. Some module on your site is adding customer profile tokens using the wrong token type string. The Entity Token module itself uses the proper token type thanks to the parameter we include in our entity info, so the culprit is some other contributed module on your site. I did a quick check and neither the Addressbook nor PayPal modules define tokens.

You may just need to search your source code to find out which module is doing it. I'd recommend searching all of your contributed modules for "commerce_customer_profile" and see if any of them include it in a reference to token definition. If you find the culprit, please reopen this issue and move it to the module's issue queue.

https://drupal.org/node/1947446

This would seem to indicate that somewhere in your drupal install there is a broken token being called? Where? Who knows... that maybe the funnest part... searching through the wild.

danharper’s picture

I had this same problem and it turned out to be a flag configuration, so the tokens will be used in config somewhere rather than code.

Check the config of all modules that use tokens such as flag, metatag, paths anything that could be using the wrong token.

Dan

Jooblay.net’s picture

Thanks Dan will do:)