Merchant Optimizer Users Guide by ewghwehws

VIEWS: 1 PAGES: 23

									            Merchant Optimizer User Guide
                                                  Version 5.00




Miva Merchant Speed and Search Engine Enhancement Module
Contents
Overview...................................................................................................... 4

Installing Merchant Optimizer...................................................................... 4

       Uploading the Module to Your Server ......................................................... 4

       Assigning a Module to a Store .................................................................. 6

       Adding the License Key............................................................................ 6

Setting Up Merchant Optimizer for the First Time ........................................ 7

Creating Optimizer Pages............................................................................. 8

Creating Optimizer Category and Product Pages .......................................... 8

       Overall Choices ...................................................................................... 9

              Update ALL Items............................................................................ 9

              Update CHANGED Items................................................................... 9

Page Rendering Problems .......................................................................... 10

Tips and Tricks ........................................................................................... 11

       Making Search Engine Robots Bypass Merchant .........................................11

       Robots.txt Tutorial .................................................................................11

              User-agent ....................................................................................12

              Disallow:.......................................................................................12

              White Space & Comments ...............................................................12

              Examples ......................................................................................13

       Shopability of Optimizer Pages ................................................................13

              Basket Redirect Modules: ................................................................13

       Maximizing Optimizer Page Usage ............................................................14

              Static Category Tree .......................................................................14

              Using .htaccess Rewrites .................................................................15

       By Passing Dynamic Content on Static Pages .............................................16

       Cleaning Up Old Files .............................................................................16

Optimizer Compatibility Issues .................................................................. 16

              3rd Party Modules ...........................................................................17

              Search Friendly Links ......................................................................18
             Pagination .....................................................................................18

             Javascript Issues............................................................................19

Store Front Tab .......................................................................................... 20

      Create/Copy Store Front .........................................................................20

      Update/Create Store Front Page ..............................................................20

      Copy Store Front Page to Site Root ..........................................................20

Category Pages .......................................................................................... 20

      Update.................................................................................................20

             Pagination .....................................................................................20

             Update .........................................................................................20

Product Pages ............................................................................................ 21

      Update.................................................................................................21

Module Setup ............................................................................................. 21

      Merchant URLS......................................................................................21

             Base URL ......................................................................................21

             Merchant Store Front ......................................................................21

             Merchant Category .........................................................................21

             Merchant Product ...........................................................................21

      Optimizer Files ......................................................................................22

             Home Page Directory ......................................................................22

             Home Page Filename ......................................................................22

             Category Page Directory..................................................................22

             Product Page Directory....................................................................22

      Preferences...........................................................................................22

             On Admin Updates .........................................................................22

             File Name Case ..............................................................................22

             Page Count ...................................................................................23

             Replace spaces (' ') in codes with .....................................................23
Overview
     Merchant Optimizer increases your server’s response time, bandwidth usage
     and overall presentation of speed. Optimizer does this by creating standard
     HTML pages that are virtually exact duplicates of the dynamically generated
     Miva Merchant store pages. By keeping “just looking” store browsers in
     these static pages, you save your web server’s valuable resources for
     customers who are actually buying.

     Web servers can typically serve HTML (static) pages 10 to 100 times faster
     than a similar dynamically generated page. Even on fast hosts, with the finely
     tuned sites, you can benefit from the static verse dynamic page display. This
     is because static pages can be cached (saved) on the users local computer.
     Therefore, when the page is requested a second time…the server doesn’t
     even need to download the page. And, no matter how fast your site is,
     nothing will ever come close to plain old HTML.

     In addition, Optimizer produced HTML pages are more appealing to most
     search engines because of their “search friendly naming” and faster download
     time profile. And when search engines (search robots) come calling to look
     over your site Optimizer can ensure that event does not impact on overall site
     performance. Keep in mind that search robots can typically request a new
     page or screen 10 to 100 times faster than a human can. Using a simple
     “robots.txt” file can lessen this effect. (See Using Robots.txt File.)

     Merchant Optimizer installs quickly as a standard Utility module. Once
     installed and registered, you need only accept the defaults presented by the
     Setup Tab or, in most cases, make a single change defining where on your
     server you want to locate the index.html or “home page” page of your static
     pages. You can choose to setup the home page to work along side of your
     existing index page of your site, or use it to replace the current home page of
     your site.

     The other settings can generally left as is, but provide great flexibility to
     leverage the power of Miva Merchant within static pages. For example you
     could create a separate set of pages for affiliates by defining a different home
     page path, and adding the affiliate link to the category and product paths.
     You could also use this method to embed a unique code that will let you track
     entries from the static pages.


