Closed (outdated)
Project:
Token
Version:
7.x-1.x-dev
Component:
Code
Priority:
Major
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
31 Aug 2011 at 19:09 UTC
Updated:
1 Nov 2025 at 14:40 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
dave reidAre you using the 'Entity tokens' module at all? I haven't been able to replicate this at all...
Comment #2
dave reidComment #3
Anonymous (not verified) commentedI'm getting a similar warning. Don't use entity tokens. Installed modules that require tokens are page title and pathauto.
The warning message I get is:
Comment #4
cybermcm commentedI've the same warnings like moreorless. I also don't use entity tokens
Comment #5
rgaskell commentedI too see the message like moreorless reported. I updated the token module and then did the core update to 7.8. I wonder if the order made a difference.
Comment #6
dmirtillo commentedI'm having the same issue on a 7.8 install which i just updated.
rgaskell, i did it the other way around and i have the issue aswell, so i guess order doesn't matter.
The error message i receive, though, has different tokens:
Comment #7
patrickkraaij commentedI've the same warnings:
Earlier this month I got the warning:
WD actions: 3 orphaned actions
(when using drush cc all), cause I unchecked the comment module. In admin/config/system/actions there are no more actions for comment. I removed that by using
https://drupal.org/node/445922#comment-3738188
Comment #8
chemicalroman commentedSame problem using last dev and core 7.8
Comment #9
valderama commentedI can confirm this problem - after updating to token beta 5 this warning shows up on the status report page. Here I am using D7.7, so the error seems not to be 7.8 specific. Flushing cache didn't help.
Can we reopen this issue?
Comment #10
el7cosmosI have this warning with comment module disabled:
If i enable comment module, the warning didn't appear.
Comment #11
rosk0Same problem:
Comment #12
dave reidInteresting - so you're getting this error when you have comment module disabled.
Comment #13
rizenine commentedSame here. When comments module is disabled it shows this error.
Comment #14
graytoby commentedI've lost all Node Hierarchy tokens. I use Entity token module as it is required by Rules.
Comment #15
dave reid@spongecat: This is not related to the issue at hand.
Thanks all for helping debug this - this helped expose a bug in token.module's own hook_token_info_alter(). I'm on it.
Comment #16
corbacho commentedAfter updating Token to the last version, I have this error: (Drupal 7.7)
Comment #17
bryancasler commented#12 Yup, I have the comment module disabled and I'm getting these. Drupal 7.7
Comment #18
jies commented#12: I have the same 'Status Report' message with Comment module disabled. When I enable it, the message clears. Drupal 7.4 Acuia Dev Desktop.
Comment #19
Patricia_W commentedI'm not using Entity tokens. I am using Pathauto which depends upon Token.
Comment #20
Anonymous (not verified) commentedProblem with meta tags quick module?
Comment #21
dave reidThis should be addressed for the following items with http://drupalcode.org/project/token.git/commit/f147805 in 7.x-1.x-dev:
$info['tokens']['comment']['url']
$info['tokens']['term']['url']
$info['types']['comment']
$info['types']['term']
If you are getting this notice for other types, you will need to file an issue with the modules that provides the offending tokens.
Comment #22
BeaPower commentedIs that the fix, can anyone comment on whether #21 worked?
Comment #23
chemicalroman commented#21 worked for me, thanks!
Comment #24
calculus commentedSub
Comment #25
upupax commentedI confirm that #21 solved the $info['types']['comment'] issue with Comment module disabled.
Comment #26
Patricia_W commented#21 also solved my problem. Thanks.
Comment #27
baluertlI confirm that #21 eliminated the yellow notice of missing tokens on Status Report page. Thanks, Dave!
Comment #28
Anonymous (not verified) commented#21 worked for me as well.
Thanks for the fix.
Comment #29
frank ralf commented#21 did the trick, thanks!
PS:
I couldn't apply the patch using NetBeans as usual. Is the Git patch format any different from the CVS patch format?
Comment #30
MZiray commentedThe lastest dev release (from Sept 6) fixes this issue. So no need to apply that patch anymore, just get the latest dev version.
Comment #31
dadderley commentedHad the same problem as above.
The lastest dev release (from Sept 6) fixes this issue.
Thanks AvalonInnovations.
Comment #32
thomsol commentedApplied latest dev, still getting Status Report message:
The following token types do not have any tokens defined:
$info['tokens']['computed']
Comment #33
shaisamuel commentedMe too like #32 (Sep 6 dev ver)
Since there are 2 of us, I changed the status to active.
Comment #34
shaisamuel commentedComment #35
klonosYep, still getting the $info['tokens']['computed'] not defined even after installing latest dev from Sep 6.
Comment #36
dave reidPlease file an issue with the Computed field module.
Comment #37
klonosYou're right Dave, just thought it might be something that could be handled in Token. Here's the issue in Computed field project's queue: #1275946: Site status report -> Problems detected: The following token types do not have any tokens defined: $info['tokens']['computed']
Comment #38
pissouxxx commentedGot a similar problem with notifications
Tokens Problems detected
The following token types do not have any tokens defined:
$info['tokens']['subscription']
The following token types are not defined but have tokens:
$info['types']['notifications_subscription']
Comment #39
Screenack commented#21 fixes the problem here, as should the latest dev release. I had to delete token, and replaced it with the Sept 6 download, to see the change. "drush up" alone may not trigger a thorough update.
Comment #40
Screenack commentedNote: I'm seeing this same error with the 7.x-1.0-beta5 branch.
Comment #41
steinmb commented#21 fixes this problem, thanx Dave! :)
Anyone still seeing this pls. make sure you are running latest dev.
Comment #42
loicgao commented#21 fixes some problems, but I have still this warning
Comment #43
klonosHey, Loïc, you'll need to file this as a separate issue in the Profile 2 project's issue queue (same way we did for #1275946: Site status report -> Problems detected: The following token types do not have any tokens defined: $info['tokens']['computed'] in the Computed field project's issue queue).
Comment #44
mgiffordI just got this too after upgrading to 7.x-1.0-beta5 on Drupal 7.8.
I'm not certain where to go to fix this or what effect it is likely to have.
Comment #46
wendallsan commentedI still get the following warning in my Status Report:
This is a duplicate of item #38 above.
How can I fix this or suppress this message from the status report if it's not actually a problem?
Comment #47
dave reidThen please file an issue in the subscriptions module - or try updating the subscriptions module to the latest dev and checking to see if this has already been fixed.
Comment #48
felixvang commentedI'm new to this. how did you get #21 apply to work? Do you have any instruction on how to apply?
Comment #49
Anonymous (not verified) commentedabout #21, sorry for the newbie question.
Tokens Problems detected
The following token types are not defined but have tokens:
$info['types']['sms_user']
Should I open an issue in the smsframework module project?
Comment #50
afpteam commentedRe: 21 above,
FWIW, I just did a fresh install of Groups with Token 7.x-1.4 having Groups Example enabled and found the problem continues even with the patch. Not sure how that will affect the $info['types']['comment'] use with respect to url's as the patch seems to address.
I turned off 'Message OG example' and 'Message example', which stopped the production of the php error message ...
Notice: Undefined index: membership_type in og_entity_property_info() (line 236 of /var/www/drupal/sites/all/modules/og/og.module)
Comment #51
silkogelman commented@arpteam #50:
That 'line 236 Undefined index Notice' might be related to this issue:
#1937530: Organic Group Widget on an Entity Reference field not working properly
Comment #52
matbaa commentedI have the same warnings too
Comment #53
karnakitab commentedI have this error message with latest dev as well as stable versions of token.
Any tricks to solve this?
Comment #54
narayankumar commentedYes. Same as above:
Comment #55
karnakitab commented@narayankumar use the patch https://www.drupal.org/files/voting_rules_missing_token_description-1268... to your voting_rules files.
You can apply this diff patch using Netbeans/Eclipse IDE in case you are on Windows machine. I successfully applied this patch on my Red Hat server. Hope this helps.
Comment #56
bisonbleu commentedPatch referenced in #55 worked for me. Thanks all!
Comment #57
iwd35 commentedhi,
7.43 updated version on my system but i have give errors:
Tokens Problems detected
The following tokens or token types are missing required name and/or description information:
$info['types']['date']
$info['tokens']['node']['url']
$info['tokens']['file']['size']
$info['tokens']['user']['url']
$info['tokens']['date']['custom']
The following token types are not defined but have tokens:
$info['types']['node']
$info['types']['term']
$info['types']['vocabulary']
$info['types']['file']
$info['types']['user']
$info['types']['current-user']
Comment #58
issa.haddadinHello
I'm facing the same issue on Token-7.x-1.6 with Drupal-7.43, as i get the same warning every time i clear the cache which basically breaks the related tokens:
Also the same thing happened when i used the dev (7.x-1.6+8-dev) version of the module with a little different warning:
Comment #59
arnoldski commentedUsing Drupal 7.44 and Token 7.x-1.6.
If I disable the module Domain Access (domain) the error is gone.
Comment #60
jamesdixon commentedI experience the same issue as #57, #58 and #59 with Drupal 7.42 and token 7.x-1.6.
Some things I've noticed:
1) Disabling and enable ANY module will make this error go away temporarily. Something that's happening when you disable or enable a module fixes the token issue.
2) Flushing the cache causes the token problems to return.
Comment #61
jamesdixon commentedAfter some serious debugging we found the issue was with a patch we applied on the noty_messages module.
What was happening was:
1) Flushing the cache cleared the token cache in the table cache_token
2) When trying to save a node or entity that was using tokens in metatag etc, the token cache would be built in cache_token, but was missing a ton of tokens.
3) I believe the token cache was being tripped up by the following line towards the top of noty_messages.module, as removing it removed the problem:
4) When the node / entity was trying to save, it was reporting missing tokens, because it couldn't find them in the token cache_token table.
I'm not sure why that line of code would break the tokens, but from now on I'm avoiding the use of any function calls in define()!
If anyone with a better understanding of token or PHP wouldn't mind explaining why that line of code interrupted the token cache building routine, I'd love to hear about it.
Here's more details on the patch that caused the issue:
https://www.drupal.org/node/2745151#comment-11452115
Comment #62
jamesdixon commentedAfter further reflection, I have a theory. If token is building the cache using a stripped down bootstrap level, the url() function may not be available. When the noty_messages.module file is loaded, it tries to define NOTY_MESSAGES_AJAX_URL with the url() function and silently fails stopping the token cache from being built. I'm surprised I didn't find any PHP errors or warnings in the logs when flushing cache.
Comment #63
BasH commentedI experienced exactly the same issue as #57, #58 and #59 with Drupal 7.43 and token 7.x-1.6.
For me disabling the bitcache module worked (also after flushing all caches).
Going to test this with Drupal 7.50 next week.
Comment #64
veeraprasadd commentedI am also experiencing the same issue as mentioned in #57, #58 and #59 with Drupal 7.52 and token 7.x-1.6. Any solution to resolve issue? Unable to update any URL Pattern.
Regards,
Veera
Comment #65
vedpareek commentedI am also facing same issue.
Comment #66
vedpareek commentedHello All,
I have created a patch. Please apply this patch in token module.
Comment #67
rajveergangwarHi Ved,
I have used this patch is not working from my side please check it again.
Comment #68
rajveergangwarBelow are the tokens
$info['types']['date']
$info['tokens']['node']['url']
$info['tokens']['file']['size']
$info['tokens']['user']['url']
$info['tokens']['date']['custom']
The following token types are not defined but have tokens:
$info['types']['node']
$info['types']['term']
$info['types']['vocabulary']
$info['types']['file']
$info['types']['user']
$info['types']['current-user']
Comment #69
vedpareek commentedPlease ignore patch. I am facing cache problem.
Comment #70
kevinquillen commentedSeeing this now on a 7.43 site. Clearing cache from the admin UI has no effect.
Comment #71
kevinquillen commentedHow can I rebuild token info?
Comment #72
kevinquillen commentedAdding screenshot of what I see on the production site. Why is this token for date blank? This is being fed from system.tokens.inc.
The actual list of tokens is a lot longer:
PHP memory is 512M, PHP 7. I cannot replicate it locally. Cleared cache dozens of times on production. Only ONCE did I see the token list populate, however, it went away on the next cron / cache clear.
The date token comes from core, so, I don't see how this is a contributed module/code issue. Besides that, I don't have any contrib modules other than the standard ones that provide tokens.
Everything worked up until 7.43 and the upgrade to PHP 7 on the production server.
Comment #73
kevinquillen commentedRe-adding photo from #72.
Comment #74
Adon Irani commentedI am experiencing the same issue. In my case it token replacement was breaking and my WebForms were sending empty emails.
FOR ME... it is related to the autoslave module, https://www.drupal.org/node/2898888v
Enabling and disabling the module creates and resolves the issue.
Comment #75
kevinquillen commentedFor me, I had to increase opcache memory to 128 up from 64. This particular issue went away.
Comment #76
maha-2017 commentedHi,
I got the following error with h5p module
TOKENS OR TOKEN TYPES MISSING NAME PROPERTY
$info['tokens']['node-field_interactive_content']['h5p_content_revisioning_handled']
$info['tokens']['node-field_interactive_content']['h5p_content_id']
How do I fix this?
Thanks
Comment #77
lookatthosemoose commentedEnabling entity_tokens module and clearing cache fixed this for me, using Drupal 7.56 and Token 1.7
Comment #78
kevinquillen commentedJust want to reiterate that clearing cache does not fix this issue. It will resurface eventually.
Upping opcache memory to 128 MB only resolved the issue temporarily. The problem returned. So I set max accelerated files to 6000 (up from 2000). After that, I wound up implementing Memcache with 128M and the problem has gone away for good, I cannot replicate it.
Comment #79
sol358 commentedHello.
I have version 7 of drupal, and when updating to php 7, he gave me these errors in the token module.
Same problem:
Token types are not defined but have tokens:
Tokens or token types missing name property:
Can you please help me?
Thanks
Comment #80
pbosmans commentedAny progress with this issue ?
After updating to php7.2, these errors occured in the status page.
Comment #81
shaktikI've got the same warnings in PHP 7.3.
Token types are not defined but have tokens
$info['types']['node']
$info['types']['term']
$info['types']['vocabulary']
$info['types']['file']
$info['types']['user']
$info['types']['current-user']
Warning
Tokens or token types missing name property
$info['types']['date']
$info['tokens']['node']['url']
$info['tokens']['file']['size']
$info['tokens']['user']['url']
$info['tokens']['date']['custom']
Comment #82
shaktikI've got the same warnings in PHP 7.3.
Token types are not defined but have tokens
$info['types']['node']
$info['types']['term']
$info['types']['vocabulary']
$info['types']['file']
$info['types']['user']
$info['types']['current-user']
Warning
Tokens or token types missing name property
$info['types']['date']
$info['tokens']['node']['url']
$info['tokens']['file']['size']
$info['tokens']['user']['url']
$info['tokens']['date']['custom']
Comment #83
bysv commentedMe too, the same warnings in PHP 7.3 version. Any idea to solve this?
Token types are not defined but have tokens
$info['types']['node']
$info['types']['term']
$info['types']['vocabulary']
$info['types']['file']
$info['types']['user']
$info['types']['current-user']
Warning
Tokens or token types missing name property
$info['types']['date']
$info['tokens']['node']['url']
$info['tokens']['file']['size']
$info['tokens']['user']['url']
$info['tokens']['date']['custom']
Comment #84
kevinquillen commentedRevisit comments #75 and #78 to see if that resolves it for you.
Comment #85
Bagz commentedJust came across the same issue on one of my sites, same status report messages as in #79.
Clear cache from admin did not solve it, but
drush cc allmade it go away.Comment #86
Josephnewyork commentedI've upgraded from 7.67 to 7.69 as well as the Webform module and now all tokens are not being rendered and seeing the same thing in status:
Token types are not defined but have tokens
$info['types']['node']
$info['types']['term']
$info['types']['vocabulary']
$info['types']['file']
$info['types']['user']
$info['types']['current-user']
Warning Tokens or token types missing name property
$info['types']['date']
$info['tokens']['node']['url']
$info['tokens']['file']['size']
$info['tokens']['user']['url']
$info['tokens']['date']['custom']
I'm using PHP 7.3.9, and nothing like memcache or opcache.
I've attempted disabling any module using hook_token_info hook_token_info_alter and clearing all caches.
I'm desperate to fix this, made the mistake of updating prod.
*UPDATE* I reverted back to 7.67 from 7.69 and now all tokens are working. That mean the issue is with the core?? Also, I get "Warning: "continue" targeting switch is equivalent to "break" now on both versions...
*UPDATE* If doesnt matter what Core version I use, the issue is still breaking my site, page title reads " | ", and my Views Slideshow Block's tokens arent being rendered. Look like this: [node:title].
Comment #87
renguer0 commentedI have this problem related:
TOKEN TYPES DO NOT HAVE ANY TOKENS DEFINED
$info['types']['node-layout_builder__layout']
There is some news about it?
Comment #88
mdkdio commentedI am having the same issue as renguer0 #87
Drupal 8.8.2
Comment #89
Josephnewyork commentedI'm back again as I was wrong, degrading the core didn't solve it:
Token types are not defined but have tokens
$info['types']['node']
$info['types']['term']
$info['types']['vocabulary']
$info['types']['file']
$info['types']['user']
$info['types']['current-user']
Warning Tokens or token types missing name property
$info['types']['date']
$info['tokens']['node']['url']
$info['tokens']['file']['size']
$info['tokens']['user']['url']
$info['tokens']['date']['custom']
I'm using PHP 7.3.9
If doesn't matter what Core version I use, the issue is still breaking my client's site, page title reads " | ", and my Views Slideshow Block's tokens aren't being rendered, they look like this: [node:title] and no images are shown.
On the Help Tokens page I get an error when clearing the cache:
Notice: Undefined index: name in _token_token_tree_format_row() (line 201 of /var/www/html/sites/all/modules/token/token.pages.inc). =>An when the tokens are listed, it looks like this:
Screen Shot
As you can see from the screenshot, many tokens aren't listed and it seems to break off after a custom date token [date:custom:?] and it's group has no Name.
A few days ago I installed memcache, 128MB and it didn't help, if it was a memory issue people keep referring to. I was thinking it was because yesterday morning, the problem went away, but when I cleared the cache, it went back.
I'm really really desperate to fix this. I've go through almost all of my module token_info hooks returning []; one by one, hoping it will find the culprit, but no luck. I'll let ya know if I finish. Please help
*UPDATE*
So I spoke too soon about installing memcache and it not working. I'm a noob with memcache and thought that just installing it on the server was good enough. I didn't realize that you must also install the PHP plugin as well as configure and install the memcache Drupal module. It seem to be functioning now! It's a production site, so I'm afraid to play with it anymore in case it breaks again, but it seems to be fine now. Drupal doesn't work without object caching?? OKAY... I'll reply back later regardless of the outcome (as if anyone is listening lol). Thanks!
Comment #90
shaktikHi Josephnewyork,
try drush cc all to fix temporary.
Comment #91
spacetaxi commentedIt appears to be a PHP version issue for me. Reverting to PHP5 fixes it.
Comment #92
r.tini commentedHad the same problem on Drupal 7.67.
We resolved the issue working on folders access permissions on the server where our Prod runs. Apparently, with CI/CD they were changed by default on release and that caused, by other things, the tokens to not work.
Comment #93
snehi commentedHi Everyone, i found the issue after debugging for few nights.
The opcache, here was the culprit.
1. On our dev and QA instances we were using opcache with opcache.memory_consumption = 128MB.
2. On my local, i was not using opcache, hence getting the same error like some token are missing on status report.
3. Once i enabled the opcache on my local via php.ini, it starts working for few minutes, till the time the 128MB was not consumed.
4. Hence i increased my opcache to 500MB on my local and its been few days, site is working fine.
5. I checked on INT and QA the opcache memory was full and i try increasing the size to 1GB, so things are pretty fine there.
Posting here, so that others can also look into same solution.
Thanks to https://drupal.stackexchange.com/questions/233135/some-tokens-show-as-mi....
Don't forget to read the last comment on the question here.
Thanks,
Davinder
Comment #94
davej commentedI encountered similar problems with tokens on Drupal 7.70 and PHP 7.3, e.g. when creating a node:
Once this problem arose, the node title failed to display on the browser tab. Clearing caches via the UI (admin menu) did not fix.
drush cc allfixed temporarily. Subsequently clearing caches via the UI reintroduced the problem.When running
drush cc all, a warning appeared similar to #86 :This is a PHP 7 compatibility issue. I applied this patch from this issue to address that warning. After doing that, clearing caches from the UI no longer produced the problem - and instead fixed it if it was already happening.
To double-check that this was the cause, I reverted the patch, re-tested, re-patched, re-tested, repeated that a couple of times with consistent results. On other sites, it's possible another module has the same PHP 7 compatibility issue, so check any warnings from drush.
Comment #95
Josephnewyork commentedSo since the last 3 months when I last replied here, I have been able to keep the site up for a few days at a time once I installed memcache, memcache php, and the memcache Drupal module. On my hosting ( Rackspace CentOS w/ 1GB memory ), I set an alert once memory use reaches 80%+ and another with 90%+. A few times a week, the alerts are triggered after a spike or series of spikes, and at the same time, the memcache fails, which causes the Drupal tokens to break again. So, I freak out, CL memcache restart, and clear the Drupal caches, and the site is fine for a while. But I can't keep doing this... It's probably safe to upgrade the general Linux cloud server to a 2GB, and that may fix it, but then the hosting cost increases by over 50%, and I've never been the guys that just throws money at things to fix them.
I saw above that someone allocated 1GB to opcache, but I don't think I'm using opcache... I never installed it.
What should I do here guys?? This site is a simple blog, why is this so difficult? I'm even using a CDN.
Thanks!!
Comment #96
steinmb commentedThis issue is getting old and cluttered. I read multiple different problems. Some fixed in here, some hosting env. related. I suggest that PHP 7.3/7.4 issue should split out (child issue) from this into a new and clean one that can focus on tackle any PHP version compatibility problems.
Comment #97
steinmb commentedFor people running out of memory, perhaps test https://www.drupal.org/project/token_tweaks in a local env. It normally help. In the issue queue are there also multiple issues related to memory issue. Perhaps move those discussions there? The original issue was created 9y ago and addressed and closed by Dave R. Perhaps time to close this and open new and clean issue(s) with a an clean description, how to re-produce it and so on. Clear issues with a narrow scope is easier to understand, and what we all want, fix.
Comment #98
Josephnewyork commentedI agree fixing the PHP 7 version issues should be moved as it's a different issue, and open to continue with a new memory issue continuation, if I have time. Please post it here if someone creates one, and I will contribute.
Comment #99
Claude VIGUIE commentedIn case it could help
I had exactly the same problem on gentoo D7.68, php5.3.8, Nocache , No Memcache (no one of the previous config was related to the problem)
The problem was... a same define eg: (define('SAMENAME','xxxxxxxxxx');) in two different modules...
I changed the name of the constant in one of the two modules, UI clear cache... and that's it....
I will make an update if the problem re-appear.. but from now everything is ok
Comment #100
krishna mishra commentedTokens (Token module ) is not working properly with PHP7.4 on other hand with PHP7.2 Token works fine . Below are are status message if i visit status page:
Token types are not defined but have tokens
$info['types']['node']
$info['types']['term']
$info['types']['vocabulary']
$info['types']['file']
$info['types']['user']
$info['types']['current-user']
Warning
Tokens or token types missing name property
$info['types']['date']
$info['tokens']['node']['url']
$info['tokens']['file']['size']
$info['tokens']['user']['url']
$info['tokens']['date']['custom']
Thanks,
Krishna
Comment #101
andylarks commentedI'll add my bit to agree that this is an error with PHP7.4
Any suggestions on how to solve greatly appreciated...and a little urgent, because I have a live site losing all their metatags!
Thanks in hope...
Andy
Comment #102
tomarnold2 commentedAndy,
I was seeing the same thing and not sure what the heck was going on.
In my case, the odd behavior showed-up because of a duplicate constant definition in two modules. I'm not clear exactly why this would cause the tokens to be blown away, but there you go. Look to see if there's a weird error you're getting for a duplicate global/constant definition or something else.
The only other solution I have for you -- which is the path I also took -- is to downgrade to 7.2.x.
Good luck.
Tom
Comment #103
andylarks commentedHi @tomarnold2
Thanks for the pointer - sorry for the slow reply. The probably initially seemed to magically resolve itself, but has now resurfaced on another site.
Any pointer on how on earth I find duplicate constant definitions across modules?
...or does anyone else know of a way to solve this?
Many thanks
Andy
Comment #104
andylarks commentedFWIW:
I've opened a new issue for the PHP7.4 related element of this here:
https://www.drupal.org/project/token/issues/3192956
Comment #105
andylarks commented...and in case someone gets this far:
>>> Downgrading PHP to PHP7.2 "fixed" this issue for me.
Please see: https://www.drupal.org/project/token/issues/3192956
...where I've raised this as a PHP7.4 compatibility issue
Comment #106
pamelalies commentedI was trying to track down this issue for a couple of months, and I finally found the solution for our sites! I thought I would post it here in case anyone else might have the same root cause - because it wasn't an easy one to track down.
I know a lot of people mentioned that it started happening after upgrading PHP to 7.4. In our case the problem was caused by the Colorfield module, which has some of the "curly braces" code, which is deprecated in PHP 7.4.
I applied this patch to our installed Colorfield module, and it fixed this issue that's been plaguing us.
https://www.drupal.org/project/colorfield/issues/3163653
You wouldn't think that a module throwing a warning would break so many other things, but in this case it did. If this isn't your exact problem, you might try fixing any other curly braces deprecations in any other modules you might have installed and see if it helps you as it did us.
Comment #107
bkaernel commentedSame problem for me with Drupal 7.101 - Php 8.2.25 - 5.5.68-MariaDB
My tokens [node:title] and others was invalid with the module autopath.
Token types are missing : $info['types']['node'] etc...
I search a long time. Install and re-sinstall modules and clean all caches.
At the end, i found a folder outside my root call "drupal_temp" whith folders of old modules and others.
I delete all this folders and my problems has been resolved !
Comment #108
apmsooner commented