DNN Tokens

Jun 15, 2009 at 11:24 PM

Hi There

Is there a way to enable DNN token substitution in the output.

It Would be particulary useful inside email and text templates etc because we could use tokens like [portal:portalname] instead of hard coding the shop/site name in emails/text.

I've seen other module developers use an additional prefix on their tokens like [DNN:dnntokanename]  ie [DNN:portal:portalname] which enables us to see the token is a DNN token and not a NB-Store module token.

Peter

Coordinator
Jun 16, 2009 at 7:51 AM

Hi Peter,

The token replacement at the moment uses an expanded version of the DNN token replacement, doing the code for this is possible, but it may cause a large (or bigger) overhead in database reads and CPU.  Hence the reason I've tried to keep it to a minimum.  However I'll make a note and see if it's feasible in a future release.

Jun 16, 2009 at 11:09 AM

Thanks for the reply Dave

Don't know how DNN architecture works but understand "overhead" concerns.

With that in mind, i note the HTML/Text module adds a check box [ Replace Tokens: [ ]  ] as a way of limiting overhead unless required. Perhaps a similar options could be added to NB_Store???

Anyway just a thought and I can make do with out it.

Cheers

Peter