Installing Merchant Optimizer
     The Merchant Optimizer module installs as a standard Miva Merchant utility
     module. You should first extract the Module from its "zipped" format and save
     it somewhere convenient on your PC such as your C:/ drive.

Uploading the Module to Your Server
     You can manually FTP the module file to your server, but most people find it
     easier to use the upload feature in the Merchant Administration screen.

     To upload the module to your server
Login to your Merchant Administration screen.

If you are in "Simple Administration mode, click the "Switch to Advanced
Administration" link




On the left-side frame of the Merchant Admin, click [Add] next to the Modules
folder.
     In the main screen area, click the browse button to open the Upload File
     dialog.




     In the Upload File dialog, click the Browse button to locate the file
     pm_optimzer5.mvc.

     When located, click Upload to send the file to your web server. (If you are
     updating the module, be sure to select the Overwrite checkbox.)




     With the module listed in the Add Module screen, click Add. In the screen that
     appears, you should see confirmation that the module has been added. You
     now need to assign the module to a store.

Assigning a Module to a Store
     After you've uploaded the module to your server, you can assign it to a store.

     To assign a module to a store
     In the left-side frame of the Merchant Administration screen, open Stores,
     then open the name of the store to which you want to add the module.

     Click the Utilities link. (You do not need to open Utilities.)

     In the Store Utility Configuration screen, mark the box labeled Merchant
     Optimizer, and then click Update.

     The left-side area should refresh, and the Merchant Optimizer link should
     appear underneath the Utilities folder.

Adding the License Key
     After you've assigned the module to the store, your next step is to access the
     module and enter the license key provided.

     To add the license key
     Under your store's Utilities folder, click the Merchant Optimizer link. This
     should open the Merchant Optimizer Module Setup tab in the right-hand side
     of the screen.
    From your fulfillment email, copy the license code provided, and then paste it
    into the License Key box.

    Click Update. You are now ready to setup and use the Merchant Optimizer
    module.


Setting Up Merchant Optimizer for the First Time
    Typically you need only change the settings in the Optimizer Files group of
    the Module Setup tab. These settings tell Optimizer where you want to save
    your generated files.

    The overall tasks for using Optimizer for the first time are:

    !   Make your settings in the Module Setup tab. Typical settings are
        appropriate for most users: Typical First Time Setup. Use of advanced
        setting are covered in Appendix A – Module Field Explanations.

    !   Make a test run of your Merchant Storefront.

    !   Make a test run of all your product pages and then category pages.

    !   Make final review of the Optimizer pages, then go live.

    If you have any problems while performing these tasks, consult our
    Troubleshooting section.

    Typical first time setup
    !   In the Optimizer Files group, change the Home Page Directory setting to
        your desired directory for Optimizer pages. For example, if you type
        store, your static pages will appear when you enter the following URL:

        http://www.phosphormedia.com/store/

        Note: For Search Engine optimization, you should have a path that is relevant to
        customer searches. For example, if you sell woman's shoes, you might want to use
        woman-shoes as your Static Page Directory.
        Note: Optimizer has an option to copy your store’s Store Front screen to the root of
        your site, thus allowing visitors to see Optimizer created pages when only the domain
        name is entered. However, the product and category pages will still be stored
        underneath the subdirectory you use here.
    !   If desired, use Category Page Directory and Product Page Directory boxes
        to change the subdirectory name used for products and categories.

    !   Optionally, you can use Home Page Filename to set the name for the
        created Store Front (Home) page. However, unless you know why you
        should do this, we recommend that you just leave it as index.html.

        Tip: You can setup Optimizer to use a temporary directory for testing if you plan on
        using your Optimizer produced store front page as your site’s home page and you
        are concerned about folks seeing a “work in progress.”
   That’s it for the most part. You might want to review the options under
   preferences, but if you don’t understand their significance, you should just
   use the defaults.


