Scot's Scripts Miva Merchant Module Support

Scot's Scripts Miva Merchant Module Support

Support for our Miva Modules.
Find answers to your installation and usage questions.
This is the place to start if you have questions about our modules. Most of our Miva Modules are fully documented. Do not hesitate to contact us if you can't find the answer you're looking for!

Looking for something? Start typing here:

Scot's Blogger is used to created this support system.

ProContentX Basic Instructions

last updated

Page Item

ProContnetX must be assigned to any store template that you want to use it on.

Displaying Content

When editing content or snippets click on the icon for page items that can be used to display or load content.


Make sure the visual editor settings are set.

If you have been using ProContent 3 there is an import option in the settings. Note that if you import, the ProContentX data tables will be initialized, so import before creating any new fields and content entries.


Fields are similar to custom fields in Miva Merchant in that you create a field and then create content for store items (products, categories, and pages.)

When editing a field there is also a place to create visual or code content. This is the lowest level default content for the field and is what should be used for basic fall-back or global content.

Note that there is also default content for the field for each store item, however this is an advanced way of using ProContentX that most users won't need to deal with.


Click the Content link to create content for a field while editing a store item. The content you create is "attached" to that store item in a similar way to how custom fields work.

Global Content

Each store item can have it's own custom content as well as it's own default or global content. That is, if you are editing "Product A" for example and create global content (clicking on the icon) then that will be default product content for that field.

Content Hierarchy

Content displayed using the most basic page item has an order of importance in how it's loaded. For example, this page item loads content for the field some_field_code:

<mvt:item name="procontentx" param="some_field_code" />

The content will display in order of importance.

  1. product content
  2. product default content
  3. category content
  4. category default content
  5. page content
  6. page default content
  7. field default content

So, if you're on the product page and there is product content based on l.settings:product, it will be displayed and the process stops.

If you're on the product page and there is no custom product content ProContentX will try to display default product content, and if that's not found, it will display the field default content if it exists.

Advanced Hierarchy 

In a more confusing situation, say you have a field called item_seo and there is content for all store types, it will first try to display the product content, but if it's not found it will try to display related category content if it can, and then move down to page content and then it will try default field content.

To do this, it looks for l.settings:product, l.settings:category, and l.settings:page.

It's probably a good idea to keep the fields organized in a way so that product related fields are just used for products, category related fields for categories, etc...

Visual vs Code Editor

Visual Editor: This content is basic html and text. You can not use SMT/Template code in the editor.

Code Editor: If the code editor is selected, you can use SMT/Template code in your content. It can interact with other code in the page template using l.settings and global variables.


Snippets are a powerful feature that let you create easy to use content blocks and/or pseudo-functions out of SMT code.

Snippets can be used the same way as theme content sections. Some uses for snippets would be to control meta data, contact forms, anything you'd use theme content for. The advantage of using ProContentX snippets is that you can access them while editing products, pages, and categories, so you don't have to jump around to different areas of the store.

Snippets are fully integrated into the template system so you can use and set l.settings and global variables in snippet code (when using the code editor.)

Loading Content

There are times when you may want to load content rather than displaying it. This is especially useful for snippets when they are being used a pseudo SMT functions and don't need to display output.

Clicking the icon when editing content will give you the page items that can be used to display and load content.

You assign ProContentX data to a variable or not. By default, ProContentX will load content into l.settings:procontentx:_product:content for products, _category:content for categories and _page:content for pages.

Display the content simply with a page entity, such as: &mvt:procontentx:_product:content;