Hi Joe,
I've been looking into that too, recently. It looks like you can just create your own TokenProvider class, make it inherit DotNetNuke.Services.Tokens.TokenProvider and register it in web dot config as the default one.

    public class JoesTokenProvider : TokenProvider
    {
        /// 
        public override bool ContainsTokens(string content, TokenContext context)
        {
            return false; // already determined by BaseCustomTokenReplace
        }

        /// 
        public override string Tokenize(string content, TokenContext context)
        {
            var tokenizer = new TokenReplace { TokenContext = context };
            return tokenizer.ReplaceEnvironmentTokens(content);
        }
    }

Then you can implement it however you want to implement it.

But I haven't tried it yet myself either...

Greetz,
Stefan

 

Sounds cool!

From what version on is 'Latest versions'?
And where does it reside?

Hi Joe,

I believe I did that initial implementation to better support tokenization across all modules for our Tokens Builder (formerly known as My Tokens).

We derive ours from DotNetNuke.Services.Tokens.TokenProvider, same as the built-in one (CoreTokenProvider).
Note that you'll also need to configure web config to use your provider, which if I'm not mistaken will override the default one. So make sure to inherit all built-in functionality.

Would you be interested to see the implementation we have in Plant an App?
Basically, it eliminates the need to do your own provider as new custom tokens can be created through an UI interface and become available in all modules.

Doing this from my phone but will try to give you some info. We added this to the forums module which you can see at
https://github.com/DNNCom.../Dnn.CommunityForums

First, you implement DotNetNuke.Services.Tokens.BaseCustomTokenReplace, which is the provider/router to handle replacement requests. Based on how you configure the property sources, the replacement requests are routed to each source (object) which implements DotNetNuke.Services.Tokens.IPropertyAccess. You implement a method GetProperty, which receives a property name, a format string, and other parameters.

If you want to see a simple implementation, see Dnn.CommunityForums/Services/Tokens/ForumsModuleTokenReplacer.cs

This implementation handles [DCF:*] tokens. We also have a ton more code here: Dnn.CommunityForums/Services/Tokens/TokenReplacer.cs, which implements token replacement for [FORUM:*], [FORUMTOPIC:*], etc.

One HUGE caveat. When you pass whatever source text containing the tokens, if a token is not recognized, it is removed. So you have to include property sources for USER:, PORTAL:, etc. if your source will include those tokens.

Also, nested tokens are not allowed but we implemented that for the forums module so that tokens could be embedded in the format string of a token. If you want more information on forums tokens, see https://github.com/DNNCom.../wiki/TokenReference

So...is there some example somewhere that you know of that actually

- uses the standard DNN tokens 

- allow you to expand it with your own tokens

I've tried some things (like the suggestions above) but it doesn't seem to be that simple.

Indeed if you create a custom provider and register it in webconfig, it will replace the defaultprovider.
So it only replaces your own tokens, and not the standard stuff that DNN has built in.

And it is not so easy to kind of override the default token provider.

So any examples would be great...