Creating Optimizer Pages
   We recommend that the first page you tell Optimizer to create is a copy of the
   Merchant Store Front. So you can easily review the results.

   By default this page is created in its own subdirectory. You need to either
   point to it from some other page (produced outside of Optimizer) or use the
   Optimizer controls to copy the Store Front page to your root directory and
   replace your current home page.

   To update the Optimizer store front page
   1. Click the Store Front tab.

   2. Choose to either Update/Create Store Front Page, or Copy Store Front to
      Site Root depending on how you are using Optimizer pages.

   3. Click Update.

   Tip: We recommend that you review the created page each time you update it. A link to
   this page is provided in the Store Front tab.
   Once Optimizer creates the store front page, you just view it (we provide a
   link right to that file) to ensure that it matches the look of your Merchant
   store front screen. Since this page is created programmatically, some “bad
   habits” of HTML editing create less than optimal rendering of the Merchant
   Store Front screen. See, “Page Rendering Problems”, later in this guide.

   After creating and reviewing the store front page, you can now proceed to the
   Category or Product tabs and create the static pages that mirror your
   categories and products.


Creating Optimizer Category and Product Pages
   Category and Product Pages tabs have essentially the same behavior, choices
   and processes.

   You can use the Category Pages and Product Pages tab to create and update
   your Optimizer pages. Depending on your Module Setup|Preferences
   Optimizer will track category and product updates made through the
   Merchant Admin. If you have Run Optimizer on Product/Category Update
   (recommended) selected, pages are automatically updated when that item is
   updated. If you have Ask Before Running Optimizer, and did not check the
   Optimizer Update box in the items edit screen, Optimizer will list the updated
   items in its relevant tab.

   On the Category/Product tabs have two overall choices and two or many
   individual choices as follows:
Overall Choices
     You can elect to have Optimizer simply update ALL items or update only
     CHANGED items.

     Update ALL Items
     For update ALL, you can elect to have Optimizer either Update, Ignore, or
     Delete the associated item’s static page. By default, Optimizer chooses the
     most logical settings for these items. Here’s what the settings mean:

     Update           A new copy of the ALL active category or product pages are
                      created, overwriting the existing pages.

     Ignore           A new copy of these pages is NOT created.

     Delete           An existing copy of the page (if any) is deleted. (Note, if
                      using Optimizer primarily for Search Engine optimization, we
                      recommend using a 302 permanent redirect if you are
                      deleting products or categories.)

     Active Page      Any category or product page that is viewable by the general
                      public.

     Inactive Pages   Any category or product page that is NOT viewable by the
                      general public. For example, a product in an availability
                      group or a product marked active



     Update CHANGED Items
     For update CHANGED items, you can elect to have Optimizer either Update,
     Ignore, or Delete the individual changed items associated static page. By
     default, Optimizer chooses the most logical settings for each item. Here’s
     what the settings mean:

     Update           A new copy of the category or product page is created,
                      overwriting the existing page.

     Ignore           Optimizer ignores this changed item but removes it from the
                      list of changed items after Optimizer runs.

     Delete           An existing copy of the page (if any) is deleted. (Note, if
                      using Optimizer primarily for Search Engine optimization, we
                      recommend using a 302 permanent redirect if you are
                      deleting products or categories.)

     Active Page      Any category or product page that is viewable by the general
                      public.

     Inactive Pages   Any category or product page that is NOT viewable by the
                      general public. For example, a product in an availability
                      group or a product marked active
   When you first run Optimizer, you will probably want to run the Update ALL
   option. Afterwards, as you add or update products and categories through the
   Merchant Admin, Optimizer will track these changes and when you return to
   the Optimizer screens, display only those categories and products that require
   updating. Alternately, Optimizer presents a tab in the Edit Category or
   Product admin screens where you can update categories or products static
   page from that Edit admin screen.

   To create a complete set of category or product pages
   1. Click the Category Pages or Product Pages tab.

   2. Select the Update ALL (items) option.

   3. Click Run. Optimizer will cycle through all of your categories updating,
      ignoring or deleting then according to the settings.

   To update existing category pages
   1. Click the Category Pages tab. The first 25 of any categories that have
      been updated through the Merchant Admin should be listed below.

   2. To update all categories (even the ones that are not shown) select the
      Update All Listed option.

   3. To update only specific categories, choose the Update/Remove All
      According to Checkboxes below option. Then, in the check boxes below,
      choose either the Update or Remove Option. (If the category was deleted,
      it will appear as an update, and you will need to mark the Delete
      checkbox.)

   4. Click Update. Optimizer will update the selected categories.

   Note: Remember, if Run Optimizer on Product/Category Update (recommended) is
   selected, pages will update automatically and will not be displayed in the item’s tab.


