Hi Ben

I'm afraid, not :(

However, we might have a potential sponsor to include MyTokens into the communication templates, product descriptions, etc. in the next upcoming release. The sponsor did not need it to be in the XSLT scripts though.

I'm curious, how do you intend to use tokens (or MyTokens) if it was available in the XSLT scripts? What do you plan to do with it? We can consider the work if it makes sense.

Thanks!

MyTokens support would allow for the creation of some awesome dynamic scripts without having to jump through major programming hoops to get things to work semi-dynamic. For example, creating Promotions for coupon code that work on only a select number of products. Since you can't query the database from the XLT script, the only way is to hard-code all the product variant id's that are eligible for discount in a very long IF statement block, or a long delimited string to be used in a compare function.

MyTokens would give the ability to query the database directly, pulling out all the Variant ID's for a specified criteria (ie: Product Name). Then the XLT code can be written in a more generic way, so that should the database items change, no need to change the XLT as well. It would allow for less manual maintenance, and having to remember all the areas that need to be maintained on changes.

Thank you for sharing. It sounds like a great idea. We'll evaluate the feasibility and impact when we implement the MyTokens.

I just checked and noticed that StoreFront v11.x was released (I am running on 10.x right now).

I read the release notes and see that DNNSharp's MyTokens has been incorporated in some areas (Product Description & Base Communication Templates). I just want to verify, does that mean MyTokens still does not function within XSLT action scripts?