Extends Existing Token Replacement
MyTokens inherits all token sources available in DNN (Host, Portal, User, Membership, Profile, Tab, Module, DateTime, Ticks).
New Predefined Token (Core Tokens)
Application, ServerVars, Session, Cookie, Get, Post, Params, UserRoles, URL, NavigateURL, Random
Razor Support (C# and VB.NET)
Starting with version 2.0, My Tokens supports Razor scripts, so it's now possible to write complex templates with loops and conditions. All custom tokens are available!
Spark Support
Same as Razor, Spark is an engine capable of building complex templates. The main difference between the two is that Spark is more HTML friendly; a lot of its syntax happens inside tags.
Inline Script Support
Normally, Razor and Spark templates are built from My Tokens studio then later used in modules (such as HTML module). But it also supports writing the templates directly in the content by enclosing them between ... respectively ... tags.
Tokens that Persist
Special Tokens that get their value from page state and save it in cookies or session, so after page state is lost, the token maintains its value; the tokens are GetOrSession, GetOrCookie, GetOrProfile, PostOrSession, PostOrCookie, PostOrProfile.
Gadgets Interface
My Tokens provides an XML mechanism to define gadgets, that is tokens that result in embedding some 3rd party controls on the page. My Tokens comes with gadgets for embedding YouTube Videos, Facebook Like button, Disqus, News rotator, Currency Exchange Rates, Tweeet button, Google Maps and much more.
Custom Tokens
Create new tokens as constant strings or built against Database, HTTP Server, FTP Servers or Mail Servers. Further processing of result is possible with the use of Parsers.
Database Tokens
Will run a query and fetch the results in tokens that can be used in any MyTokens-aware module.
HTTP Tokens
MyTokens will make an HTTP Request and put the response in tokens. Using the parsers, the response can be interpreted as text, json, xml or stripped using a regular expression.
File System Tokens
Tokens are built from a file loaded from disk. Paths can be specified absolute or relative to website root. How tokens are extracted depends on parsers and rules used.
FTP Tokens
This behaves the same as File System Token, except the file is grabbed from an FTP Server.
Mail Server Tokens (Experimental)
MyTokens can connect to a Mail Server using POP3 or IMAP and fetch email parts (subject, body, to, from, attachment). Currently, it's only possible to retrieve latest email; filters will be added to match emails.
Token Parsers
Once data is returned from the Token Source, further processing is made with the use of Parsers. My Tokens comes with following parsers: No Parser (data is left as it is), Strip Xml/Html tags, XML Parser, Json Parser and RegExp Parser.
Patch Standard Modules
MyTokens will automatically patch some standard modules (even if they're installed after MyTokens). Supported modules are: Text/Html, Links, Announcements, Reports, Documents, User Defined Table, Form and List, IFrame and MLHTML.
Token Replacement in DNN Skin
MyTokens provides a Skin Object that will replace tokens in Skin Files. In general, it can be included in any .ascx or .aspx file.
Advanced Caching Strategies
My Tokens provides several configurable layers for caching tokens. They are: global (per host), per portal, per role and per user.
Seamless and Quick Integration
MyTokens can be integrated with any other module both ways: to replace tokens and to export tokens that will get replaced in other MyTokens-aware modules (using the Api or using intermediate storage - database, file system, application collections).
See more features