Page Rendering Problems
   Since Optimizer creates its pages programmatically, some “bad habits” of
   HTML editing create less than optimal rendering of the Merchant Store
   screens. The following common errors, once corrected, will not only ensure
   better Optimizer pages, but, will also make your Merchant store more
   compatible with a larger number of browsers.

   !   When creating tables to contain images that must abut one another, keep
       that table, and all its cells on one line, and eliminate all extraneous
       spaces. For example:
       <table><tr><td><img src=”start.gif”></td><td><img src=”middle.gif”></td><td><img
       src=”end.gif”></td></tr></table>
     !   When writing or copying Javascript code, make sure you use HTML
         comments to enclose the Javascript code. For example:
         <script language="JavaScript">

         <!—

         function PopWinSP(URL)
         {   popupWin = window.open(URL, 'Filename', 'width=460,height=560,scrollbars=yes');
             window.top.name = 'opener';
         }

         //-->

         </script>

     !   Use correct quoting when creating Javscript Links. For example:

         <a href=’javascript:window.open(“foo.html”)’>


         is not correct. It should be

         <a href=”javascript:window.open(‘foo.html’)”>



     !   When writing or copying Javascript code, make sure all lines are correctly
         terminated with the JavaScript line termination character “;”. For
         example:
         function PopWinSP(URL)
         {   popupWin = window.open(URL, 'Filename', 'width=460,height=560,scrollbars=yes');
             window.top.name = 'opener';
         }



Tips and Tricks
     Here are some ideas to help you get more value from Merchant Optimizer.

Making Search Engine Robots Bypass Merchant
     While it may seem counterintuitive for us to suggest that you block search
     engines from scanning your site; that’s exactly what we do suggest in some
     cases. When search engines scan Merchant sites, they can use up a
     tremendous amount of server resources as they can “click” links (including
     add to basket links) several times a second.

     …but what about search engine listings?

     Your site will be more than adequately represented in search engines by the
     Optimizer produced pages, so in essence, there is no need at all for Search
     engines to crawl your Merchant generated pages.

     …so how do I create a robots.txt file?

Robots.txt Tutorial
     Search engines will look in each directory of your site for a file named
     "robots.txt". For example: http://www.mydomain.com/robots.txt. This file
     tells the search spider which files it may look at in order to index and rank..
     This system is called, The Robots Exclusion Standard.
The format for the robots.txt file is special. It consists of records. Each
record consists of two fields : a User-agent line and one or more Disallow:
lines. The format is:
<field “:” <value>

