Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Wiped out my test server and installed the first Beta of Commons. The following was listed in my Status Report:
The following token types are not defined but have tokens:
$info['types']['taxonomy_term']
I then installed the Dec 18 DEV version on top of this and the problem still exists.
Comments
Comment #1
ezra-g CreditAttribution: ezra-g commentedThanks for the bug report!
Marking postponed pending #1529788: token types are not defined but have tokens: taxonomy_term.
Comment #2
Anonymous (not verified) CreditAttribution: Anonymous commentedThank you, ezra-g, for addressing this!
Comment #3
pdeclarens CreditAttribution: pdeclarens commentedHello,
I have the same problem with the 3.0 version and in the beta 2 version
Comment #4
quiethero CreditAttribution: quiethero commentedI have the same issue after just having installed DC
Comment #5
japerrythis is definitely a flags / commons issue. See my comment below for more information.
http://drupal.org/node/1529788#comment-7254480
Comment #6
japerryFixed! It just needed an info entry added to the follow module. This should suppress this error and give a place for the token to live :)
http://drupalcode.org/project/commons_follow.git/commit/0f3c232
Comment #7
Dave ReidThis is unfortunately only suppressing a larger error. I don't really think this should have been added.
Comment #8
Dave ReidThis is the real bug in Flag: #1965760: Flags should use the actual token type rather than flag type when adding tokens to entity types
Comment #9
japerryYes, that is correct that it temporarily fixes the flag issue. However, it does allow tokens to be used, even though its in a new type, which should be term instead of taxonomy_term.
Marking as postponed, waiting for #1965760: Flags should use the actual token type rather than flag type when adding tokens to entity types to be resolved.
Comment #10
WebSinPat CreditAttribution: WebSinPat commentedSame problem, with DC3.
I'm wondering if I should apply the fix in #6 as a stop-gap, or wait for this to be fixed correctly, pending the fix to bug in Flag?
Thanks.
Comment #11
japerryThe patch from #6 is in the commons nightly, and will be in the 3.3 release when it comes out. While it doesn't fix the underlying flag issue, it does manually create an area for tokens to be used.
Comment #12
WebSinPat CreditAttribution: WebSinPat commentedThe patch in #6 seems to have gotten rid of my error message in the status report.
Thanks @japerry for the explanation.
Comment #13
japerryI've reverted #6 , and applied a patch against flag to fix the root of the taxonomy term issue. If you get a recent version of the profile, you'll see the fix.
http://drupalcode.org/project/commons_follow.git/commit/62a9a12
http://drupalcode.org/project/commons.git/commit/bb135dc
Keeping marked as postponed until we get validation from the flag people.
Comment #14
ezra-g CreditAttribution: ezra-g commentedFolks can help get this resolved by reviewing the patch to flag that japerry rolled: #1965760: Flags should use the actual token type rather than flag type when adding tokens to entity types.
Thanks, japerry!
Comment #15
ezra-g CreditAttribution: ezra-g commentedGiven the volume and severity of remaining issues, let's postpone this for post 3.3.
Comment #16
zilla CreditAttribution: zilla commentedto clarify for other users who find this page when encountering this precise issue:
this is NOT a drupal-commons-specific issue, it appears to be related to the "message" stack, and specifically the flag within messages that will allow for one to subscribe or receive notifications (etc) for a taxonomy term. this may be the fault of flags, or messages using flags 3.x, but it will happen with any instance where one is allowed to subscribe to a term using, for example, the "sample flags provided by message subscribe module"
Comment #17
ezra-g CreditAttribution: ezra-g commentedRemoving from the 3.4 radar.
Comment #18
cosineBob CreditAttribution: cosineBob commentedJust updated a test site (7.26 - 3.9 )with 10 updates. One of them now creates this same message. The updates were:
Custom Search to 1.14
Entity API to 1.4
Entityreference prepopulate to 1.5
Flag to 2.2
Flag Abuse to 2.0
Message Subscribe to rc2
Organic Groups to 2.6
Radioactivity to 2.9
Real Name to 1.2
Adaptive Theme to 3.2 (not used)
No message prior to these updates. Not really anxious to do them one at a time but I could if that would help.
Comment #19
cosineBob CreditAttribution: cosineBob commentedSee my comment #18 regarding this message reappearing after installing updates.
Comment #20
Lan CreditAttribution: Lan commentedI am not using this Drupal Commons module, but dont know somehow the following is in my Status Report after i upgrade some modules on my site:
The following token types are not defined but have tokens:
$info['types']['taxonomy_term']
Any recommended how to fix it. Thanks.
Comment #21
goodboyLan, try this code:
You can see tokens than uses taxonomy_term token group. ( Right token group is term. ) So, you can determine problem module.
Comment #22
Chris Charlton+1 to 'goodboy' for pointing out a solution to trace down which token/module is the problem: https://www.drupal.org/node/2750053
Comment #23
Chris Charlton