• NOTE: The following codes apply to Merchant versions 2.x, 3.x, or 4.x. They do not apply to Merchant 5.x.
• e - Editing of the mmui.mv or related MIVA Merchant core files required if you are NOT using the incredibly versatile OpenUI. See the installation document for editing procedures. If using compiled Merchant, see the note about editing the mmui.mv below.
• c - Module(s) included in the Combo bundle for versions 3.x and 4.x. Save with the bundle purchase.
• o - OpenUI 2.x-4.13 or OpenUI 4.14-4.24 only. All other modules work with both the MMUI and OpenUI.
• t - OpenUI Tokens can be used to replace code at hook points in compiled Merchant versions using OpenObjects. The OpenDesigner screen lists the OpenObjects. The OpenObjects provide a template screen which can contain both the existing hook points (backward compatibility) and the ability to move output around within the OpenObject screen.
• t2 - OpenUI Tokens can be used to replace code at some hook points in compiled Merchant versions using OpenObjects.
• t3 - Uses hook points within OpenObjects in compiled Merchant versions.
• oec - Compiled version works with or without OpenUI (optional), but is enhanced if OpenUI is used. Contact me if you have a question about this.

MIVA Merchant 2.x - 4.x Editing: Editing of the MIVA Merchant standard mmui.mv can be as few as a couple lines added to hook a specific function in a module to several different editing locations within the mmui.mv file. My favorite free editor (at least it was when I got it) is Programmer's File Editor (PFE). For those using a MAC, try BBEdit at http://www.barebones.com/ If you are using the OpenUI, there probably will be no need to edit the MIVA Corp supplied mmui.mv file because hooks are built into the OpenUI.
If you are running compiled MIVA Merchant 4.x and need to edit the mmui.mv, you will have to recompile the mmui.mv after editing. This requires that you have the compiler software or a developer with the MIVA Merchant Developer's license edits and recompiles the mmui.mv for you. For this reason, most store owners will likely install the OpenUI to eliminate the need to edit and recompile the mmui.mv. I have not updated all of the install documents to reflect the correct path to be used when editing the mmui.mv. If the code insert includes a path with a file name ending in .mv, that should be changed to .mvc. For example
<MvDO FILE="{g.Module_Root$'modules/fulfill/couponrd.mv'}" NAME="l.ok" VALUE="{Coupon_Pass()}">
would be changed to:
<MvDO FILE="{g.Module_Root$'modules/fulfill/couponrd.mvc'}" NAME="l.ok" VALUE="{Coupon_Pass()}">

Many (but not all) of the online documents are enhanced read files. The code segments in red show the code which you will add to the applicable file if editing is required. When there is code in black, surrounded by red, it is only the red you are adding. The code shown in black is already in the file you are editing. Normally you are going to copy and paste these red segments into the file you are editing. Do not "view source" to copy the segment as the source code has been modified so that it properly displays in an htm file. For example, the < has been converted to &lt; for display purposes. Hence, copy the red segment as you see it in the displayed help file.

Important note about MIVA Merchant 5.x modules. Our 5.x modules currently support the default MIVASQL database configuration in MIVA Merchant 5.x. They may support MySQL if you are NOT load balancing by placing the scripts on multiple servers and the databases on a single server. As long as the scripts are on one server, the MySQL should work too. A couple highly respected web hosts have commented on this issue.

Version changes. Over time, modules are updated within the numbered version, e.g.