The robots.txt file should be created in Unix line ender mode! Most good text
editors will have a Unix mode or your FTP client *should* do the conversion
for you. Do not attempt to use an HTML editor that does not specifically have
a text mode to create a robots.txt file.

User-agent
The User-agent line specifies the robot. For example:
User-agent: googlebot

You may also use the wildcard character "*" to specify all robots:
User-agent: *

You can find user agent names in your own logs by checking for requests to
robots.txt. Most major search engines have short names for their spiders.

Disallow:
The second part of a record consists of Disallow: directive lines. These lines
specify files and/or directories. For example, the following line instructs
spiders that it can not download email.htm:
Disallow: email.htm

You may also specify directories:
Disallow: /cgi-bin/

Which would block spiders from your cgi-bin directory.

There is a wildcard nature to the Disallow directive. The standard dictates that
/bob would disallow /bob.html and /bob/indes.html (both the file bob and
files in the bob directory will not be indexed).

If you leave the Disallow line blank, it indicates that ALL files may be
retrieved. At least one disallow line must be present for each User-agent
directive to be correct. A completely empty Robots.txt file is the same as if it
were not present.

White Space & Comments
Any line in the robots.txt that begins with # is considered to be a
comment only. The standard allows for comments at the end of
directive lines, but this is really bad style:
Disallow: bob #comment
Some spider will not interpret the above line correctly and instead will
attempt to disallow "bob#comment". The moral is to place comments
on lines by themselves.

White space at the beginning of a line is allowed, but not recommended.
         Disallow: bob #comment

     Examples
     The following allows all robots to visit all files because the wildcard "*"
     specifies all robots.
     User-agent: *
     Disallow: *

     This one keeps all robots out of your merchant pages, assuming that your
     Merchant directory (the one where merchant.mvc resides) starts at /mm5/.
     User-agent: *
     Disallow: /mm5/

     The next one bars all robots from the cgi-bin and images directories:
     User-agent: *
     Disallow: /cgi-bin/
     Disallow: /images/

     This one bans Roverdog from all files on the server:
     User-agent: Roverdog
     Disallow: /

     This one bans keeps googlebot from getting at the cheese.htm file:
     User-agent: googlebot
     Disallow: cheese.htm


Shopability of Optimizer Pages
     To make Optimizer pages friendlier to your shoppers, we suggest using a
     basket redirect module. These modules (a list follows this section) change the
     behavior of Merchant so that when a customer adds a product to their basket
     from an Optimizer page, they are taken to the store’s Basket Screen where
     they are given an option to either review their basket contents, checkout, or
     continue shopping. Clicking Continue Shopping will take them back to the
     Optimizer page from where they entered the Basket screen. In addition, to
     keep customers in Optimizer pages as much as possible, make sure your
     store is setup to NOT show the category tree on the Basket screen. (This is
     the default behavior, however many third party modules offer this ability.)

     Basket Redirect Modules:
     VikingCoders:           Goto Basket/Continue Shopping

     NetBlazon:        Add Product Redirect to Basket
Maximizing Optimizer Page Usage
    The basic concept improving performance with Optimizer is to keep your
    customers browsing through your store’s static pages. In the most basic
    setup, you can use the static storefront page that Optimizer creates as your
    home page, and when customers click a category, they view the products in
    that category (or additional category selections) in a static page produced by
    Optimizer.

    However, there are a number of ways customers can “fall into” the
    dynamically generated Merchant screens. For example:

    If they do a search and then view a product from the search results, they will
    be viewing a Merchant generated screen. In addition, the category tree (if
    present) will also link to Merchant generated screens.

    If they view their basket screen, and the category tree is present on this
    screen, the links in the tree will point to Merchant generated pages.

    There are a number of techniques that will steer the client back into the
    Optimizer produced pages.

    Static Category Tree
    If your store’s categories do not frequently change, you can use a static
    category tree in place of the Merchant generated tree. You can use DHTML or
    JavaScript categories trees to make it easier to update and navigate.

    The basic process is to:

    1. Create your static tree using the DHTML or JavaScript script of your
       choice.

    2. Add the tree in Merchant’s Category Header container, ending the script
       with the HTML comment tag <!— .

    3. In the Merchant Category Footer, close the HTML comment tag (-->).

       Optionally, you may want to create a top level category that contains all
       the other categories as child (or sub-categories). This will help speed up
       the processing and display of the dynamic category tree. Even though its
       hidden, the dynamic tree is processed and its output included in the
       source of the HTML page.
