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.
The values of a CCK Computed field, whether it's stored in db or calculated on-the-fly, isn't replaced by the "Replacement patterns".
Comments
Comment #1
fagodo they appear in the replacement pattern list?
Comment #2
kvaes CreditAttribution: kvaes commentedyes, but when processed, they remain in their syntax state
Comment #3
fagoas replacement of other fields is working fine, I suppose this is a bug of the computed field token integration, which might be in the token module or in the computed field module itself.
Comment #4
kvaes CreditAttribution: kvaes commentedmy bad, I had two content types, both with a field containing price
content type x had a price calculated (thru cck computed field) that pointed to the price of content type y
I saw the non computed-field one
as i've just read thru the requests of the computed field project, it shows that the computed field doesn't support tokens (yet?)
thanks for your help so far, gonna see if I can patch the cck field to provide token functionality
Comment #5
kvaes CreditAttribution: kvaes commented(forgot to close this one)
my own mistake, no code error