icfoundation - Foundation Store The Foundation store is distributed with Interchange to give you a starting point with which to build your e-business. While the Foundation store is designed to be relatively easy to start with, it is still a full-featured demonstration of a number of Interchange capabilities. Once you understand the Foundation store and how it works you are well on your way to understanding the Interchange software. The following is a list of some popular features: Regardless of the number of products in a catalog, categorizing them makes them easier to find. Pick a field in the database, typically named category, and classify the products for search using Interchange. You can display a thumbnail image for the items that have images. To do this, add an image field in the database. (See the 'image' field of the products database.) You can embed searches of similar products on an individual product display page with the [query ...] or [loop ...] tags. Or, if customer data is developed, search a past order database and display products that would be of interest to that customer. You can key the placement of a review or testimonial on the existence of a file being in a certain directory. This is reasonable to do when a user is viewing a single product. By determining how users will enter and exit the catalog, complex and intelligent conditional schemes are possible, especially if the Cookies capability is exercised. However, it is recommended that simplicity be used. Consumers will not make purchases if they can't navigate their way around the catalog. It is important to remember that users will lose their session (and items in their shopping cart) if their browser does not accept cookies and they leave the site. Interchange addresses this problem by using the area and page tags. If you are using frames, source all frame panes containing Interchange links from an initial page served by Interchange. If you don't do this, the user may have multiple session IDs depending on which frame generated the link. Note that Interchange can work properly even if the browser doesn't store cookies. In this situation Interchange inserts a session ID into each URL; if the ID is preserved as the user navigates from page to page the session will remain intact. Interchange pages are contained in the catalog directory. Each individual catalog has its own base directory. The catalog directory has the following structure by default: File containing configuration directives for a particular catalog. Configuration settings established in the catalog.cfg directory will not effect any other catalogs running under the version of Interchange you are using. Subcatalogs can have differing information in a file named for that subcatalog. Directory that will be read when directives are set with the filename notation. For example, the file config/static.pages will be read when the following directive is encountered in the catalog.cfg file.
StaticPage <static.pages
This directory also contains template information used with the makecat program. File which contains catalog-specific errors. It is also where any syntax errors in embedded Perl code are shown. Directory normally used for tracking files, order profiles, and other configuration and log information. Directory that contains the pages of the catalog. This can be considered to be the "document root" of the catalog. Pages contained therein are called with the path information after the script name. For example:
/cgi-bin/simple/products/gold will call the page in thpages/products/gold.html.
file
Directory that contains database source files, including the special Interchange databases shipping.asc, pricing.asc (and other shipping database files). Directory that contains session files. The temporary or scratch directory used for various storage reasons, like retired ID numbers, search paging files, sort tests, import temporary files, etc. This is the default set by ScratchDir. It can be redefined to be located on another partition. This section describes the files located in the Foundation demo.
Template File Locations This diagram shows the directory and file structure used for the default Foundation 'templates' directory. The base will be a directory with the name of your catalog, here called CATROOT.
CATROOT/⎪⎪----templates/⎪----cart⎪----components/⎪----affiliate_receptor⎪----best_horizontal⎪----best_vertical⎪----cart⎪----cart_display⎪----cart_tiny⎪----category_vertical⎪----cross_horizontal⎪----cross_vertical⎪----modular_buy⎪----modular_update⎪----none⎪----promo⎪----promo_horizontal⎪----promo_vertical⎪----random⎪----random_horizontal⎪----random_vertical⎪----saved_carts_list_small⎪----search_box_small⎪----upsell⎪----upsell_horizontal⎪----upsell_vertical⎪----default --> foundation⎪----foundation/⎪----cart⎪----fullwidth⎪----leftonly⎪----leftright⎪----regions/⎪----LEFTONLY_BOTTOM⎪----LEFTONLY_TOP⎪----LEFTRIGHT_BOTTOM⎪----LEFTRIGHT_TOP⎪----NOLEFT_BOTTOM⎪----NOLEFT_TOP⎪----simple⎪----theme.cfg⎪----fullwidth⎪----leftonly⎪----leftright⎪----regions/⎪----LEFTONLY_BOTTOM⎪----LEFTONLY_TOP⎪----LEFTRIGHT_BOTTOM⎪----LEFTRIGHT_TOP⎪----NOLEFT_BOTTOM⎪----NOLEFT_TOP⎪----sampledata/⎪----computers/⎪----images/⎪----items/⎪----generic.gif⎪----gift_certificate_large.gif⎪----yourimage.gif⎪----thumb/⎪----generic_thumb.gif⎪----gift_certificate.gif⎪----thumb.gif⎪----products/⎪----inventory.txt⎪----merchandising.txt⎪----mv_metadata.asc⎪----options.txt⎪----pricing.txt⎪----products.txt⎪----userdb.txt⎪----reports/⎪----download/⎪----00352as.pdf⎪----11993ab.pdf⎪----22083da.pdf⎪----49503cg.pdf⎪----59330rt.pdf⎪----59402fw.pdf⎪----66548ch.pdf⎪----73358ee.pdf⎪----83491vp.pdf⎪----90773sh.pdf⎪----products/⎪----mv_metadata.asc⎪----products.txt⎪----userdb.txt⎪----tools/⎪----etc/⎪----after.cfg⎪----before.cfg⎪----images/⎪----items/⎪----os28004.gif⎪----os28005.gif⎪----os28006.gif⎪----os28007.gif⎪----os28008.gif⎪----os28009.gif⎪----os28011.gif⎪----os28044.gif⎪----os28057a.gif⎪----os28057b.gif⎪----os28057c.gif⎪----os28062.gif⎪----os28064.gif⎪----os28065.gif⎪----os28066.gif⎪----os28068.gif⎪----os28068a.gif⎪----os28068b.gif⎪----os28069.gif⎪----os28070.gif⎪----os28072.gif⎪----os28073.gif⎪----os28074.gif⎪----os28075.gif⎪----os28076.gif⎪----os28077.gif⎪----os28080.gif⎪----os28081.gif⎪----os28082.gif⎪----os28084.gif⎪----os28085.gif⎪----os28086.gif⎪----os28087.gif⎪----os28108.gif⎪----os28109.gif⎪----os28110.gif⎪----os28111.gif⎪----os28112.gif⎪----os28113.gif⎪----os29000.gif⎪----thumb/⎪----gift_certificate.gif⎪----os28004_b.gif⎪----os28005_b.gif⎪----os28006_b.gif⎪----os28007_b.gif⎪----os28008_b.gif⎪----os28009_b.gif⎪----os28011_b.gif⎪----os28044_b.gif⎪----os28057a_b.gif⎪----os28057b_b.gif⎪----os28057c_b.gif⎪----os28062_b.gif⎪----os28064_b.gif⎪----os28065_b.gif⎪----os28066_b.gif⎪----os28068_b.gif⎪----os28068a_b.gif⎪----os28068b_b.gif⎪----os28069_b.gif⎪----os28070_b.gif⎪----os28072_b.gif⎪----os28073_b.gif⎪----os28074_b.gif⎪----os28075_b.gif⎪----os28076_b.gif⎪----os28077_b.gif⎪----os28080_b.gif⎪----os28081_b.gif⎪----os28082_b.gif⎪----os28084_b.gif⎪----os28085_b.gif⎪----os28086_b.gif⎪----os28087_b.gif⎪----os28108_b.gif⎪----os28109_b.gif⎪----os28110_b.gif⎪----os28111_b.gif⎪----os28112_b.gif⎪----os28113_b.gif⎪----os29000_b.gif⎪----products/⎪----affiliate.txt⎪----area.txt⎪----cat.txt⎪----inventory.txt⎪----merchandising.txt⎪----mv_metadata.asc⎪----options.txt⎪----orderline.txt⎪----pricing.txt⎪----products.txt⎪----transactions.txt⎪----userdb.txt
Themes This section explains how themes are defined in Interchange via the STYLE variable and the theme configuration file, theme.cfg. STYLE The STYLE variable in CATROOT/products/variable.txt indicates the template style to be used as the theme for the catalog; the appropriate templates for that theme are found in CATROOT/templates/__STYLE__/. (To change the value of the STYLE variable, either edit variable.txt directly or use the table editor feature of the admin interface.) The default theme for Interchange is the Foundation demo; hence, the STYLE variable is assigned the value 'Foundation' in variable.txt. The theme is defined in catalog.cfg as follows (line numbers added):
# Here we set up the catalog theme.
1 ParseVariables Yes
2 ifndef STYLE3 Variable STYLE default4 endif5 include templates/__STYLE__/theme.cfg
Variables that make up the look and feel of the STYLE (theme) are defined in the file CATROOT/templates/foundation/theme.cfg, which is read by Interchange in line 5 above. theme.cfg The file CATROOT/templates/foundation/theme.cfg serves three purposes: It defines the THEME and THEME_IMG_DIR variables, It defines a cascading style sheet for the theme, and It defines the location of region templates according to the traffic settings for the Interchange daemon. The THEME variable is used to set the location of the region templates in the traffic settings section of the theme.cfg file. It is also used in the cart template definition file (CATROOT/templates/cart) to set the path of an image. The THEME_IMG_DIR variable is used to set image paths in the template region files and the template component files. The look and feel of the Foundation theme are defined primarily in the cascading style sheet specified in the theme.cfg file. This The Interchange TRAFFIC setting, defined system-wide in interchange.cfg, is described in the ??document??. The settings in theme.cfg pertain to the location of region templates for the high and low traffic settings. For example, if you need to define a separate set of high traffic templates, you would change the ConfigDir variable in theme.cfg to point to the directory containing those templates.
Template Definition Files The template definition files store the name and description of the template as well as components and options for that template.
templates/carttemplates/fullwidthtemplates/leftonlytemplates/leftright
templates/foundation/carttemplates/foundation/fullwidthtemplates/foundation/leftonlytemplates/foundation/leftrighttemplates/foundation/simple
Template Walkthrough -- leftonly This section is best read while viewing the file CATROOT/templates/leftonly and the 'Edit Page' page in the Content Editor of the Interchange Administration Tool. Looking at the example template definition file, all lines located between the [comment] and [/comment] tags (lines 1 and 53) control what is available in the Edit Page screen of the Administration Tool. Lines 2-5: Template specification
2 ui_template: Yes3 ui_template_name: leftonly4 ui_template_layout: LEFTONLY_TOP, UI_CONTENT, LEFTONLY_BOTTOM5 ui_template_description: Page with top/left areas.
Line 2 indicates that this file is a template for the user interface. Line 3 names the template, while Line 4 indicates the regions that comprise the template and that will eventually make up the new page that is created from the template. Line 5 provides a description used to identify the template when it appears in a Select Template pull-down menu on the Edit Page of the Administration Tool. This description can be changed or modified to better describe a new template or a template that is created from the stock templates provided with Interchange. Lines 7-8: Break
7 break:8 widget: break
This code creates a separation line in the Edit Page between sets of options. In the default Interchange installation the line is grey, but the color can be changed. Note - Changing this color applies the change to any catalog served by Interchange. Lines 10-11: Page Title
10 page_title:11 description: Page title
This code tells Interchange to display a text field on the Edit Page for entering the page title ('Title of New Page' in this example). The value entered is assigned to the scratch variable page_title and is set as a default value at the bottom of the template definition file using the following ITL:
54 [set page_title][set]
which, in turn, sets the scratch variable on the new page using the tag
[set page_title]Title of New Page[set]
The scratch variable page_title is parsed by the following code in the region template specified in the template definition file and called in the new page:
<title>[scratch page_title]</title>
Lines 13-15: Page Banner
13 page_banner:14 description: Page banner15 help: Defaults to page title
Assigns a textual title for the page to the scratch variable page_banner, which is assigned by the following ITL:
55 [set page_banner][set]
The scratch variable page_banner is set on the new page using the tag
[set page_banner]Banner of New Page[set]
The scratch variable can be parsed in the region template by this code:
[either][scratch page_banner][or][scratch page_title][/either]
This results in the page banner being displayed if defined. Otherwise, the page title is used. Lines 17-20: Members Only
17 members_only:18 options: 1=Yes,0=No*19 widget: radio20 description: Members only
This creates a radio-button form element on the Edit Page with the user can specify whether the page can be accessed if a visitor is logged in (Yes) or not (No). The default is indicated by an asterisk. The scratch variable members_only is assigned by the ITL code
56 [set members_only][set]
and set on the new page using the tag
[set members_only]0[/set]
if the page can be accessed without logging in or
[set members_only]1[/set]
if it can not. The members_only function is handled by the following code within each region template file:
[if scratch members_only][set members_only][/set][if !session logged_in][set mv_successpage]@@MV_PAGE@@[/set][bounce page=login][/if][/if]
This code says that if "members only" is set to yes, and the visitor is logged in, to display the page. Otherwise, redirect the visitor to the login page. Lines 22-23: Break
22 break1:23 widget: break
Another separation line. Lines 25-28: Horizontal Before Component
25 component_before:26 options: =none, best_horizontal=Best Sellers, cross_horizontal=Cross sell, \promo_horizontal=Promotion, random_horizontal=Random items, \upsell_horizontal=Upsell27 widget: select28 description: Component before content
This allows the inclusion of a defined component (included in the CATROOT/templates/components directory) to be displayed before, or above, the page's content. It provides a pull-down menu on the Edit Page displaying the available components. The components, identified here on line 26, can be assigned a name via the value=name convention. The scratch variable component_before is assigned in the template definition file by the ITL code
57 [set component_before][set]
It is called with the following code within the LEFTRIGHT_TOP, LEFTONLY_TOP, and NOLEFT_TOP region templates:
[if scratch component_before][include file="templates/components/[scratch component_before]"][/if]
Lines 30-33: Horizontal After Component
30 component_after:31 options: =none, best_horizontal=Best Sellers, cross_horizontal=Cross sell, \promo_horizontal=Promotion, random_horizontal=Random items, \upsell_horizontal=Upsell32 widget: select33 description: Component after content
Similar to component_before, this allows the inclusion of a defined component after, or below, the page's content. The scratch variable component_before is assigned in the template definition file by the ITL code
58 [set component_after][set]
It is called with the following code within the LEFTRIGHT_BOTTOM and LEFTONLY_BOTTOM region templates:
[if scratch component_after][include file="templates/components/[scratch component_after]"][/if]
Lines 35-38: Horizontal Item Width
35 component_hsize:36 options: 1,2,3*37 widget: select38 description: Component items horizontal
This setting allows you to choose how many items the horizontal components display. For example, the horizontal best sellers component ("best_horizontal") uses this setting to randomly select the best sellers. Notice the default is 3 if nothing is defined. It is called by the following code in the promo_horizontal and random_horizontal components in the Foundation demo.
random="[either][scratch component_hsize][or]2[/either]"
Lines 40-45: Before/After Banner
40 hbanner:41 options: =--custom--, Also see..., Best Sellers, New items, \Some of our fine products, Specials, You might also like42 widget: move_combo43 width: 4044 description: Before/after Banner45 help: Banner for Before/after component
Allows a title for the horizontal components to be defined to be displayed in a header above the component's items. It is called with the [scratch hbanner] tag and used in the Foundation demo in the random_horizontal component. Lines 47-51: Special Tag
47 hpromo_type:48 options: specials=Specials, new=New items49 widget: select50 description: Special tag51 help: Only for a horizontal Promotion
This setting is only viable when a promotion is used for a horizontal component. It tells the promotional component which row(s) to evaluate in the merchandising table for display within the component. This setting, used in the promo_horizontal component, typically correlates to the featured column of the merchandising table as follows:
[query arrayref=mainsql="SELECT sku,timed_promotion,start_date,finish_dateFROM merchandisingWHERE featured = '[scratch hpromo_type]'"][/query]
Edit Page Function Creating a page with the following specifications using the Edit Page function results in the HTML and ITL code displayed below. Specifications:
Template: Page with top/left areas.Page title: testPage banner: testMembers only: NoComponent before content: Best SellersComponent after content: Random itemsComponent items horizontal: 3Before/after Banner: New itemsSpecial tag: SpecialsContent: <P>My first HTML/ITL page!
Resulting code:
[comment]ui_template: Yesui_template_name: leftonly[/comment]
[set hbanner]New items[/set][set page_title]test[/set][set hpromo_type]specials[/set][set component_hsize]3[/set][set page_banner]test[/set][set members_only]0[/set][set component_before]best_horizontal[/set][set component_after]random_horizontal[/set]@_LEFTONLY_TOP_@
<!-- BEGIN CONTENT --><P>My first HTML/ITL page!<!-- END CONTENT -->
@_LEFTONLY_BOTTOM_@
An important point demonstrated here is the inclusion of the region templates LEFTONLY_TOP and LEFTONLY_BOTTOM through the @_VARIABLE_NAME_@ notation. These are included because of line 4 of the leftonly template definition file:
4 ui_template_layout: LEFTONLY_TOP, UI_CONTENT, LEFTONLY_BOTTOM
However, understand that you are free to change the region templates used in the file by editing the file itself or, better yet, using an existing region as a starting point for a region of your own design. The next section explains the structure of region templates.
Region Templates Interchange region templates (or "regions") are portions of HTML and ITL that are included in pages within a catalog. Using regions, along with the cascading style sheet defined in theme.cfg, allows you to control the look and feel of specific parts of each catalog page. The default Foundation region set, found in CATROOT/templates/foundation/regions, includes the following:
LEFTONLY_TOPLEFTONLY_BOTTOMLEFTRIGHT_TOPLEFTRIGHT_BOTTOMNOLEFT_TOPNOLEFT_BOTTOM
The Foundation demo uses the Variable feature extensively to simplify hand page editing. Basically, a Variable is a define that permits the substitution of text for a simple __VARIABLE__ string in a page. For example, in the test page above, the variables LEFTONLY_TOP and LEFTONLY_BOTTOM correspond to region templates that provide a logobar, menubar, leftside menu, and copyright footer. Content, consisting of HTML and ITL, is placed within the BEGIN and END CONTENT comments. The following illustration shows how this looks on the page:
+--------------------------------------------------------+⎪ LOGOBAR ⎪⎪--------------------------------------------------------+⎪ MENUBAR ⎪⎪--------------+-----------------------------------------+⎪ ⎪ ⎪⎪ ⎪ ⎪⎪ ⎪ ⎪⎪ LEFTSIDE ⎪ This is your content ⎪⎪ ⎪ ⎪⎪ ⎪ ⎪⎪ ⎪ ⎪⎪ +-----------------------------------------⎪⎪ ⎪ COPYRIGHT ⎪+--------------------------------------------------------+
In this diagram, LEFTONLY_TOP contributes the LEFTSIDE, LOGOBAR, and MENUBAR sections, while LEFTONLY_BOTTOM contributes the COPYRIGHT section. The following subsections provide an inventory of where each of the region templates, included with the Foundation demo, are used in the pages and template definition files that make up the catalog. LEFTONLY_TOP The LEFTONLY_TOP template region is used in the following template pages:
pages/aboutus.htmlpages/account.htmlpages/affiliate/index.htmlpages/affiliate/login.htmlpages/canceled.htmlpages/contact.htmlpages/customerservice.htmlpages/flypage.htmlpages/help.htmlpages/login.htmlpages/logout.htmlpages/modular_modify.htmlpages/new_account.htmlpages/ord/basket.htmlpages/privacypolicy.htmlpages/process_return.htmlpages/quantity.htmlpages/query/check_orders.htmlpages/query/order_detail.htmlpages/query/order_return.htmlpages/returns.htmlpages/saved_carts.htmlpages/ship_addresses.htmlpages/ship_addresses_added.htmlpages/ship_addresses_removed.htmlpages/stock-alert-added.htmlpages/stock-alert.html
The LEFTONLY_TOP template region is used in the following templates:
templates/foundation/carttemplates/foundation/leftonlytemplates/foundation/simple
Region Template Walkthrough -- LEFTONLY_TOP
1 <!-- BEGIN LEFTONLY_TOP -->2 [if scratch members_only]3 [set members_only][/set]4 [if !session logged_in]5 [set mv_successpage]@@MV_PAGE@@[/set]6 [bounce page=login]7 [/if]8 [/if]910 <html>11 <head>12 <title>[scratch page_title]</title>13 __THEME_CSS__14 </head>1516 <body marginheight="0" marginwidth="0">1718 <!--- top left and right logo --->19 <table width="100%" border="0" cellspacing="0" cellpadding="0">20 <tr>21 <td align="left" valign="middle" class="maincontent">22 <img src="__THEME_IMG_DIR____LOGO__">23 </td>24 <td align="right" valign="middle" class="maincontent">25 <img width="174" height="60" src="__THEME_IMG_DIR__logo2.gif"> 26 </td>27 </tr>28 </table>2930 <!--- menu bar along the top --->31 <table width="100%" border="0" cellspacing="0" cellpadding="0">32 <tr>33 <td width="100%" class="menubar">34 <a href="[area index]"><img name="Home" border="0" src="__THEME_IMG_DIR__home.gif"></a>35 <img src="__THEME_IMG_DIR__sep.gif">36 <a href="[area login]">37 [if session logged_in]38 <img alt="Log Out" border="0" src="__THEME_IMG_DIR__logout.gif"></a>39 [else]40 <img alt="Log In" border="0" src="__THEME_IMG_DIR__login.gif"></a>41 [/else]42 [/if]43 <img src="__THEME_IMG_DIR__sep.gif">44 <a href="[area ord/basket]"><img alt="Your Cart" border="0" src="__THEME_IMG_DIR__cart.gif"></a>45 <img src="__THEME_IMG_DIR__sep.gif">46 <a href="[area ord/checkout]"><img alt="Check Out" border="0" src="__THEME_IMG_DIR__checkout.gif"></a>47 <img src="__THEME_IMG_DIR__sep.gif">48 <a href="[area customerservice]"><img alt="Customer Service" border="0" src="__THEME_IMG_DIR__service.gif"></a>49 <img src="__THEME_IMG_DIR__sep.gif">50 <a href="[area aboutus]"><img alt="About Us" border="0" src="__THEME_IMG_DIR__about.gif"></a>51 </td>52 </tr>53 </table>5455 <!--- left category column, main content column, and right special column --->56 <table width="100%" border="0" cellspacing="0" cellpadding="0">57 <tr>58 <td width="20%" valign="top" align="left" class="categorybar">59 <!--Left Sidebar-->60 <table width="100%" border="0" cellspacing="0" cellpadding="0">61 [include file="templates/components/[control component none]"][control]62 [include file="templates/components/[control component none]"][control]63 [include file="templates/components/[control component none]"][control]64 </table>65 </td>66 <td width="80%" valign="top" align="center" class="maincontent">67 [include file="templates/components/[control component none]"][control]68
LEFTONLY_BOTTOM The LEFTONLY_BOTTOM template region is used in the following template pages:
pages/aboutus.htmlpages/account.htmlpages/affiliate/index.htmlpages/affiliate/login.htmlpages/canceled.htmlpages/contact.htmlpages/customerservice.htmlpages/flypage.htmlpages/help.htmlpages/login.htmlpages/logout.htmlpages/modular_modify.htmlpages/new_account.htmlpages/ord/basket.htmlpages/privacypolicy.htmlpages/process_return.htmlpages/quantity.htmlpages/query/check_orders.htmlpages/query/order_detail.htmlpages/query/order_return.htmlpages/returns.htmlpages/saved_carts.htmlpages/ship_addresses.htmlpages/ship_addresses_added.htmlpages/ship_addresses_removed.htmlpages/stock-alert-added.htmlpages/stock-alert.html
The LEFTONLY_BOTTOM template region is used in the following templates:
templates/foundation/carttemplates/foundation/leftonlytemplates/foundation/simple
LEFTRIGHT_TOP The LEFTRIGHT_TOP template region is used in the following template pages:
pages/browse.htmlpages/index.htmlpages/results.htmlpages/results_big.htmlpages/swap_results.html
The LEFTRIGHT_TOP template region is used in the following templates:
templates/foundation/leftright
LEFTRIGHT_BOTTOM The LEFTRIGHT_BOTTOM template region is used in the following template pages:
pages/browse.htmlpages/index.htmlpages/results.htmlpages/results_big.htmlpages/swap_results.html
The LEFTRIGHT_BOTTOM template region is used in the following templates:
templates/foundation/leftright
NOLEFT_BOTTOM The NOLEFT_BOTTOM template region is used in the following template pages:
pages/ord/checkout.htmlpages/splash.html
The NOLEFT_BOTTOM template region is used in the following templates:
templates/foundation/fullwidth
NOLEFT_TOP The NOLEFT_TOP template region is used in the following template pages:
pages/ord/checkout.htmlpages/splash.html
The NOLEFT_TOP template region is used in the following templates:
templates/foundation/fullwidth
Template Page List /home/ic/catalogs/ft/pages/:
aboutus.htmlaccount.htmlbrowse.htmlcanceled.htmlchange_password.htmlcontact.htmlcustomerservice.htmldeliver.htmlflypage.htmlhelp.htmlindex.htmllogin.htmllogout.htmllost_password.htmlmodular_modify.htmlnew_account.htmlprivacypolicy.htmlprocess_return.htmlquantity.htmlresults_big.htmlresults_either.htmlresults.htmlreturns.htmlsaved_carts.htmlship_addresses_added.htmlship_addresses.htmlship_addresses_removed.htmlsplash.htmlstock-alert-added.htmlstock-alert.htmlswap_results.html
/home/ic/catalogs/ft/pages/admin/report_def:
Order%20Status.htmlProducts%20to%20edit.html
/home/ic/catalogs/ft/pages/admin/reports:
Order%20Status.htmlProducts%20to%20edit.html
/home/ic/catalogs/ft/pages/affiliate:
index.htmllogin.html
/home/ic/catalogs/ft/pages/ord:
basket.htmlcheckout.html
/home/ic/catalogs/ft/pages/query:
check_orders.htmlget_password.htmlorder_detail.htmlorder_return.html
Special Page List /home/ic/catalogs/ft/special_pages/:
badsearch.htmlcanceled.htmlcc_not_valid.htmlconfirmation.htmlfailed.htmlinteract.htmlmissing.htmlneedfield.htmlnomatch.htmlnoproduct.htmlnotfound.htmlorder_security.htmlreconfig.htmlsec_faq.htmlsecurity.htmlviolation.html
Components Added new [control] and [control-set] tags to set series of Scratch- like option areas. Used for components in UI content editing. Interchange components are portions of HTML and ITL that are included in pages within a catalog depending on options set in the Administration Tool. The default component set includes the following:
affiliate_receptorbest_horizontalbest_verticalcartcart_displaycart_tinycategory_verticalcross_horizontalcross_verticalmodular_buymodular_updatenonepromopromo_horizontalpromo_verticalrandomrandom_horizontalrandom_verticalsaved_carts_list_smallsearch_box_smallupsellupsell_horizontalupsell_vertical
/home/ic/catalogs/ft/templates/components: affiliate_receptor Not used in Foundation demo best_horizontal The best_horizontal component is used in the following templates:
templates/foundation/carttemplates/foundation/leftonlytemplates/foundation/leftright
Not used in Foundation demo pages best_vertical The best_vertical component is used in the following template:
templates/foundation/leftright
Not used in Foundation demo pages cart The cart component is used in the following page:
pages/ord/basket.html
cart_display The cart_display component creates a small shopping cart that is displayed on the search results page (pages/results.html). It is displayed after an item in a list of results from a search is added to the shopping cart. cart_display is called in results.html by the following include statement:
[include file="templates/components/cart_display"]
The cart_display component is used in the following pages:
pages/results.html
Component Walkthrough -- cart_display The remainder of this section is best read in conjunction with the file CATROOT/templates/components/cart_display in a text editor. Lines 1-6: Component Specification
1 [comment]2 ui_component: cart_display3 ui_component_group: info4 ui_component_label: Smaller cart for display in content area56 [/comment]7
These lines control what is shown in the Edit page screen of the admin interface.
8 <!-- BEGIN COMPONENT [control component cart_display] -->
Line 8 is an HTML comment noting the start of the code for the component. (Note that this can serve as a useful debugging tool to help you locate the component in the resulting HTML generated by Interchange when you view the source of a page loaded in the browser.)
9 [if items]
Line 9 checks to see if there are items in the shopping basket. If there are, the remaining code up to the closing [/if] tag on line 64 is executed. If not, Interchanges continues executing the remaining code in results.html (the file that calls the cart_display component).
10 <center>11 <table width="95%" border="0" cellspacing="0" cellpadding="0">12 <TR class="contentbar2" VALIGN=TOP>13 <td align=center class="contentbar2">Action</td>14 <td class="contentbar2">15 SKU16 </td>17 <td class="contentbar2">18 Description19 </td>20 <td class="contentbar2">21 Quantity22 </td>23 <td class="contentbar2">24 Price25 </td>26 <td class="contentbar2">27 Extension28 </td>29 </TR>
Line 10 centers the table started in line 11. Lines 12-29 create a header row in the shopping cart consisting of the header titles Action, SKU, Description, Quantity, Price, and Extension.
30 <TBODY>31 [item-list]32
Line 30 defines the remainder of the table as a section while the [item-list] tag on line 31 tells Interchange to execute the code up to the closing tag ([/item-list] on line 59 for each item the customer has ordered so far.
33 <tr class="[item-alternate 2]maincontent[else]contentbar1[/else][/item-alternate]">34 <td align=center valign=top>35 [page ord/basket]edit</A>36 </TD>37 <td valign=top>[item-code]</TD>38 <td valign=top>[page [item-code]][item-description]</A>39 </TD>40
Line 33 begins the next row in the table. The [item-alternate] tag provided as the value of the class attribute tells Interchange to alternate between displaying the rows according to the "maincontent" and "contentbar1" styles (gray and white, respectively). Lines 34-36 create a link to the shopping cart (basket.html) where the customer can remove or change the quantity of the item ordered. Line 37 displays the SKU of the item. Lines 38 and 39 provide a link to the product display page (flypage.html) for the item. The [item-description] tag providing the content of the [page] tag enables the item's name to be displayed as the link to the product display page.
41 [if-item-modifier gift_cert]42 <TD ALIGN=CENTER><small>Amount of gift:</small></TD>43 <TD ALIGN=CENTER>[item-quantity]</TD>44 <TD ALIGN=right>45 [item-subtotal]46 </TD>47 [else]48 <TD ALIGN=CENTER>[item-quantity]</TD>49 <TD ALIGN=right>50 [item-price]51 </TD>52 <TD ALIGN=right>53 [item-subtotal]54 </TD>55 [/else]56 [/if-item-modifier]57 </TR>58
Line 41 checks whether the item is a gift certificate. If it is it displays "Amount of gift:" and the [item-quantity] (number of gift certificates, in this case) under the headings "Quantity" and "Price", respectively. Otherwise, lines 48 through 50 display the quantity and price of the item ordered. Lines 45 or 53 (depending on whether the item is a gift certificate) display the item subtotal (quantity multiplied by price) for the item under the heading "Extension".
59 [/item-list]60 </TBODY>61 </table>62 </FORM>63 </center>64 [/if]6566 <!-- END COMPONENT [control component cart_display] -->
Lines 59 through 64 close out the tags for the component, and line 66 indicates the end of the component code. cart_tiny The cart_tiny component is used in the following pages:
pages/account.htmlpages/browse.htmlpages/canceled.htmlpages/customerservice.htmlpages/flypage.htmlpages/help.htmlpages/index.htmlpages/logout.htmlpages/modular_modify.htmlpages/new_account.htmlpages/privacypolicy.htmlpages/process_return.htmlpages/quantity.htmlpages/query/check_orders.htmlpages/query/order_detail.htmlpages/query/order_return.htmlpages/saved_carts.htmlpages/ship_addresses.html
category_horizontal Not used in Foundation demo pages or templates. category_vertical The category_vertical component provides a listing of all products in the catalog, organized by prod_group (e.g., Hand Tools, Ladders). category_vertical is usually displayed in the LEFTSIDE section of the page, under the search_box_small component. The category_vertical component is used in the following pages:
pages/aboutus.htmlpages/account.htmlpages/affiliate/index.htmlpages/affiliate/login.htmlpages/browse.htmlpages/canceled.htmlpages/contact.htmlpages/customerservice.htmlpages/flypage.htmlpages/help.htmlpages/index.htmlpages/login.htmlpages/logout.htmlpages/modular_modify.htmlpages/new_account.htmlpages/ord/basket.htmlpages/privacypolicy.htmlpages/process_return.htmlpages/quantity.htmlpages/query/check_orders.htmlpages/query/order_detail.htmlpages/query/order_return.htmlpages/results.htmlpages/results_big.htmlpages/returns.htmlpages/saved_carts.htmlpages/ship_addresses.htmlpages/stock-alert-added.htmlpages/stock-alert.htmlpages/swap_results.html
Component Walkthrough -- category_vertical The remainder of this section is best read while viewing the file CATROOT/templates/components/cart_display in a text editor. Lines 1-6: Component Specification
1 [comment]2 ui_component: category_vertical3 ui_component_group: Navigation4 ui_component_label: Vertical category list56 page_class:7 label: Page class8 widget: select9 lookup: which_page10 db: area11 help: Defines which sets of items should be displayed12 advanced: 11314 set_selector:15 label: Page area selector16 widget: select17 db: area18 lookup: sel19 help: Defines which sets of items should be displayed20 advanced: 121 [/comment]22
These lines control what is shown in the Edit page screen of the Administration Tool.
23 <tr><td align="center" class="categorybar">24 <br>25 <table>2627 <!-- BEGIN COMPONENT [control component category_vertical] -->
Lines 23-25 set up the row and table within that row that will hold the vertical category list. Line 27 identifies the start of the code for the list.
28 [loop29 prefix=box30 search="31 fi=area32 st=db33 tf=sort34 ac=035 ac=036 co=yes3738 sf=sel39 op=eq40 se=[control set_selector left]4142 sf=which_page43 op=rm44 se=[control page_class all⎪@@MV_PAGE@@]45 "]46
Lines 28-45 build a list of product categories obtained through a search of the area table.
47 <tr>48 <td valign="top" class="categorybar">49 <b>[box-exec bar_link]area[/box-exec]</b>50 </td>51 </tr>52 <tr>53 <td valign="top" class="categorybar">5455 [set found_cat][/set]56 [loop prefix=cat57 search="58 fi=cat59 st=db60 tf=sort61 tf=name62 rf=code,name63 sf=sel64 se=[box-code]65 "66 ]67 [cat-exec bar_link]cat[/cat-exec]<BR>68 [/loop]6970 </td>71 </tr>72 [/loop]7374 </table>75 <br>76 </td></tr>7778 <!-- END COMPONENT [control component category_vertical] -->
Lines 47-78 generate a list of links based on the products and product categories identified in the search. cross_horizontal The cross_horizontal component is used in the following pages:
pages/browse.htmlpages/index.htmlpages/results.htmlpages/results_big.html
The cross_horizontal component is used in the following templates:
templates/foundation/carttemplates/foundation/leftonlytemplates/foundation/leftright
cross_vertical Not used in Foundation demo pages. The cross_horizontal component is used in the following templates:
templates/foundation/leftright
modular_buy The modular_buy component is used in the following pages:
pages/flypage.html
The modular_buy component is used in the following templates:
templates/components/modular_update
modular_update The modular_update component is used in the following pages:
pages/modular_modify.html
promo The promo component is used in the following pages:
pages/contact.htmlpages/results_big.html
promo_horizontal The promo_horizontal component is used in the following pages:
pages/aboutus.htmlpages/canceled.html
The promo_horizontal component is used in the following templates:
templates/foundation/carttemplates/foundation/leftonlytemplates/foundation/leftright
promo_vertical Not used in Foundation demo pages. The promo_horizontal component is used in the following templates:
templates/foundation/leftright
random The random component is used in the following pages:
pages/browse.htmlpages/index.htmlpages/ord/basket.htmlpages/privacypolicy.htmlpages/process_return.htmlpages/results.htmlpages/swap_results.html
random_horizontal Not used in Foundation demo pages. The random_horizontal component is used in the following templates:
templates/foundation/carttemplates/foundation/leftonlytemplates/foundation/leftright
random_vertical Not used in Foundation demo pages. The random_vertical component is used in the following templates:
templates/foundation/leftright
saved_carts_list_small The saved_carts_list_small component is used in the following pages:
pages/ord/basket.html
search_box_small The search_box_small component is used in the following pages:
pages/aboutus.htmlpages/account.htmlpages/affiliate/index.htmlpages/affiliate/login.htmlpages/browse.htmlpages/canceled.htmlpages/contact.htmlpages/customerservice.htmlpages/flypage.htmlpages/help.htmlpages/index.htmlpages/login.htmlpages/logout.htmlpages/modular_modify.htmlpages/new_account.htmlpages/ord/basket.htmlpages/privacypolicy.htmlpages/process_return.htmlpages/quantity.htmlpages/query/check_orders.htmlpages/query/order_detail.htmlpages/query/order_return.htmlpages/results.htmlpages/results_big.htmlpages/returns.htmlpages/saved_carts.htmlpages/ship_addresses.htmlpages/stock-alert-added.htmlpages/stock-alert.htmlpages/swap_results.html
The search_box_small component is used in the following templates:
templates/regions/LEFTONLY_TOPtemplates/regions/LEFTRIGHT_TOP
upsell Not used in Foundation demo pages. upsell_horizontal The upsell_horizontal component is used in the following pages:
pages/flypage.html
The upsell_horizontal component is used in the following templates:
templates/foundation/carttemplates/foundation/leftonlytemplates/foundation/leftright
upsell_vertical Not used in Foundation demo pages. The upsell_vertical component is used in the following templates:
templates/foundation/leftright
Interchange catalogs are centralized around the database. You can alter any of the standard databases, add new databases, or remove unneeded databases The foundation catalog includes the following tables, organized here by content: Your site content data area.txt
cat.txt
downloadable.txt
merchandising.txt
options.txt
pricing.txt
products.txt
products.txt.category
Customer data access.asc
gift_certs.txt
userdb.txt
Transaction-related data inventory.txt
orderline.txt
order_returns.txt
transactions.txt
Third-party relationship data affiliate.txt
banner.txt
Site administrative data component.txt
files.txt
ichelp.txt
icmenu.txt
locale.txt
mv_metadata
route.txt
shipping.asc
variable.txt
Ancillary data 2ndDayAir.csv
450.csv
country.txt
Ground.csv
NextDayAir.csv
salestax.asc
state.txt The following dictionary lists and describes each table used in the Foundation demo.
2ndDayAir.csv Shipping table from UPS (http://www.ups.com/using/services/rave/rate/). This and all shipping tables should be updated periodically.
450.csv Shipping table from UPS for 450xx Zip Code origin. You will probably need to get your own from the UPS site (http://www.ups.com/using/services/rave/rate/) and clip the headers.
Ground.csv Shipping table from UPS (http://www.ups.com/using/services/rave/rate/).
NextDayAir.csv Shipping table from UPS (http://www.ups.com/using/services/rave/rate/).
access.asc Administrative access table. This table is used by the Administration Tool. For more description on these fields, see the Red Hat Interchange Administration Tool guide. Fields
Field Descriptionusername Login name or group name (group names begin with ':')password Hashed passwordname Administrator's namelast_login Last login timesuper Set to 1 if superuseryes_tables Tables the user may editno_tables Tables the user may not editupload No Descriptionacl No Descriptionexport No Descriptionedit No Descriptionpages No Descriptionfiles No Descriptionconfig No Descriptionreconfig No Descriptiongroups Administrator's group membershipsmeta No Descriptionno_functions Explicitly disallowed functionsyes_functions Allowed functions with permission flagstable_control No Descriptionpersonal_css Administrator's personal CSS (for admin screen presentation)
username Example Data
:ausers:busersBigUsergoodyic
The login name for an administrator or an administration group. Group names are prefixed with a colon (':'). password Example Data
Ksjs65bMNLjPQ
Hashed password. name Example Data
Interchange Site AdministratorInterchange Site AssociatesBusiness Users2nd ShiftMr. JonesInbound Sales
Descriptive name for the administrator or administration group. last_login Example Data
989424489
Last login time (in unix time() format). super Boolean value. If true (1), the administrator has Interchange Site Administrator privilege. yes_tables Example Data
affiliate=vcx component=v gift_certs=v inventory=vx ...NONE
Tables this administrator or administration group can access. This is a space-delimited list of 'table_name=permission_flags' entries. no_tables Example Data
access mv_metadata variable
Tables this administrator or administration group can not use. This is a space-delimited list of tables names. upload No Description acl No Description export No Description edit No Description pages No Description files No Description config No Description Example Data Allowed Values reconfig No Description groups Example Data
ausersbusers
Allowed Values Groups the site user belongs to. You can set permissions for groups. meta No Description no_functions Example Data
orderstats trafficstats
Space-delimited list of functions explicitly not allowed for the site user. yes_functions Example Data
item=lvecd itemtype=lvc order=lvca orderstats trafficstats ...NONE
Functions the site user can perform. This is a space-delimited list of functions, with permission flags if appropriate. Usage examples dist/lib/UI/pages/admin/access_permissions.html table_control No Description Usage examples dist/lib/UI/Primitive.pm dist/lib/UI/pages/admin/special/key_violation.html dist/lib/UI/usertag/if_mm personal_css Used in the Administration Tool screens to make personal changes to the page presentation. This is done by creating your own personal CSS (cascading style sheet). Usage examples dist/lib/UI/pages/admin/preferences.html
affiliate cat_root/products/affiliate.txt This table contains data related to your affiliate programs. See also the affiliate_receptor component. Fields
Field Descriptionaffiliate Affiliate IDname Name of affiliate organizationcampaigns Campaigns this affiliate participates incoupon_amount Discount for customers from affiliate participating in coupon campaignjoin_date When the affiliate signed with youurl Your default URL to use for customers coming from the affiliate site (not the affiliate's home page)timeout Timeout in seconds after which purchases are no longer credited to the affiliateactive Boolean, set to 1 for active affiliatespassword Affiliate login passwordimage Affiliate's logo
affiliate Example Data
consolidatedhardhat
This field contains the unique Affiliate ID. name Example Data
Consolidated DiversifiedHardhat Construction
This is the descriptive name of the affiliate. campaigns Example Data
coupon
This field lists the campaigns that the affiliate participates and enables campaign features and tracks traffic from advertising campaigns. The foundation catalog implements a coupon campaign in the affiliate_receptor component. If you want to add campaigns, you will also need to develop the appropriate logic within the affiliate_receptor component and pages that use it. coupon_amount Example Data
5
This is the discount offered customers from the affiliate participating in the coupon campaign. Note -- This is implemented in the affiliate_receptor component as a flat discount amount. If you wanted a percentage discount instead, you would modify the [discount] tag in catalog_root/templates/components/affiliate_receptor (see the [discount] tag for more detail). join_date Example Data
2000082720000910
This is the date when the affiliate signed with you. url Example Data
http://demo.akopia.com/~hardhathttp://www.minivend.com/consolidated/
The value in this field is used to direct visitors coming from the Affiliate to your home page or a page you have designed specifically for visitors from that Affiliate's site. Note that this should not be the URL of the Affiliate's home site. timeout Example Data
03600
The value in this field is used to specify the amount of time a customer has to place an order to still give the Affiliate credit for it. If the customer goes over this amount of time, the Affiliate doesn't get credit for the customer visit. The timeout delay is measured in seconds, with the value of 0 (zero) disabling it. It is recommended that you use a value in the thousands to make sure the customer has enough time to shop. active This is a boolean value indicating whether the affiliate is active. password Example Data
akopia
Password for affiliate login (see catalog_root//pages/affiliate/login.html). Note that the password is stored in plaintext by default. image Example Data
http://demo.akopia.com/~hardhat/images/logo.gifhttp://www.minivend.com/consolidated/conslogo.gif
Affiliate's logo image.
area cat_root/products/area.txt This table is used to implement dynamic navigation bars. For example, it is used in the category_horizontal and category_vertical components. Note the similarity to the cat table, since both area and cat tables supply data for building links to results pages. When building entries in a navigation bar, it is the bar_link subroutine in the /dist/catalog_before.cfg configuration file that actually reads and processes the values from the table. See also the following catalog and administrative templates: cat_root/templates/components/category_horizontal cat_root/templates/components/category_vertical dist/lib/UI/pages/admin/layout.html dist/lib/UI/pages/admin/layout_auto.html dist/lib/UI/pages/admin/wizard/do_launch.html dist/lib/UI/pages/admin/wizard/do_save.html Fields
Field Descriptioncode Unique keysel Space-delimited list of navigation bars to contain the entryname Display labelwhich_page Page class in which the navigation bar may appearsort Sorting prefix for entry (preempts standard alphanumeric sort)display_type How to label links in the navbar (name, icon, url or image)image Image URL (if appropriate)image_prop HTML attributes for output <img> tag (if appropriate)banner_image Image name for use in target pagebanner_text Text for use in target pagelink_type Type of links in the navbar (external, internal, simple, complex)url Target for internal or external link_typeDatabase table file to use with 'simple' link_typepage Results page to use with 'simple' link_typesearch Search spec used with 'complex' link_typeselector The selector used to scan the products table for products in the categorylink_template Overrides template used for building navbar links.
code Example Data
123
Unique key. sel Example Data
left
Space-delimited list of navigation bars that should contain the entry. Note that comma or null should also work as a delimiter. name Example Data
Hand ToolsHardwareLaddersMeasuring ToolsPainting SuppliesSafety EquipmentSpecialsTool Storage
Label to display. which_page Example Data
all
Page class in which the navigation bar may appear. sort Example Data
0003040506
Lexographic (alphanumeric) sorting prefix. Note use of '03' rather than '3', which would sort after '13'. This controls the order of the categories in your navigation bar. If this is not set, your navbar entries will sort in alphabetical order. display_type Example Data
nameiconurlimage
What to use for the labels in the navigation bar (for example, name, icon, url or image). The navigation bars in the foundation catalog are set up with 'name' display_type.
display type Link shown asname Displays name onlyicon Displays name and specified imageimage Displays image onlyurl Displays link
image Image URL for image or icon display_type. image_prop For image or icon display_type, this contains the HTML attributes for the HTML that will appear in the navbar, for example:
<img src="image" alt="name" image_prop>name
banner_image Example Data
promo_image.gif
This field is not related to banner ads. It is useful if you want to pass to your results page an image that is specific for the navbar entry (perhaps to display a banner above your results). If you are using an Interchange search for your links (i.e., 'simple' or 'complex' link_type), then this will add 'va=banner_image=banner_image' to the resulting search specification. This puts the contents of banner_image into the Values hash of your search results page. You can access it with [value banner_image] (see the value tag). You will have to modify the standard results page (or set up and specify your own) in order to display the image.
<IMG src="[value banner_image]" alt="[value banner_text]">
The foundation catalog does not implement banner_image in the preconfigured navigation bars. banner_text Example Data
This Is A Title For Hand Tools
This field is not related to banner ads. It is useful if you want to pass to your results page some text that is specific for the navbar entry (perhaps to display a title above your results). If you are using an Interchange search for your links (i.e., 'simple' or 'complex' link_type), then this will add 'va=banner_text=banner_text' to the resulting search specification. This puts the contents of banner_text into the Values hash of your search results page. You can access it with [value banner_text] (see the value tag). You will have to modify the standard results page (or set up and specify your own) in order to display the text. The foundation catalog does not implement banner_text in the preconfigured navigation bars. link_type Example Data
noneexternalinternalsimplecomplex
Link type to create in the navigation bar.
Link type Descriptionnone No linkexternal External link. The HTML specified in url will go directly into the navigation bar.internal Internal link. This will be highlit if it is the current page. If you specify both a page and a form for the link, the url field should contain "page form". See the Search Engine documentation for more detail on search forms.simple Allows you to specify an Interchange search with a few values. See the bar_link subroutine in the /dist/catalog_before.cfg configuration file for more detail.complex Allows you to fully specify an Interchange search specification. See the bar_link subroutine in the /dist/catalog_before.cfg configuration file for more detail if you need to use these.
url Target URL (external link or internal page/search specification). See link_type . The foundation catalog navigation bars are not set up with link types that use the url field. tab Database table file to use with 'simple' link_type (searchspec fi=tab). The foundation catalog navigation bars are not set up with link types that use the tab field. page Results page to use with 'simple' link_type (searchspec sp=page). The foundation catalog navigation bars are not set up with link types that use the page field. search Search spec used with 'complex' link_type. See the Search Engine documentation for more detail on search forms. The foundation catalog navigation bars are not set up with link types that use the search field. selector The selector that is used to scan the products table for products in the category. Used with 'simple' link_type. The foundation catalog navigation bars are not set up with link types that use the selector field. link_template Overrides the usual HTML link template for navbar entries. See the bar_link subroutine in the /dist/catalog_before.cfg configuration file if you need to modify link templates. The foundation catalog navigation bars are not set up with link types that use the link_template field.
banner cat_root/products/banner.txt The banner ad table. The foundation catalog does not implement any banner ads with this table. You do not need to use this table to display ads served by third parties (for example, doubleclick). Since most banner ads on the internet are served by third parties and are not managed by your catalog, you probably will not need to set up banners here unless you do your own advertising. See Banner/Ad rotation in the template documentation for a detailed description of the columns and content of the banner table. Also, see the banner tag documentation. Fields
Field Descriptioncode Key for the item. If the banners are not weighted, this should be a category-specific code.category Category for set of weighted bannersweight Display frequency weight for weighted bannerrotate Boolean: parse banner field for banners to rotate if true (1)banner Banner name or list of banners to rotate
code Example Data
MyBannerMyBanner2MyBanner3default
See Banner/Ad rotation. category Example Data
BannerCat1
See Banner/Ad rotation. weight Example Data
127
See Banner/Ad rotation. rotate Boolean value. If true (1), rotates banners listed in banner. See Banner/Ad rotation. banner Example Data
Default banner 1{or}Default banner 2{or}Default banner 3First MyBannerSecond MyBannerThird MyBanner
See Banner/Ad rotation.
cat cat_root/products/cat.txt This table contains properties of product categories. Notice the similarity to the area table, since both the area and cat tables supply data for building links to results pages. Fields
Field Descriptioncode Unique keysel Space-delimited list of foreign keys into area tablename Category namewhich_page Page class in which the category may appearsort Sorting prefix for entry (preempts standard alphanumeric sort)display_type How to label the category links (name, icon, url or image)image Image URL (if appropriate)image_prop HTML attributes for output <img> tag (if appropriate)banner_image Image name for use in target pagebanner_text Text for use in target pagelink_type Type of links in the navbar (external, internal, simple, complex)url Target for internal or external link_typeDatabase table file to use with 'simple' link_typepage Results page to use with 'simple' link_typesearch Search spec used with 'complex' link_typeselector The selector used to scan the products table for products in the categorylink_template Overrides template used for building links
code Example Data
145
Unique key. sel Example Data
68 99
Space-delimited list of foreign key(s) into area table. The category will appear in each navbar section (defined by a row in the area table) where the key from cat.sel matches the area.code. For example, the foundation catalog (tools) places Gift Certificates in more than one category of the left navbar. name Example Data
Breathing ProtectionEye ProtectionGift CertificatePicks & HatchetsPliersRulersSandpaperToolboxes
Category name for display. which_page The page class. When building links, you can select categories matching a page class. This means you could set up your catalog to show a different list of links on page 'foo.html' than on page 'bar.html'. sort Example Data
0103
Lexographic (alphanumeric) sorting prefix. Notice use of '03' rather than '3', which would sort after '13'. You can use this to control the order of the categories in a list of links. display_type Example Data
nameiconurlimage
What to use for the labels in the navigation bar (for example, name, icon, url or image). The links in the foundation catalog are set up with 'name' display_type.
display type Link shown asname Displays name onlyicon Displays name and specified imageimage Displays image onlyurl Displays link
image Image URL for image or icon display_type. image_prop For image or icon display_type, this contains the HTML <img ...> tag attributes for the links, for example:
<img src="image" alt="name" image_prop>name
banner_image Example Data
promo_image.gif
This field is not related to banner ads. It is useful if you want to pass to your results page an image that is specific for the navbar entry (perhaps to display a banner above your results). If you are using an Interchange search for your links (i.e., 'simple' or 'complex' link_type), then this will add 'va=banner_image=banner_image' to the resulting search specification. This puts the contents of banner_image into the Values hash in your search results page. You can access it with [value banner_image] (see the value tag). You will have to modify the standard results page (or set up and specify your own) in order to display the image. For example, you might include the following in your results page:
<IMG src="[value banner_image]" alt="[value banner_text]">
banner_text This field is not related to banner ads. It is useful if you want to pass to your results page some text that is specific for the navbar entry (perhaps to display a title above your results). If you are using an Interchange search for your links (i.e., 'simple' or 'complex' link_type), then this will add 'va=banner_text=banner_text' to the resulting search specification. This puts the contents of banner_text into the Values hash in your search results page. You can access it with [value banner_text] (see the value tag). You will have to modify the standard results page (or set up and specify your own) in order to display the text. link_type Example Data
noneexternalinternalsimplecomplex
The link type to create.
Link type Descriptionnone No linkexternal External link. The HTML specified in url will go directly into the link.internal Internal link. This will be highlit if it is the current page. If you specify both a page and a form for the link, the url field should contain "page form". See the Search Engine documentation for more detail on search forms.simple Allows you to specify an Interchange search with a few values. See the bar_link subroutine in the /dist/catalog_before.cfg configuration file for more detail.complex Allows you to fully specify an Interchange search specification. See the bar_link subroutine in the /dist/catalog_before.cfg configuration file for more detail if you need to use these.
url Target URL (external link or internal page/search specification). See link_types above. tab Example Data
products
Database table file to use with 'simple' link_type (searchspec fi=tab). page Example Data
swap_results
Results page to use with 'simple' link_type (searchspec sp=page). search Example Data
fi=merchandising^Msf=featured^Mse=newfi=merchandising^Msf=featured^Mse=special^Msu=yes
Search spec used with 'complex' link_type. See the Search Engine documentation for more detail on search forms. Note: The '^M' delimiters in the sample data represents a carriage return character (Control-M, or hexadecimal 0x0d). selector Example Data
category=Breathing Protectioncategory=Eye Protectioncategory=Gift Certificatecategory=Picks & Hatchetscategory=Plierscategory=Rulerscategory=Sandpapercategory=Toolboxes
The element that is used to scan the products table for products in the category. Used with 'simple' link_type. link_template Overrides the usual HTML link template for navbar entries. See the bar_link subroutine in the /dist/catalog_before.cfg configuration file if you need to modify link templates.
country A list of countries used to build select boxes and shipping mode choices based on countries.
codesorderregionselectorshipmodesname
downloadable This table controls downloadable products. The Marketing Reports data set for the foundation catalog demonstrates downloadable products. List a product's sku in this table if you want to deliver it through a download. A customer can then download the file specified in the dl_location field after checkout. For reference, see the implementation in the following files: catalog_root/pages/deliver.html catalog_root/etc/receipt.html catalog_root/pages/query/order_detail.html Fields
Field Descriptionsku Unique key, matches product.skudl_location Location of downloadable filedl_type MIME type of downloadable file
sku Example Data Example Data from the Marketing Reports data set:
00352as22083da49503cg59330rt59402fw73358ee83491vp90773sh
This is the unique key for this table that is also the common key into the products table. dl_location Example Data from 'reports' catalog
download/00352as.pdfdownload/22083da.pdfdownload/49503cg.pdfdownload/59330rt.pdfdownload/59402fw.pdfdownload/73358ee.pdfdownload/83491vp.pdfdownload/90773sh.pdf
File location of downloadable product. dl_type Example Data from 'reports' catalog
application/pdf
MIME type of downloadable content.
files.txt A database where files (pages, etc.) can be kept instead of in the Unix filesystem.
gift_certs.txt
codeusernameorder_dateoriginal_amountredeemed_amountavailable_amountpasscodeactiveredeemedupdate_date
inventory.txt
skuQuantity infoquantityGets decremented after each sale.stock_messageThe usual shipping time of the product.Out of stock message:In stockShips in 3-5 daysShips in 4-6 weeksSpecial orderaccountAccounting infoSales accountcogs_account
locale.txt
codeen_USde_DEfr_FR
merchandising.txt
skufeaturedbanner_textbanner_imageblurb_beginblurb_endCloser (end text for feature display)timed_promotionstart_dateStart datefinish_dateupsell_toCross-sell SKUscross_sellcross_categoryothers_boughttimes_ordered
mv_metadata See the following sections in the icadvanced catalog for more information: display tag and mv_metadata mv_metadata.asc
options This table contains data for implementing simple, matrix and modular options. Simple options are options that a customer can combine arbitrarily, such as size and color. The selected options might affect price. See the accessories tag for more detail on option values for simple options. Matrix options are preconfigured combinations of options. For example, if you sell titanium and carbon-fiber bike frames, but offer only certain combinations of frame material and color, your checkout page might include a select box with only the following entries: Silver Titanium: $1672 Black Titanium: $1672 Red Titanium: $1674 Black Carbon Fiber: $1290 Yellow Flame Carbon Fiber: $1300 Note that there is no Yellow Flame Titanium offering, for example. Modular options are like a structured bill of materials, where one product is a master item and other products are subitems for that master item. The subitems can also be master items to subitems at a lower level. In addition, subitems may be designated as 'phantom', which means that they are placeholders in the hierarchy of the structured bill of materials with their own subitems, but are not actual items themselves. The foundation catalog with the computer data set uses modular options. For more information, see the following pages and components in the foundation catalog: cat_root/pages/flypage.html cat_root/templates/components/modular_buy cat_root/templates/components/modular_update Note: Subsequent foundation catalog releases may place simple, matrix, and modular option types in separate tables. Fields
Field Descriptioncode Unique ID for the product optiono_master SKU of the master item for the optionsku SKU for the option (foreign key into products table)o_group Product grouping codeo_sort Sorting prefix for list displayphantom Boolean - Item is a phantom placeholder (as in structured bill of materials) with suboptions.o_enable Boolean - enables suboptions for the optiono_matrix Matrix-type option (preconfigured combinations of attributes)o_modular Modular-type option (master/subitem relationship like modular bill of materials)o_default Default selection for the option group or suboption for a phantom optiono_label Short name for option displayo_value Simple option values (in Interchange option format)o_widget The HTML widget to use for displaying the option groupo_footer Not used in foundation catalogo_header Not used in foundation catalogo_height Height of widget (if applicable)o_width Width of widgetdescription Option/Variant description (for description in display)price Price of this option/variantwholesale Dealer price of this option/variantdifferential Differential to add to the base item price when using a phantom bill of materialsweight Weight difference with this option/variant (for shipping)volume Volume difference with this option/variantmv_shipmode No Descriptiono_exclude Option groups to exclude (trumped by o_include). Modular only.o_include Option groups to include (trumps o_exclude). Modular only.
code Example Data
1002100310041005
Unique ID for the option. o_master Example Data
00010999000999001999002
SKU of the master item for the option. The master item is one level up in the modular hierarchy, and must be one of the following: An item in the products table (matching products.sku) Another option in the options table (matching options.sku) A phantom item in the options table. If an option has a master item, then a customer can not choose that option without having previously selected the master item. The price for a master item is the sum of the master item's price and the price for each of the subitems. Because the subitems are recursively defined, the top-level item reflects the top level price plus the price of all selected options. sku Example Data
0001099900070000157000030
The sku for the item or option. This may not be unique for matrix options or if an option that belongs to multiple o_masters is listed for each master. o_group Example Data
ABCI
Product group (scanned to see whether it applies to this product or not) o_sort Example Data
0102030447484950
Sorting prefix for listing order of options. phantom Modular options only. Boolean - if true (1), then this is a phantom item acting as a placeholder for other items rather than an actual product. The item's sku will not match an entry in the products table, though the o_master will match either the sku of another phantom item in the options table or the sku of an item in the products table. o_enable Boolean - Enables subitems for this item or option. Note that an option with o_enable false may itself still be a subitem for an option or item above it. o_matrix Boolean. Set true (1) for matrix-type options. See the options table in the tools data set for examples of matrix options. Matrix options that are part of a set have the same value for options.sku. o_modular Specifies a modular option. See main heading for description of modular options. o_default Example Data
11100270000627000087
Selects the default option for a group. o_label Example Data
Add a second hard driveCase ColorCase colorCase styleInclude tapesRed
This is the short name for option display. o_value Example Data
1=One 8GB tape,\r2=Two 8GB tapes,\r=None*a=One 8GB tape,\rb=Two 8GB tapes,\r=None*baby=Baby Tower,\rmid=Mid-tower,\rfull=Full Towerbaby=Baby tower,\rmid=Mid-tower,\rfull=Full towerred=Passion Red,\rblue=Electric Blue,\rgreen=Sea Green,\rgrey=S...red=Passion Red,\ryellow=Lemon Yellow,\rblue=Electric Blue,\rgr...red=Rage Red,\ryellow=Honey Yellow
This is an Interchange value set for a simple option. It is typically a comma-delimited list of labels and values with '*' indicating the default value. See the accessories tag for more detail. Note that the "\r" characters in the above example represent carriage returns in the actual data ("\r" in perl, or Ctrl-M, or hexadecimal 0D), and the ... indicates a line too long to show. o_widget Example Data
select
This determines the HTML Widget type (e.g., a select box). For example, the [options] tag uses this entry when building HTML widgets in a page. See also the [accessories] tag for available widgets. o_footer Example Data Allowed Values o_header Example Data Allowed Values o_height This allows you to set the height of the HTML widget, if appropriate. o_width This allows you to set the width of the HTML widget, if appropriate. description Example Data
ATX Mid Tower-Grey (3)5.25 (2)3.5 & (1)3.5 HiddenEnlight ATX Desktop Case (2)5.25 & (2)3.5Enlight ATX Tower Case (4) 5.25 & (2)3.5Micro ATX Tower - Honey YellowMicro ATX Tower - Moody BlueMicro ATX Tower - Rage RedMicro ATX Tower - Smoky GreySuper Tower Case (6)5.25 & (3)3.5
Longer description to show when displaying the options. price Example Data
0.0010202975
This sets the retail price of the option. wholesale Example Data
1340.00
This sets the dealer price of the option. differential Example Data
-209-40-79
The phantom bill of materials for an option group can have a differential, which is an amount to add to the base price of the master product to get to a new base price that accommodates the phantom bill of materials. Note that the differential can be negative. For example, in the computer data set of the foundation catalog, SKU 00011 in the products table is an $849.95 pre-configured Athlon 800MHz computer that includes a 17" monitor (in this case, SKU 7000087 in the products table). The monitor by itself would otherwise have cost $209. It is much more convenient if you can use the same option part number and price for each item. To do this, you need a phantom option (in this case, SKU 999105 in the options table only) with a differential of -209 and the available monitors as suboptions. When you include the phantom option in the bill of materials for the computer (SKU 00011), the $-209 differential adjustment makes the price work out properly. For instance, suppose that a $499 computer is configured as follows:
500 MHz Athlon -- $49932 MB SDRAM -- ZERO10 GB disk -- ZERO
TOTAL -- $499
Suppose it costs $90 to upgrade the base computer to 128M of RAM and $150 for a 30 GB hard disk. If you also sell an 128MB 800 MHz $899 computer, and the customer upgrades to the 30 GB hard disk,
800 MHz Athlon -- $899(memory differential) -- $-90128 MB RAM -- $9030 GB disk -- $150
TOTAL -- $1039
If you did not have the differential, you would need a different option part number for each item make the number come out right. With the differential, you can use the same part number for 128MB RAM no matter what the base part is. The price is always $90 -- there is just a -90 differential when ordered with the 800MHz Athlon, making the effective price zero. weight Example Data
5
Shipping weight of the option. Interchange uses this to calculate shipping cost. volume Volume added by the option. mv_shipmode No Description o_exclude Modular options only. Lists the option groups to exclude once the include has been done. Takes the form of a number of wildcard atoms. o_include Modular options only. Lists the option groups to include with your item. Takes the form of a number of wildcard atoms.
order_returns.txt
codeorder_numbersessionusernamerma_numbernitemstotalreturn_dateupdate_date
orderline.txt Every line item that is actually ordered is detailed in this table. The order as a whole is one record in the transactions table. See the page query/check_orders.html for how it can be used. See etc/report for how to add to it.
codestore_idorder_numbersessionusernameshipmodeskuquantitypricesubtotalshippingtaxablemv_mimv_sisizecoloroptionsorder_dateupdate_datestatuspending = Pendingshipped = Shippedbackorder = Back orderedcredit = Waiting for credit checkcanceled = Cancelledparentaffiliatecampaigndescriptionmv_mp
pricing This database works in conjunction with the CommonAdjust directive to allow quantity pricing for one product or for a group of products (sometimes known as mix-and-match). The fields q2, q5, q10, etc. are for the quantity levels; the price_group field selects the mix-and-match category for the product. Fields
Field Descriptionsku Unique key, shared with products tableprice_group Mix-and-match categoryq2 Retail, 2 or moreq5 Retail, 5 or moreq10 Retail, 10 or moreq25 Retail, 25 or moreq100 Retail, 100 or morew2 Wholesale, 2 or morew5 Wholesale, 5 or morew10 Wholesale, 10 or morew25 Wholesale, 25 or morew100 Wholesale, 100 or more
sku Example Data
os28004os28006os28057cos28069
Unique key, matching the sku for an entry in products table. price_group Example Data
general
This field determines mix-and-match categories if you want to allow mix-and-match quantity pricing (i.e., where 5 of these plus 5 of those afford the q10 price for both these and those). q2 If set, this will be the price per item when the order quantity is 2 or greater. q5 If set, this will be the price per item when the order quantity is 5 or greater. q10 If set, this will be the price per item when the order quantity is 10 or greater. q25 If set, this will be the price per item when the order quantity is 25 or greater. q100 If set, this will be the price per item when the order quantity is 100 or greater. w2 If set, this will be the dealer price per item when the order quantity is 2 or greater. w5 If set, this will be the dealer price per item when the order quantity is 5 or greater. w10 If set, this will be the dealer price per item when the order quantity is 10 or greater. w25 If set, this will be the dealer price per item when the order quantity is 25 or greater. w100 If set, this will be the dealer price per item when the order quantity is 100 or greater.
products This is the main table for product data. See also 'The Product Database' section in the database documentation. The sku is also the master key in many of the related tables. Fields
Field Descriptionsku Unique product IDdescription Short description for list displaytitle Full title for book, CD, artwork, etc.template_page Not used in foundation catalog. No description.comment Longer description for item display (e.g., flypage.html)thumb Thumbnail imageimage Regular-sized imageprice Retail quantity one pricewholesale Dealer minimum quantity priceprod_group Product supercategorycategory Product categorynontaxable Boolean. Set true (1) if nontaxableweight Weight in your units. Should match shipping table.size List of options used with accessories tag.color List of options used with accessories tag.gift_cert Boolean. Set true (1) if this is a gift certificate.related Deprecated in favor of merchandising.upsell_tofeatured Deprecated. Use merchandising table.inactive Boolean. Set true (1) to inactivate a producturl Not Documented
sku Example Data
gift_certos28004os28006os28057c
Unique identifier for the product. You should use only characters of the class A-Z a-z 0-9 _ - (i.e., matching the regular expression, '[-A-Za-z0-9_]+'). Although Interchange itself does not impose this restriction, you may have problems with SQL databases, file systems, and URL encoding if you use other characters. For example, a slash (/) can interfere with URLs and filenames, a colon (:) can interfere with database representations (or file names on some operating systems), i<etc.> description Example Data
Brush SetDisposable Brush SetErgo RollerGift CertificatePainters Brush SetPainters LadderSpackling KnifeTrim Brush
A short description for the product that is used for displaying in the shopping cart, receipt, and order report. title Example Data
Brush SetDisposable Brush SetErgo RollerGift CertificatePainters Brush SetPainters LadderSpackling KnifeTrim Brush
This column is not used in the foundation catalog. Previously used in the Art store (simple) demo for a painting title. You probably want to use description instead. You should modify the products and other tables to suit your catalog's requirements. You might use this field if you want to show titles for books, music, or other titled merchandise. If you do not use a title that is distinct from the short description, then you probably do not need this column in the table at all. template_page Not used in foundation catalog. No Description. comment Example Data
A must have for all painters! This spackling knife is ergon...Enjoy the perfect feel and swing of our line of hammers. Thi...This set includes 2" and 3" trim brushes and our ergonomical...This set of disposable foam brushes is ideal for any stainin...
This is the field for a long description of the product. If you are using an Interchange text/gdbm database, the field size is unlimited; if using another type of database, the length will be dependent on the field type selected. If you are using a SQL database, see the appropriate cat_root/dbconf subdirectory for a place to set COLUMN_DEF values. See also the database documentation, 'Importing from an ASCII File', for details about defaults for columns that you do not define. thumb Example Data
gift_certificate.gifos28004_b.gifos28005_b.gifos28006_b.gif
This is the filename for a small (thumbnail) image of the product. image Example Data
gift_certificate_large.gifos28004.gifos28005.gifos28006.gif
This is the filename for a regular-sized image of the product, as it should appear in an HTML <img src="image"> tag. You do not need to specify the path if the image files are in the usual Interchange image directory. price Example Data
1.0012.9914.999.99
The quantity-one price of the product. See the wholesale field and the price table for dealer and quantity pricing. wholesale Example Data
1101112
This is the minimum dealer price for the item. For quantity pricing, see the price table. prod_group Example Data
Hand ToolsHardwareLaddersMeasuring ToolsMiscellaneousPainting SuppliesSafety EquipmentTool Storage
Product group (supercategory). This indicates the grouping of product categories, for example in the navigation bars created from the area table (note the match with the name data in the area table). category Example Data
BrushesGift CertificateHammersLaddersNailsPaintbrushesPutty KnivesRollers
This is the category the product should appear in when you select a list. You can put a product in more than one category, but you may need to accommodate this in display and banner headings. Embedded perl is helpful for this. nontaxable Boolean value. If true (1), the sales tax calculation for an order will not include the cost of the product. See also the salestax tag. weight Example Data
123
This is a numeric value of the weight used for determining shipping costs (with UPS, for example). In the US, this is typically the weight in pounds in order to match the UPS, Fed Ex and other standard shipping tables. size Example Data
1", 2", 3"1', 1.5'1/4", 1/2", 3/4", 1", 2", 3"10oz, 15oz, 20 oz2"6'setstandard, metric
This is where the old Construct Something demo store kept the 'size' options for a product. The foundation catalog now uses the options table instead to handle product options (also sometimes called product attributes). The accessories tag can build HTML widgets from the comma-delimited list of product options. You can use a delimiter other than comma (if compatible with the table) as long as you also set the delimiter in the accessories tag. You probably do not need this field if you use the options table (for example, if you are building from the foundation catalog). color Another product option column. No longer used in the foundation catalog. See size above for description. gift_cert Boolean value. If true (1), specifies that this product is a gift certificate. See also the gift_certs table. related Used for displaying "upsells," opportunities to purchase an additional item when this one is purchased. Contains a comma-separated list of SKUs to be offered. The foundation catalog now instead uses the upsell_to field of the merchandising table for upselling. featured Deprecated in favor of the merchandising table. inactive If true (1), renders the product inactive (i.e., it will not appear in the catalog). url Not Documented
products.category.txt The products.category.txt table (actually a link to products.txt.10) is an automatically generated index into the products table to speed category searches. See Dictionary Indexing With INDEX in the database documentation for details about auto-indexing of text databases.
route.txt
codeattachcontinuecommitcommit_tablescountercredit_cardcyber_modeemptyencryptencrypt_programerrors_toincrementinline_profileindividual_trackindividual_track_extpartialpgp_cc_keypgp_keyprofilereceiptreplyreportrollbackrollback_tablessupplanttrack
salestax.asc
shipping.asc Shipping methods table
state.txt State/territory/county information
codesordercountrystatenametaxpostcodeshipmodestax_name
transactions.txt Each individual customer order has an entry in this table. The line items are not entered here, but in the orderline table. See the page query/check_orders.html for how it can be used. See etc/report for how to add to it.
codestore_idorder_numbersessionusernameshipmodenitemssubtotalshippinghandlingsalestaxtotal_costfnamelnameLast Namecompanyaddress1address2Address line 2citystatezipcountryphone_dayDaytime Phonephone_nightHome Phonefaxb_fnameb_lnameBilling Last Nameb_companyb_address1b_address2Billing Address Line 2b_cityb_stateBilling Stateb_zipBilling Postcodeb_countryBilling Countryb_phoneorder_dateorder_ymdorder_wdaypayment_methodpo_numberavsorder_idupdate_datestatusaffiliatecampaignparentarchiveddeletedcompletecomments
userdb.txt The user database used for maintaining customer address information, account information, preferences, and more. See icdatabase for more information.
usernamepasswordaclmod_times_nicknamecompanyfnamelnameaddress1address2address3citystatezipPostcodecountryCountryphone_daymv_shipmodeb_nicknameb_fnameb_lnameb_address1b_address2b_address3b_cityb_stateb_zipb_countryb_phoneBilling Phonemv_credit_card_typemv_credit_card_exp_monthmv_credit_card_exp_yearp_nicknamefaxphone_nightfax_orderPayment method:(none) = Credit Card1 = Fax or Mail2 = Purchase order3 = CODaddress_bookaccountspreferencescartsownerfile_acldb_aclorder_numbersemail_copymail_listMailing lists the customer has joined:offer = Special offersnewsletter = Newsletteralert = Alerts and Recallsupgrade = Upgradesproject_idaccount_idorder_destcredit_limitinactivedealerDealer:(none) = No1 = Yesb_companyfeedback???
variable.txt Configuration database
codeVariable nameVariablepref_groupPreferences area
Normally, regular hypertext links are not used in Interchange pages. These kinds of links will not include the session ID. If the customer follows an external link back to the catalog, the list of products ordered so far will have been lost. The area tag is used to generate a hypertext link which includes a session ID. Instead of:
<A HREF="/cgi-bin/mv/shirts">Shirts</A>
Use:
<A HREF="[area shirts]">Shirts</A>
Inline images are placed in Interchange pages in the normal fashion with <IMG SRC="URL">. But since Interchange pages are served by a CGI program, do not use relative links. The Foundation store defines an image directory with the ImageDir and ImageDirSecure directives that automatically adjusts the image path to a set base directory. The Foundation store enables the Cookies directive so that users with cookie-capable browsers will retain session context. Then, standard HREF and Interchange page links can be intermixed without the fear of losing the shopping basket. Cookie capability is also required to use search caching, page caching, and statically generated pages. If the user's browser does not support cookies, the cache will be ignored. If planning to use more than one host name within the same domain for naming purposes (perhaps a secure server and non-secure server), set the domain with the CookieDomain directive. This must contain at least two periods (.) as per the cookie specification, and must be located in the same server as the domain. In general, it's a good idea to leave fields empty if you don't want to use them, instead of removing them from the database altogether. That way nothing in admin or demo will break.
________________________________________
Copyright 2001 Red Hat, Inc. Freely redistributable under terms of the GNU General Public License.