Using .htaccess Rewrites
If you have access to .htaccess files and your host supports Mod Rewrite, you
can add a “rewrite” rule that takes a Merchant URL such as:
www.somedomain.com/mm5/merchant.mv?Screen=CTGY&Category_Code=t
hisproduct

and translates it to:

www.somedomain.com/mystore/product/thisproduct.html

An example of how the rewrite code would work for categories and Products is
shown below (ask your hosts for specifics):
RewriteEngine On

RewriteCond    %{QUERY_STRING} !pm:optimizer [NC]
RewriteCond    %{QUERY_STRING} Screen=PROD [NC]
RewriteCond    %{QUERY_STRING} Product_Code=(.*)& [NC]
RewriteRule    ^(.*) http://www.domain.com/opt_dir/product/%1.html?
[R,L]

RewriteCond    %{QUERY_STRING} !pm:optimizer [NC]
RewriteCond    %{QUERY_STRING} Screen=PROD [NC]
RewriteCond    %{QUERY_STRING} Product_Code=(.*)$ [NC]
RewriteRule    ^(.*) http://www.domain.com/opt_dir/product/%1.html?
[R,L]

RewriteCond    %{QUERY_STRING} !pm:optimizer [NC]
RewriteCond    %{QUERY_STRING} Screen=CTGY [NC]
RewriteCond    %{QUERY_STRING} Category_Code=(.*)& [NC]
RewriteRule    ^(.*) http://www. domain.com/opt_dir/category/%1.html?
[R,L]

RewriteCond    %{QUERY_STRING} !pm:optimizer [NC]
RewriteCond    %{QUERY_STRING} Screen=CTGY [NC]
RewriteCond    %{QUERY_STRING} Category_Code=(.*)$ [NC]
RewriteRule    ^(.*) http://www. domain.com/opt_dir/category/%1.html?
[R,L]
Replace www.domain.com with your domain

Replace the /opt_dir/ directory with your Home Page setting in the Module
Setup tab.

IMPORTANT: You need to enable .htaccess rewrite on the server. (Ask
your host.)
     Special thanks to David Hubbard of www.Hostasaurus.com and Remik
     of www.dotcomhost.com for their contributions to the htaccess
     rewrite rules.

By Passing Dynamic Content on Static Pages
     If you have customer specific dynamic content on your store front, category
     or product pages, you can easily bypass the display of this information when
     running Optimizer. For example, if you are using a “mini-basket” or a
     “Welcome Back: Customer Name” display, you can either replace them with
     something more generic such as a link to the basket or a general “Welcome to
     our store” message

     The basic method is the same for all types of data: You add a special variable
     to the Optimizer page call settings, and then test for that variable before
     displaying the dynamic content. Here is an example of hiding a mini-basket
     display.

     To by pass dynamic content
     !   On the appropriate page template, you can wrap the dynamic content in
         an IF statement. For example:

         <mvt:if expr="g.pm:optimizer">
             Items to appear on static pages only
         <mvt:else>
             Items or code to appear on dynamic pages only
         </mvt:if>


     That’s it!

Cleaning Up Old Files
     You can easily remove category and product pages that are no longer in use.

     To clean up old files
     1. Create a run of ALL product pages, ALL category pages.

     2. Using a standard FTP client, access your Optimizer page directory.

     3. Assuming that this is a stand-alone directory (i.e., only contains the
        Optimizer files), sort the directory view by date, and then delete all the
        older files.

     Note: You might want to create a list of these old files (again, most FTP clients have this
     feature) and use the list of old file to create a “301” permanent redirect directive. This is a
     standard .htaccess command that tells servers and search engines that the page is not
     longer available and that they should go to the indicated page instead.


