Sebastian Leupold wrote:
please be aware, that built in TokenReplace engine has been created to provide you with some context about the current user, module, page and portal, it can be extended by custom modules with individual tokens, but it is NOT a full script language with e.g. if ... then ... else logic included. I.e. it will be easier to create a custom module for your purpose.
Hi Sebastian,
I've been reading up on custom tokens and your work & posts on TokenReplace have been a big help. What I can't find a straight forward answer for is this: are custom tokens that I create in my own module exposed to the DNN Core Modules that use TokenReplace?
For example if my custom module exposes some custom tokens by implementing IPropertyAccess & GetProperty in the info class as per your example in your post "4.6.0. A Sneak Peek (5) - Token Replace", can I then use these tokens in the Text/HTML module, or only within my own custom module?
I've had a look at the MyTokens module which allows custom tokens in a number of places, but it's a bit overkill for what we're after (just exposing half a dozen or so tokens to Text/HTML & our own custom modules) and I wonder if their patching of core modules like Text/HTML is the only way to expose custom token to other modules.
Thanks,
Jess