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 fix for 2180031 changed the value of the 'sanitize' option to that is used by tokens to do token replacements during metatag processing. In our use case, we need the [node:summary] and [node:description] tokens to pass through _text_sanitize() in order to invoke text filter processing. My fix is to convert the sanitize default value to a setting. But, does the really need to be a per-metatag setting?
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | metatag-token_sanitize-2720221-2.patch | 1.54 KB | dnmurray |
Comments
Comment #2
dnmurray CreditAttribution: dnmurray at Phase2 commentedComment #3
DamienMcKennaComment #4
metalboteThanks for this patch.
I encountered the problem with email adresses in [node:summary], which were formerly obfuscated by spamspan and now were displayed as plain in metatag description...
Worked as aspected and should be integrated as option as soon as possible, because many won't notice the side effects of fix 2180031 on customer pages.
Comment #5
DamienMcKennaThis seems to be useful for certain circumstances and doesn't break anything, so ok, cool, thanks!