Toggle token replacement in tracking codes

Created on 23 May 2016, over 8 years ago
Updated 23 March 2023, over 1 year ago

Token replacement in tracking codes is very handy, but if no tokens are used in a tracking code, and producing tokens is expensive (e.g. due to other modules or just the sheer size of a site), it can be worth providing an option to toggle whether to replace tokens or not. Here's a patch that does this -- it defaults to the current behaviour, so tracking codes continue to use token replacement by default.

I guess it would extra nice if the UI could indicate that a token-like string was matched in the code, and ask whether that was intended as a token for processing or should be skipped?! But the simple checkbox is probably sufficient, at least.

✨ Feature request
Status

Fixed

Version

1.0

Component

Code

Created by

πŸ‡¬πŸ‡§United Kingdom james.williams

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Production build 0.71.5 2024