Does a list of MIVA tokens/entities exists? If so, where?

[William Davis]

Does a list of MIVA tokens/entities exists? If so, where?

[Bruce - PhosphorMedia]

None that would really be helpful. The list of available variables (tokens) and their values is different for every site and every page and even every visitor. So, you need to use a tool that exposes them. Miva has a built in version called Token List (its under Utilities), and we have one called Merchant Inspector on our site. The main advantage to our version is that it runs on the front side of the site (hidden from everyone but you or your representatives) and it shows the ACTUAL values for that Site, Page, Visitor, including varaibles that may have been created on the page itself (ie, via Toolkilt or SMT code.)

http://www.phosphormedia.com/product/pm_inspector.html

[William Davis]

None that would really be helpful. The list of available variables (tokens) and their values is different for every site and every page and even every visitor. So, you need to use a tool that exposes them. Miva has a built in version called Token List (its under Utilities), and we have one called Merchant Inspector on our site. The main advantage to our version is that it runs on the front side of the site (hidden from everyone but you or your representatives) and it shows the ACTUAL values for that Site, Page, Visitor, including varaibles that may have been created on the page itself (ie, via Toolkilt or SMT code.)

http://www.phosphormedia.com/product/pm_inspector.html

Sorry Bruce, but I just don't understand. I'm coming from MM4.24c OpenUI world, and I know that is two different universes away from each other.

Not that it matters, just using this analogy because its the only one I know wherein I know you also understand (better than I do). In the "MM4.24c OpenUI" world we have a simple list of render tokens. Are you saying that in the latest and greatest version of MIVA 9.6 they opted for something do away with simplicity in exchange for complexity? If so, why?

I'm certain I am missing something here. Please elaborate. Maybe once I understand, I can stop bothering everybody on how to render something so ridiculously simple on a template as it use to be on MM4.24c OpenUI.

[Bruce - PhosphorMedia]

It was actually much the same in OpenUI 4.24...the main difference is, since there was little which could effect the number and potential values of variables, one might get by with a static 'list of' these. In MM9, you are right in the sense that its vastly more complex, therefore a static list would probably give you more trouble than it helps. Take a look at the Token List display. It can be used a start, but be aware, it won't show you variables created on the Page itself through SMT / Other Modules, but it will show you the bulk of the variables Miva generates for each page.

[Kent Multer]

In MM version 5 (and now 9), there is a new module type called "component." (More precisely, it's a new "module feature." A module can be of more than one type now, e.g. it can be both a shipping module and a system-ex at the same time.) Component modules are the ones that correspond roughly to the old OpenUI extensions. They can create template variables (l.setting:xxxxx), and they can also provide mvt:item tags that work about like the old tokens or hook points.

Each component module can create as many variables as it wants to; there's no need to explicitly register them with the store. The only way to get a complete list of them is by reading the source code of all the component modules that are in use on any given page. (Unless maybe Miva has published some documentation that includes lists of the variables that each component creates?) At run-time, of course, you can use one of the token-listing modules to get a list of all variables to which values have been assigned.

Mvt:item tags do need to be registered with the system. There's a master list that's available under User Interface > Items. And each page template has an Items tab where you can find out which ones are assigned to that page.

Hope that helps --

[William Davis]

In MM version 5 (and now 9), there is a new module type called "component." (More precisely, it's a new "module feature." A module can be of more than one type now, e.g. it can be both a shipping module and a system-ex at the same time.) Component modules are the ones that correspond roughly to the old OpenUI extensions. They can create template variables (l.setting:xxxxx), and they can also provide mvt:item tags that work about like the old tokens or hook points.

Each component module can create as many variables as it wants to; there's no need to explicitly register them with the store. The only way to get a complete list of them is by reading the source code of all the component modules that are in use on any given page. (Unless maybe Miva has published some documentation that includes lists of the variables that each component creates?) At run-time, of course, you can use one of the token-listing modules to get a list of all variables to which values have been assigned.

Mvt:item tags do need to be registered with the system. There's a master list that's available under User Interface > Items. And each page template has an Items tab where you can find out which ones are assigned to that page.

Hope that helps --

Ahhh..., that cleared things up a bit.

What if one needs to render a value on an email template subject line (e.g.: "[StoreName] - Order [#OrderNumber] confirmation. Thanks [CustomerFirstName]!"), wherein the "token" may not exists in that particular template? How would one use MIVA's or Bruce's token list from that screen?

[Bruce - PhosphorMedia]

Ahhh..., that cleared things up a bit.

What if one needs to render a value on an email template subject line (e.g.: "[StoreName] - Order [#OrderNumber] confirmation. Thanks [CustomerFirstName]!"), wherein the "token" may not exists in that particular template? How would one use MIVA's or Bruce's token list from that screen?

Token List: After you assign the module to your store, you'll see a menu item called Token List under the More menu button.
Inspector: After you install and assign the module, you'd just navigate to the email template in a browser, and click the Inspector button.

And to add to what Kent mentioned, be aware, that unlike MM4 variables can be created and modified in the page itself. For example, one could add an MVT:DO function call to create an array of Best Seller's products for example, so you have a whole new list of variables. OR, a simple SMT assign can change the value of a variable or even create one. (Which, btw Token Viewer will not see these page created variable but Inspector can.)

[William Davis]

Thanks!!!