Optimizer Compatibility Issues
     Understanding how Optimizer works is the key to understanding possible
     optimizer compatibility problems. Essentially, Optimizer calls the Merchant
     screen the same as a browser would. It then copies the resulting page,
replaces Merchant specific links, removes the other dynamic specific values
(such as the session id) and then writes that file to your server.

3rd Party Modules
Since its calling dynamic pages and creating standard (or static) HTML pages,
features such as Related Products from Order History, while captured at the
moment Optimizer runs, do not update with subsequent orders until you re-
run Optimizer. This would also include modules such as “review this product”
type modules and discounts based on customers. However, most modules
that link back to Merchant to access their features work just fine. For
example, Tell a Friend, Wish Lists, discounts by product or category, etc.
Search Friendly Links
Search friendly type links are not necessary when using Optimizer, and need
to be “turned off” when running Optimizer as Optimizer cannot re-write these
types of links.

Pagination
Currently, Optimizer does not support pagination of categories. If you are
using category pagination, the first page of the category will be correctly
created as an Optimizer page. However, when the customer clicks the “Next”
button, they will be taken to a Miva Merchant screen.

A partial solution is to use Optimizer’s “Disable” pagination feature (under
Tools). This will make all your products in a given category appear on a single
screen. This is NOT recommended if you have a large number of products
(say, more than 30) in a single category. We are working on a better solution.

