Copyright © 2001, William Weiland
Add insurance to the order total based on rates you establish in admin.
1) In admin, click Add Modules
2) Click the file upload button
3) Browse to find the insursub.mv file on your hard drive and upload
4) Click Add to add it to the domain
5) Click the image to the left of your store name
6) Click on the Utility Configuration link
7) Check the box to the left of Insurance by Subtotal and select Update
8) Click on Add Modules again
9) Click the file upload button
10) Browse to find the cim_ins.mv file on your hard drive and upload
11) Click Add to add it to the domain
12) Click the image to the left of your store name
13) Click on the System Extension Configuration link
14) Check the box to the left of CIM System Module for Insurance by Subtotal and select Update
In the Utility Configuration screen you will enter your store's insurance rates. The input has a guide to the left of the input field.
If you are using the Miva Merchant User Interface (mmui) you will need to make some very simple edits to the core files. Be sure to do that with a text editor (NO WYSIWYG editors) such as Programmer's File Editor (PFE) so as not to damage the mv files. ALWAYS BACKUP your unmodified mv files in case you make a mistake.
In your mmui.mv file find <MvFUNCTION NAME = "MMUI_Order_CustomerInformation" and
insert the following line just before the table with the continue button
<MvDO FILE="{g.Module_Root$'modules/util/insursub.mv'}" NAME="l.insurance_prompt" VALUE="{Insure_Prompt()}">
This module can be used in both Merchant version 3.x and 2.2x. However, there is a serious, fatal error bug in one of the Miva Corp supplied core files in versions 2.22, 2.23, and 2.24. Hence, in order to use this module in those versions of Merchant, you will need to edit the db.mv file. Be sure you make a backup of this file in case you make an error. In the db.mv file, locate the function BasketCharge_DeleteAll_Module. The MvWHILE loop needs to be closed with </MvWHILE> instead of </MvIF>. If you don't fix this, you will get an error upon checkout. Again, this bug has been fixed in Merchant 2.25 and 3.x so you only need to make the file correction in Merchant 2.22, 2.23, and 2.24.