Miva Merchant 4.00 Release Notes
Posted by Wayne Smith on 08 July 2009 10:37 AM
Miva Merchant 4.00 Release Note
Miva Merchant 4.00 requires the Miva Engine 3.91 or higher to be installed and
1. Simple Administration
The default screen for a new installation or a new administrative user, Simple Administration guides users step-by-step through the process of creating a store. A checkmark displays next to each completed step, and the next step automatically displays. Users can revisit completed steps at any time, and move between Simple and Advanced Administration with a single mouse click. When a user logs out, Miva Merchant will log that user back into the same interface.
2. Attribute templates
Attribute templates consist of one or more attributes and applicable options. They can be assigned or copied to products. Assigned attribute templates can be changed globally by updating the template. Copied templates can be edited within each product without affecting the template. A field is included in Product Import, with a choice to assign or copy the attribute template(s).
3. Affiliate program
Allows Merchants to set up an affiliate program and offer commissions based on traffic, purchases, or both from customers sent to the site by an affiliate. The affiliate program creates payout reports that are viewable by the administrator. The affiliate can view the current commission and payout status on the Affiliate Information page of the Store Interface. The administrator can configure the feature so that affiliates are created automatically at sign-up from the store, only after approval by an administrative user, or can only be entered by the administrator.
Allows merchants to track inventory levels for products in the store. Stock levels and stock level messages are configurable globally and on a product by product basis. The stock level messages display in the store interface, and can warn customers of low or out-of-stock products. Sold out products can also be hidden. Email can be sent when low or out of stock levels are occur. Inventory fields are included in Product Import.
5. Added a percentage to Price Percentage Table Shipping
The shipping module can now calculate shipping charges based on a percentage of the total amount of the order.
6. Next/Previous in Edit Screens
Allows navigation through lists of items with one click. A VCR-style navigation bar and buttons allow the user to view the first, previous, next, and last items of the type being edited. For example, this feature is used in the product, customer, and category screens.
7. Select/Deselect All
Allows a user to select or deselect all of a displayed list, by clicking on !+ to check all or !â€“ to uncheck all. For example, the user might search for a certain set of products, then click !+ (check all) to add the displayed and checked products to a category. Several screens now include the check/uncheck all.
8. Basic Statistics
The Administration Interface data area displays the following information:
â€¢ Hits: Hits on merchant.mv regardless of screen, action, etc.
â€¢ Visits: Based on new baskets created.
â€¢ Orders: Based on baskets converted to orders.
â€¢ Revenue: Total of all the order totals
â€¢ Products Sold: Total of all products sold.
â€¢ Best Sellers: List of the top five selling products and the number of each sold.
Internet Host Provider: New Features
Provisioning allows hosts to preset data for a given Miva Merchant installation.
There are now two types of provisioning. Setup Provisioning, and Post Setup
â€¢ Setup Provisioning is accomplished with the site.dat file which contains a single record of pipe "|" delimited data.
The site.dat file now supports all data needed to finish setup including the Merchantâ€™s contact information and default administrative user name and password. The results of a setup that uses site.dat can now have its output returned as XML to make automated installation easier. This file is read only during the setup process and is deleted when setup is completed.
â€¢ Post Setup Provisioning is accomplished through provide.dat file which contains multiple records each of which is a command to add or modify data for the current installation.
When the provide.dat file is present, it is read every time a user logs into the administration interface. Any errors that occur while the file is processed are logged, and the provide.dat file is deleted after processing. Virtually all data the software reads can be added or modified via the provide.dat file. Including Stores, Users, Groups, Countries, States, Categories, Products, Attribute Templates, Attributes & Options, Upsale, Inventory, Affiliate Configuration, Customers, Availability Groups, Price Groups, Shipping Configuration, Payment Configuration, Order Fulfillment Configuration, Logging Configuration, and more.
Additionally, some configuration options must be set using provide.dat, including:
â€“ Settings that disable access in the administrative interface to the menus for Domain Settings, Modules, Payment, Shipping, Fulfillment and Users.
â€“ Setting a limit on the maximum number of stores that can be added for a Miva Merchant Installation.
2. Improved Administrative Security
â€¢ A configurable limit to the number of times a user can fail a login attempt and how much time that user account will be locked out after that number is reached.
â€¢ Display the number of failed login attempts to users when they log in.
â€¢ Switched from using cookies for the Administrative users to a short-lived SessionID.
Allows the provisioner to change the appearance of the administration interface to
display branding information. The provisioner places HTML and/or Miva Script
content in header and footer files for the left Administration Interface menu, the
Administration Interface data area, the About Miva Merchant screen, and the new
Simple Administration screen. Additionally, provisioners can modify the default
frameset, allowing them to have their own navigation bars or otherwise
incorporate the Miva Merchant administrative interface into the look & feel and
functionality of their existing systems.
â€¢ Headers and footers are stored in a subdirectory of the distribution directory,
â€¢ The following files are used:
â€“ h_lnav.mv: Left Administration Interface menu Header
â€“ f_lnav.mv: Left Administration Interface menu Footer
â€“ h_main.mv: Administration Interface Data Area Header
â€“ f_main.mv: Administration Interface Data Area Footer
â€“ h_about.mv: About Screen Header
â€“ f_about.mv: About Screen Footer
â€“ h_simple.mv: Simple Administration Header
â€“ f_simple.mv: Simple Administration Footer