Note: Most customers do not like pagination anyway. They generally prefer to
scroll rather than click and wait. So, we recommend pagination not be used
anyway. Instead, consider adding better sub-categorization to break up large
numbers of products. Also, consider using attributes and options for products
that differ only in a small degree, such as size or color.
Javascript Issues
In addition to making sure any Javascript or other scripting code is properly
formatting with line termination characters, it’s a good idea to use an
“include” method for javascripts. For example, instead of adding the
javascript code to the global header as:
function PopWinDN(URL) {
        popupWin = window.open(URL, 'Filename', 'scrollbars,resize="yes",
width=540,height=600')
        window.top.name = 'opener';
}

function PopWinSP(URL) {
        popupWin = window.open(URL, 'Filename',
'width=460,height=560,scrollbars=yes')
        window.top.name = 'opener';
}

You could place the script for the code in a file called popup.js, and reference
that file as:
<SCRIPT LANGUAGE=JAVASCRIPT SRC=/popup.js></SCRIPT>
Appendix A – Optimizer Screen Reference
     This section contains brief summaries of Optimizer Admin interface elements.
     This summary is organized by “Tab” and then by control “Group”. This
     information is also available via Help link pop-ups in the actual interface of
     the module.


Store Front Tab
Create/Copy Store Front
     You can use settings to update your Store Front page
     (www.yourdomain.com/mm5/merchant.mvc?Screen=SFNT) and copy that
     page to your site's root folder to act as the home page for your site.

Update/Create Store Front Page
     When checked, Update will create a "home page" for Optimizer files according
     to your settings in the Module Setup tab. (See below.)

Copy Store Front Page to Site Root
     When checked, Update will copy the Optimizer "home page" to your site's root
     directory.

     If you choose to copy your Store Front page to your site root, it will overwrite
     your existing index.html. Therefore, we recommend testing your Store Front
     page and site in the Merchant Optimizer directory before copying this file.


Category Pages
Update
     These settings control Optimizer updates Category pages.

     Pagination
     Optimizer does not create additional static pages for paginated Category
     pages. (Besides, most users don't click through them anyway.) You can
     choose to Disable Pagination while Optimizer runs to that ALL products in a
     category will be shown on that category's static page.

     If you have a large number of products in a category, for example more than
     50, running Optimizer without pagination may cause Optimizer to time out.

     Update
     There can be two tables presented: Update ALL Categories and Update
     CHANGED Categories. You will only see the Update CHANGED Categories
     table if you have pending updates from editing categories through the
     Merchant Admin screens AND you have not selected Run Optimizer on
     Category Update in the Module Setup tab.
    Both tables have the same controls, and if both are present, you need to
    select which table controls you want to use by checking its radio button.

    The individual table contains controls that allow you to Update, Ignore, or
    Delete a type of page or specific page.


Product Pages
Update
    These settings control Optimizer updates Product pages.

    There can be two tables presented: Update ALL Products and Update
    CHANGED Products. You will only see the Update CHANGED Products table if
    you have pending updates from editing products through the Merchant Admin
    screens AND you have not selected Run Optimizer on Product Update in the
    Module Setup tab.

    Both tables have the same controls, and if both are present, you need to
    select which table controls you want to use by checking its radio button.

    The individual table contains controls that allow you to Update, Ignore, or
    Delete a type of page or specific page.


Module Setup
    Use this tab to control general settings for Merchant Optimizer

Merchant URLS
    These settings control the way Optimizer "calls" the various screens in your
    store in order to generate static versions. Since this call is the same as
    entering the store's url in a browser, they can be used to achieve a lot of
    different effects. See the Merchant Optimizer User's Guide for examples.

    For the most part, you do not need to change these settings as Optimizer
    automatically fills them out.

    Base URL
    The base url of your store.

    Merchant Store Front
    The base url needed to call your store's Store Front screen.

    Merchant Category
    The base url needed to call your store's category screens.

    Merchant Product
    The base url needed to call your store's product screens.
Optimizer Files
     These settings control the way Optimizer saves the files it creates on your
     server. You can name the main directory that Optimizer creates and its sub-
     directories for product and categories. (By default, they are called /optimizer,
     /product and /category. We strongly recommend that you rename the
     /optimizer directory to something appropriate to the products in your store.
     For example: if your site was "www.MyShoeStore.com" you would want to
     use something like /greatshoes.

     Home Page Directory
     The directory where Optimizer will create its two subdirectories, and its home
     page (index.html) file.

     Home Page Filename
     Unless required by some server setups, leave as index.html. (If you don't
     know, leave it alone.)

     Category Page Directory
     The subdirectory where category pages will be saved..

     Product Page Directory
     The subdirectory where product pages will be saved..

Preferences
     These settings control the way you interact with Optimizer.

     You can name the main directory that Optimizer creates and its sub-
     directories for product and categories. (By default, they are called /optimizer,
     /product and /category. We strongly recommend that you rename the
     /optimizer directory to something appropriate to the products in your store.
     For example: if your site was "www.MyShoeStore.com" you would want to
     use something like /greatshoes.

     On Admin Updates
     When you update a category or product page through the Merchant Admin,
     Optimizer can automatically update its corresponding static page (Run
     Optimizer on Update), or you can choose to check a box in the Merchant
     Optimizer tab to cause Optimizer to update that page (Ask Before Updating).

     If Run Optimizer is selected, and you delete, place a product into Availability
     Group, or make the product Inactive, Optimizer will delete that product's
     page. There is a similar effect on categories.

     File Name Case
     Optimizer uses the category or product code to create the file name of its
     static page. Since file names on most servers are case sensitive, it is
     important that you use ONLY one method. However, for you can select either
     to leave the case as is, force the file names to all lower case (typical) or force
     them all to uppercase.
Page Count
To prevent time outs and lessen server load, Optimizer creates its pages in
batches. The default is 20. You can increase this amount if you are on a high-
end server to somewhat increase the overall speed of updates, or decrease
the amount if Optimizer is timing out when updating pages.

Replace spaces (' ') in codes with
Optimizer uses the category or product code to create the file name of its
static page. If your codes have spaces in them, you can select whether they
are replaced by hyphens (-) or underscores (_). Some SEO folks say that
Hyphens are preferred from a SEO perspective.

								
To top