Fetching contributors…
Cannot retrieve contributors at this time
1675 lines (1205 sloc) 58.1 KB
!init OPT_LOOK="icdevgroup"; OPT_STYLE="manual"
# $Id: ic_ecommerce.sdf,v 1.25 2004-05-05 15:22:29 jon Exp $
!define DOC_NAME "Interchange Ecommerce Functions"
!define DOC_TYPE ""
!define DOC_CODE "ic_ecommerce"
!define DOC_VERSION substr('$Revision: 1.25 $',11, -2)
!define DOC_STATUS "Draft"
!define DOC_PROJECT "Interchange"
!define DOC_URL ""
Interchange has a completely flexible order basket and checkout
scheme. The C<foundation> demo presents a common use of this process,
in the directory pages/ord -- the files are:
> basket.html The order basket displayed by default
> checkout.html The form where the customer enters their billing
> and shipping info
... and in the directory etc:
> receipt.html The receipt displayed to the customer
> report The order report mailed to you
> mail_receipt The customer's email copy (if requested)
It is not strictly necessary to display an order basket when
an item is ordered. If you specify a different page to be
displayed that is fine, but most customers will be confused if
you don't give them an indication that the order operation has
Any order basket is an HTML C<FORM>. It will have a number of
variables on it. At the minimum it must have an C<[item-list]> to
loop through the items, and the C<quantity> of each item must be
set in some place on that form. Any valid Interchange tags may be
used on the page, and you may use multiple item lists if necessary.
H2: How to order an item
Interchange can either use a form-based order or a link-based order to
place an item in the shopping cart. The link-based order uses the
special C<[order item-code]> tag:
=over 4
=item [order code]
named attributes:
> [order code="sku" quantity="n"* href="page"* cart="cartname"* base="table"*]
> * = optional parameters
Expands into a hypertext link which will include the specified
code in the list of products to order and display the order page. B<code>
should be a product SKU listed in one of the "products" tables, and is the
only required parameter. B<quantity> may be specified if more than one
(the default) of the item should be
placed in the cart. B<href> allows some page other than the default order
page to be displayed once the item has been added to the cart. B<cart>
selects the shopping cart the item will be placed in. The optional argument
B<base> constrains
the order to a particular products file -- if not specified, all tables
defined as products files will be searched in sequence for the item.
N: Example:
> Order a [order TK112]Toaster</a> today.
Note that this is the same as:
> Order a [page order TK112]Toaster</A> today.
You can change frames for the order with:
> Order a <A HREF="[area order TK112]" TARGET=newframe>Toaster</A> today.
=item [/order]
Expands into </a>. May be used to give the order tag the appearance
of being a container tag, but neither necessary nor recommended.
To order with a form, you set the form variable C<mv_order_item> to
the item-code/SKU and use the C<refresh> action:
> <FORM ACTION="[process-target]" METHOD=POST>
> <INPUT TYPE=hidden NAME="mv_todo" VALUE="refresh">
> <INPUT TYPE=hidden NAME="mv_order_item" VALUE="TK112">
> Order <INPUT NAME="mv_order_quantity" SIZE=3 VALUE=1> toaster
> <INPUT TYPE=submit VALUE="Order!">
> </FORM>
You may batch select whole groups of items:
> <FORM ACTION="[process-target]" METHOD=POST>
> <INPUT TYPE=hidden NAME="mv_todo" VALUE="refresh">
> <INPUT TYPE=hidden NAME="mv_order_item" VALUE="TK112">
> <INPUT NAME="mv_order_quantity" SIZE=3> Standard Toaster
> <INPUT TYPE=hidden NAME="mv_order_item" VALUE="TK200">
> <INPUT NAME="mv_order_quantity" SIZE=3> Super Toaster
> <INPUT TYPE=submit VALUE="Order!">
> </FORM>
Items that have a quantity of zero (or blank) will be skipped, and only
items with a positive quantity will be placed in the basket.
You may also specify attributes like size or color at time of order (see
I<How to set up an order button>).
H2: How to set up an order link
On a product display page, use:
> [order 00-0011]Order the Mona Lisa</a>
If coming from a search results or on-the-fly page, you may use the generated
C<[item-code]> thusly:
> [order [item-code]]Order [item-field name]</a>
Bear in mind that if you have not reached the page via a search or
on-the-fly operation, C<[item-code]> means nothing and will cause an error.
H2: How to set up an order button
Interchange can order via form submission as well. This allows you
to order a product (or group of products) via a form button. In its
simplest form, it is:
> <FORM ACTION="[process-target]" METHOD=POST>
> <INPUT TYPE=hidden NAME=mv_todo VALUE=refresh>
> <INPUT TYPE=hidden NAME=mv_order_item VALUE="00-0011">
> <INPUT TYPE=submit VALUE="Order the Mona Lisa">
> </FORM>
The default quantity is one. An initial quantity may be set by the user
by adding an mv_order_quantity variable:
> Number to order:<INPUT TYPE=text NAME=mv_order_quantity VALUE="1">
You can order multiple items by stacking the variables:
> <FORM ACTION="[process-target]" METHOD=POST>
> <INPUT TYPE=hidden NAME=mv_todo VALUE=refresh>
> <INPUT TYPE=hidden NAME=mv_order_item VALUE="00-0011">
> <INPUT TYPE=hidden NAME=mv_order_item VALUE="00-0011a">
> <INPUT TYPE=submit VALUE="Order the Mona Lisa with frame">
> </FORM>
Initial size or color may be set as well, provided I<UseModifier> is
set up properly:
> <INPUT TYPE=hidden NAME=mv_order_size VALUE="L">
If the order is coming from a generated flypage, loop list, or search
results page, you can get a canned select box from the
C<[item-accessories size]> or C<[item-accessories size]> tag. See
I<Item Attributes>.
H2: How to set up an on-the-fly item
If you enable the catalog directive I<OnFly>, setting it to the
name of a subroutine (or possibly a UserTag) that can handle its calls, then
Interchange will add items to the basket that are not in the product
database. Interchange supplies an internal C<onfly> subroutine, which
will work according to the examples given below.
In C<catalog.cfg>:
> OnFly onfly
If your item code is not to be named C<mv_order_item> then you
must perform a rename in the C<Autoload> routine.
A basic link can be generated like:
> <a href="[area form="
> mv_todo=refresh
> mv_order_item=000101
> mv_order_fly=description=An on-the-fly item|price=100.01
> "]">Order item 000101</a>
The form parameter value C<mv_order_fly> can contain any number of fields
which will set corresponding parameters in the item attributes. The fields
are separated by the pipe (C<|>) character and contain value-parameter
pairs separated by an = sign. (These are URL-encoded by the C<[area ...]> or
C<[page ...]> tag, of course.) You can set a size, color, or any other parameter.
The special attribute C<mv_price> can be used in conjunction with the
C<CommonAdjust> atom C<$> to set the price for checkout and display.
The C<[item-list]> sub-tag C<[item-description]>, when used with an
item-list, will use the item attribute C<description> to display in the
basket. Note that C<[item-field description]> or C<[item-data products description]>
will NOT work, as both of these tags reference an actual field value for
a record in the products table - not applicable for on-the-fly items.
Similarly, an attempt to generate a flypage for an on-the-fly item
(C<[page 000101]>, for example) will fail, resulting in the display of
the SpecialPage B<missing>.
If you wish to set up a UserTag to process on-the-fly items, it should
accept a call of
> usertag(mv_item_code, mv_item_quantity, mv_order_fly)
The C<mv_item_code> and C<mv_order_fly> parameters are required to trigger
Interchange's C<add_item> routine (along with mv_todo=refresh to set the action).
The item will always act as if C<SeparateItems> or C<mv_separate_items> is
Multiple items can be ordered at once by stacking the variables. If there
is only one C<mv_order_item> instance, however, you can stack the C<mv_order_fly>
variable so that all are concatenated together as with the C<|> symbol. So
the above example could be done as:
> [area form="
> mv_todo=refresh
> mv_order_item=000101
> mv_order_fly=description=An on-the-fly item
> mv_order_fly=price=100.00
> "]
Multiple items would need multiple instances of C<mv_order_item> with
a corresponding C<mv_order_fly> for each C<mv_order_item>. You can
order both C<000101> and C<000101> as follows:
> [area form="
> mv_todo=refresh
> mv_order_item=000101
> mv_order_fly=description=An on-the-fly item|price=100.00
> mv_order_item=000102
> mv_order_fly=description=Another on-the-fly item|price=200.00
> "]
The following two forms correspond to the above two examples, in order,
with the slight refinement of adding a quantity:
> <FORM ACTION="[area process]" METHOD=POST>
> <INPUT TYPE=hidden NAME=mv_todo VALUE="refresh">
> <INPUT TYPE=hidden NAME=mv_order_item VALUE="000101">
> Qty: <INPUT SIZE=2 NAME=mv_order_quantity VALUE="1">
> <INPUT TYPE=hidden NAME=mv_order_fly
> VALUE="description=An on-the-fly item|price=100.00">
> <INPUT TYPE=submit VALUE="Order button">
> </FORM>
> <FORM ACTION="[area process]" METHOD=POST>
> <INPUT TYPE=hidden NAME=mv_todo VALUE="refresh">
> <INPUT TYPE=hidden NAME=mv_order_item VALUE="000101">
> Qty: <INPUT SIZE=2 NAME=mv_order_quantity VALUE="1"><BR>
> <INPUT TYPE=hidden NAME=mv_order_fly
> VALUE="description=An on-the-fly item|price=100.00">
> <INPUT TYPE=hidden NAME=mv_order_item VALUE="000102">
> Qty: <INPUT SIZE=2 NAME=mv_order_quantity VALUE="1"><BR>
> <INPUT TYPE=hidden NAME=mv_order_fly
> VALUE="description=Another on-the-fly item|price=200.00">
> <INPUT TYPE=submit VALUE="Order two different with a button">
> </FORM>
H2: Order Groups
Interchange allows you to group items together, making a master item
and sub-items. This can be used to delete accessories or options when
the master item is deleted. In its simplest form, you order just one
master item and all subsequent items are sub-items.
> <FORM ACTION="[process-target]" METHOD=POST>
> <INPUT TYPE=hidden NAME=mv_todo VALUE=refresh>
> <INPUT TYPE=hidden NAME=mv_order_group VALUE="1">
> <INPUT TYPE=hidden NAME=mv_order_item VALUE="00-0011">
> <INPUT TYPE=hidden NAME=mv_order_item VALUE="00-0011a">
> <INPUT TYPE=submit VALUE="Order the Mona Lisa with frame">
> </FORM>
If you wish to stack more than one master item, then you must define
mv_order_group for B<all> items, with either a 1 value (master) or 0 value
(sub-item). A master owns all subsequent sub-items until the next master
is defined.
> <FORM ACTION="[process-target]" METHOD=POST>
> <INPUT TYPE=hidden NAME=mv_todo VALUE=refresh>
> <INPUT TYPE=hidden NAME=mv_order_group VALUE="1">
> <INPUT TYPE=hidden NAME=mv_order_item VALUE="00-0011">
> <INPUT TYPE=hidden NAME=mv_order_group VALUE="0">
> <INPUT TYPE=hidden NAME=mv_order_item VALUE="00-0011a">
> <INPUT TYPE=hidden NAME=mv_order_group VALUE="1">
> <INPUT TYPE=hidden NAME=mv_order_item VALUE="19-202">
> <INPUT TYPE=hidden NAME=mv_order_group VALUE="0">
> <INPUT TYPE=hidden NAME=mv_order_item VALUE="99-102">
> <INPUT TYPE=submit VALUE="Order items">
> </FORM>
When the master item C<00-0011> is deleted from the basket,
C<00-0011a> will be deleted as well. And when 19-202 is deleted,
then 99-102 will be deleted from the basket.
\NOTE: Use of checkboxes for this type of thing can be hazardous, as they
do not pass a value when unchecked. It is preferable to use radio groups
or select/drop-down widgets. If you must use checkboxes, be sure to
explicitly clear C<mv_order_group> and C<mv_order_item> somewhere on the
page which contains the form:
> [value name=mv_order_group set='']
> [value name=mv_order_item set='']
The attributes C<mv_mi> and C<mv_si> are set to the group and sub-item status
of each item. The group, contained in the attribute C<mv_mi>, is a
meaningless yet unique integer. All items in a group will have the same
value of C<mv_mi>. The attribute C<mv_si> is set to 0 if the item is
a master item, and 1 if it is a sub-item.
H2: Basket display
The basket page(s) are where the items are tracked and adjusted by the
customer. It is possible to have an unlimited number of basket pages.
It is also possible to have multiple shopping carts, as in buy or
sell. This allows a basket/checkout type of ordering scheme, with custom
order pages for items which have many accessories.
The name of the page to display can be configured in several
^ Set the SpecialPage C<order> to the page to display
when an item is ordered.
+ Use the C<[order code=item page=page_name] Order it! </aE<gt>> form of
order tag to specify an arbitrary order page for an item.
+ If already on an order page, set the mv_orderpage,
mv_nextpage, mv_successpage, or mv_failpage variables.
The following variables can be used to control cart selection and
page display:
=over 4
=item mv_cartname
The shopping cart (default is main) to be used for this order
=item mv_failpage
Page to be displayed on a failed order
check (see I<Advanced Multi-level Order Pages>)
=item mv_nextpage
Page to display on a return operation.
=item mv_orderpage
Page to be displayed on a refresh.
=item mv_successpage
Page to be displayed on a successful order
check (see I<Advanced Multi-level Order Pages>).
=item mv_order_profile
Order profile to be used if the form action is F<submit>
(see I<Advanced Multi-level Order Pages>).
H2: Multiple Shopping Carts
Interchange allows you to define and maintain multiple shopping carts.
One shopping cart -- main, by name -- is defined when the user session
starts. If the user orders item M1212 with the following tag:
> [order code=M1212 cart=layaway] Order this item! </a>
the order will be placed in the cart named I<layaway>. However, by default
you won't see the just-ordered item on the basket page. That is because
the default shopping basket displays the contents of the 'main' cart only.
So copy the default basket page (pages/ord/basket.html in the demo)
to a new file, insert a C<[cart layaway]> tag, and specify it as the target
page in your C<[order]> tag:
> [order code=M1212 cart=layaway page=ord/lay_basket] Order this item! </a>
Now the contents of the I<layaway> cart will be displayed. Most of the ITL
tags that are fundamental to cart display accept a 'cartname' option,
allowing you to specify which cart to be used:
=over 4
=item [cart cartname]
A 'sticky' setting of the default cart name to use for all subsequent
cart-related tags. Convenient, but you must remember to use C<[cart main]>
to get back to the primary cart! As an alternative, you can specify the
desired cart as a parameter of the other tags. These are not sticky,
referencing the specified cart only for the instance in which they are called:
=item [item-list cartname]...[/item-list]
Iterates over the items in the specified cart - tags like C<[item-quantity]>
and C<[item-price]> will be evaluated accordingly;
=item [nitems cartname]
Returns the total number of items in the specified cart;
=item [subtotal cartname]
Returns the monetary subtotal for the contents of specified cart;
=item [shipping cartname], [handling cartname], [salestax cartname], [total-cost cartname]
You get the idea. It is worth noting that tags which summarize
cart contents do not need to be in used concert, or in conjunction with
an C<[item-list]>. For instance, you can display just the grand
total for a cart on the sidebar or bottom of each page, using
C<[total-cost]> by itself, if you wish.
You can also order items from a form, using the C<mv_order_item>,
C<mv_cartname>, and optional C<mv_order_quantity> variables.
> <input type=checkbox name="mv_order_item" value="M3243"> Item M3243
> <input name="mv_order_quantity" value="1"> Quantity
> <input type=hidden name="mv_cartname" value="layaway">
> <input type=hidden name="mv_doit" value="refresh">
> <input type=submit name="mv_junk" value="Place on Layaway Now!">
> </FORM>
If you need to utilize an alternative item price in conjunction with
the use of a custom cart, see the section on I<PRODUCT PRICING> for
pricing methods and strategies.
Interchange maintains a price in its database for every product. The price
field is the one required field in the product database -- it is necessary
to build the price routines.
For speed, Interchange builds the code that is used to determine a product's
price at catalog configuration time. If you choose to change a directive
that affects product pricing you must reconfigure the catalog.
H2: Simple pricing
The simplest method is flat pricing based on a fixed value in
the C<products> database. If you put that price in a field named
C<price>, you don't need to do more. If you want to change pricing
based on quantity, size, color or other factors read on.
H2: Price Maintenance with CommonAdjust
A flexible chained pricing scheme is available
when the I<CommonAdjust> directive is set.
We talk below about a I<CommonAdjust string>; it will be defined
in due time.
A few rules about CommonAdjust, all assuming the I<PriceField> directive
is set to C<price>:
LI1: 1
If C<CommonAdjust> is set to any value, a valid I<CommonAdjust string> or
not, extended price adjustments are enabled. It may also hold the
default pricing scheme.
LI1: 2
The C<price> field may also hold a I<CommonAdjust string>. It takes
precedence over the default.
LI1: 3
If the value of the C<CommonAdjust> directive is set to a CommonAdjust
string, and the C<price> field is empty or specifically I<0>, then it
will be used to set the price of the items.
LI1: 4
If no CommonAdjust strings are found, then the price will be 0, subject
to any later application of discounts.
LI1: 5
If another CommonAdjust string is found as the result of an operation,
it will be re-parsed and the result applied. Chaining is retained; a
fallback may be passed and will take effect.
Prices may be adjusted in several ways, and the individual actions
are referred to below as I<atoms>. Price atoms may be I<final>,
I<chained>, or I<fallback>. A final price atom is always applied if it
does not evaluate to zero. A chained price atom is subject to further
adjustment. A fallback price atom is skipped if a previous chained price
was not zero.
Atoms are separated by whitespace, and may be quoted (although there
should not normally be whitespace in a setting). A chained item ends
with a comma. A fallback item has a leading semi-colon. Final atoms
have no comma appended or semi-colon prepended.
A I<settor> is the means by which the price is set.
There are eight different types of price settors. All settors
can then yield another CommonAdjust string.
It is quite possible to create endless loops, so the maximum
number of initial CommonAdjust strings is set to 16, and there
may be only 32 iterations by default before the price will return zero on
an error. (The maximum iterations is specified with
the {{CMD[jump="icconfig.html#Limit"]Limit}} directive.)
B<NOTE>: Common needs are easily shown but not so easily explained;
skip to the examples in the reference below if your vision starts to
blur when reading the next section. 8-)
\USAGE: Optional items below have asterisks appended. The asterisk should
not be used in the actual string. Optional B<base> or B<table> always
defaults to the active C<products> database table. The optional B<key>
defaults to the item code except in a special case for the attribute-based
lookup. The B<field> name is not optional except in the case of an
attribute lookup.
=item N.NN or -N.NN
where N is a digit. A number which is applied directly; for instance
10 will yield a price of 10. May be a positive or negative number.
=item N.NN%
where N is a digit. A number which is applied as a percentage of
the I<current> price value. May be a positive or negative number. For
example, if the price is 10 and -8% is applied, the next price value
will be 9.20.
=item table*:column:key*
Causes a straight lookup in a database table. The optional B<table>
defaults to the main products database table for the item (subject
of course to multiple product files). The B<column> must always
be present. The optional B<key> defaults to the item code except
in a special case for the attribute-based lookup. The return value
is then re-parsed as another price settor.
=item table*:col1..col5,col10:key*
Causes a quantity lookup in database table B<table> (which defaults to
the products database), with a set of comma-separated fields, looked
up by the optional B<key>. (Key defaults to the item code, of course).
If ranges are specified with .., each column in the sequence will be used;
> pricing:p1,p2,p3,p4,p5,p10:
is the same as
> pricing:p1..p5,p10:
Leading non-digits are stripped, and the item quantity is compared with
the numerical portion of the column name. The price is set to the value of
the database column (numeric portion) that is at least equal to it but
doesn't yet reach the next break.
\WARNING: If the field at the appropriate quantity level is blank,
a zero cost will be returned from the atom. It is important to
have all columns populated.
=item ==attribute:table*:column*:key*
Does an attribute-based adjustment. The attribute is looked up in the
database B<table>, with the optional B<column> defaulting to the same
name as the I<value> of the B<attribute>. If the column is not left blank,
the I<key> is set to the I<value> of the B<attribute> if blank.
=item & CODE
The leading C<&> sign is stripped and the code is passed to the
equivalent of a C<[calc]> tag. No Interchange tags can be used, but
the &tag_data routine is available, the current value of the price
and quantity are available as C<$s>, and the current item (code, quantity,
price, and any attributes) are available as C<$item>, all forced
to the package Vend::Interpolate. That means that in a UserTag:
> $Vend::Interpolate::item is the current item
> $Vend::Interpolate::item->{code} gives key for current item
> $Vend::Interpolate::item->{size} gives size for current item (if there)
> $Vend::Interpolate::item->{mv_ib} gives database ordered from
=item [valid Interchange tags]
If the settor begins with a square bracket (C<[>) or underscore, it
is parsed for Interchange tags with variable substitution (but no Locale
substitution). You may define a price in a I<Variable> in this fashion.
The string is re-submitted as an atom, so it may yield yet another
=item $
Tells Interchange to look in the C<mv_price> attribute of the shopping cart,
and apply that price as the final price, if it exists. The attribute must
be a numerical value.
=item >>word
Tells the routine to return C<word> directly as the result. This is not
useful in pricing, as it will evaluate to zero. But when CommonAdjust
is used for shipping, it is a way of re-directing shipping modes.
=item word
The value of C<word>, which must not match any of the other settors,
is available as a key for the next lookup (only). If the next settor
is a database lookup, and it contains a dollar sign (C<$>) the C<word>
will be substituted; i.e. C<table:column:$> becomes C<table:column:word>.
=item ( settor )
The value returned by C<settor> will be used as a key for the next
lookup, as above.
H2: CommonAdjust Examples
Most examples below use an outboard database table named B<pricing>, but
any valid table including the B<products> table can be used. We will refer
to this B<pricing> table:
> code common q1 q5 q10 XL S red
> 99-102 10 9 8 1 -0.50 0.75
> 00-343 2
> red 0.75
The simplest case is a straight lookup on an attribute; I<size> in this
> 10.00, ==size:pricing
With this value in the C<price> field, a base price of 10.00 will be
adjusted with the value of the I<size> attribute. If size for the item
99-102 is set to C<XL> then 1.00 will be added for a total price of 11.00;
if it is C<S> then .50 will be subtracted for a total price of 9.50;
for any other value of I<size> no further adjustment would be made. 00-343
would be adjusted up 2.00 only for I<XL>.
> 10.00, ==size:pricing, ==color:pricing
This is the same as above, except both size and color are adjusted for.
A color value of red for item code 99-102 would add 0.75 to the price. For
00-343 it would have no effect.
> 10.00, ==size:pricing, ==color:pricing:common
Here price is set based on a common column, keyed by the value of the
color attribute. Any item with a color value of red would have 0.75 added
to the base price.
> pricing:q1,q5,q10:, ;10.00, ==size:pricing, ==color:pricing:common
Here is a quantity price lookup, with a fallback price setting. If there
is a valid price found at the quantity of 1, 5, or 10, depending on
item quantity, then it will be used. The fallback of 10.00 only applies if no
non-zero/non-blank price was found at the quantity lookup. In either
case, size/color adjustment is applied.
> pricing:q1,q5,q10:, ;10.00 ==size:pricing, ==color:pricing:common
Removing the comma from the end of the fallback string stops color/size
lookup if it reaches that point. If a quantity price was found, then size
and color are chained.
> pricing:q1,q5,q10:, ;products:list_price, ==size:pricing, ==color:pricing
The value of the database column C<list_price> is used as a fallback
instead of the fixed 10.00 value. The above value might be a nice one
to use as the default for a typical retail catalog that has items with
colors and sizes.
H2: PriceBreaks, discounts, and PriceAdjustment
There are several ways that Interchange can modify the price of a product during
normal catalog operation. Several of them require that the I<pricing.asc>
file be present, and that you define a pricing database. You do that by
placing the following directive in I<catalog.cfg>:
> Database pricing pricing.asc 1
\NOTE: PriceAdjustment is slightly deprecated by CommonAdjust, but
will remain in use at least through the end of Version 3 of Interchange.
Configurable directives and tags with regard to pricing:
=over 4
=item *
Quantity price breaks are configured by means of the I<PriceBreaks> and
I<MixMatch> directives. They require a field named specifically C<price>
in the pricing database. The B<price> field contains a space-separated
list of prices that correspond to the quantity levels defined in the
F<PriceBreaks> directive. If quantity is to be applied to all items in
the shopping cart (as opposed to quantity of just that item) then the
I<MixMatch> directive should be set to B<Yes>.
=item *
Individual line-item prices can be adjusted according to the value of
their attributes. See I<PriceAdjustment> and I<CommonAdjust>. The
pricing database B<must> be defined unless you define the F<CommonAdjust>
=item *
Product discounts for individual products, specific product codes,
all products, or the entire order can be configured with the C<[discount ...]>
tag. Discounts are applied on a per-user basis -- you can gate the
discount based on membership in a club or other arbitrary means. See
I<Product Discounts>.
For example, if you decided to adjust the price of T-shirt part number
99-102 up 1.00 when the size is extra large and down 1.00 when the size is small,
you would have the following directives defined in <catalog.cfg>:
> Database pricing pricing.asc 1
> UseModifier size
> PriceAdjustment size
To enable automatic modifier handling, you define a size field in
> code description price size
> 99-102 T-Shirt 10.00 S=Small, M=Medium, L=Large*, XL=Extra Large
You would place the proper tag within your C<[item-list]> on the shopping-basket
or order page:
> [item-accessories size]
In the pricing.asc database source, you would need:
> code S XL
> 99-102 -1.00 1.00
If you want to assign a price based on the option, precede the number
with an equals sign:
> code S M L XL
> 99-102 =9.00 =10 =10 =11
IMPORTANT NOTE: Price adjustments occur AFTER quantity price breaks, so
the above would negate anything set with the I<PriceBreaks> directive/option.
Numbers that begin with an equals sign (C<=>) are used as absolute
prices and are I<interpolated for Interchange tags first>, so you can
use subroutines to set the price. To facilitate coordination with the
subroutine, the session variables C<item_code> and C<item_quantity> are
set to the code and quantity of the item being evaluated. They would
be accessed in a global subroutine with C<$Vend::Session->>C<{item_code}>
and C<$Vend::Session->>C<{item_quantity}>.
The pricing information must always come from a database because
of security.
H2: Item Attributes
Interchange allows item attributes to be set for each ordered item. This
allows a size, color, or other modifier to be attached to a common
part number. If multiple attributes are set, then they should be
separated by commas. Previous attribute values can be saved by means
of a hidden field on a form, and multiple attributes for each item
can be I<stacked> on top of each other.
The configuration file directive I<UseModifier> is used to set
the name of the modifier or modifiers. For example
> UseModifier size,color
will attach both a size and color attribute to each item code that
is ordered.
B<IMPORTANT NOTE:> You may not use the following names for attributes:
> item group quantity code mv_ib mv_mi mv_si
You can also set it in scratch with the mv_UseModifier
scratch variable -- C<[set mv_UseModifier]size color[/set]> has the
same effect as above. This allows multiple options to be set for
products. Whichever one is in effect at order time will be used.
Be careful, you cannot set it more than once on the same page.
Setting the C<mv_separate_items> or global directive I<SeparateItems>
places each ordered item on a separate line, simplifying attribute
handling. The scratch setting for C<mv_separate_items> has the same
The modifier value is accessed in the C<[item-list]> loop with the
C<[item-modifier attribute]> tag, and form input fields are placed with the
C<[modifier-name attribute]> tag. This is similar to the way that quantity
is handled, except that attributes can be "stacked" by setting multiple
values in an input form.
You cannot define a modifier name of I<code> or I<quantity>, as they
are already used. You must be sure that no fields in your forms
have digits appended to their names if the variable is the same name
as the attribute name you select, as the C<[modifier-name size]> variables
will be placed in the user session as the form variables size0, size1,
size2, etc.
You can use the C<[loop arg="item item item"]> list to reference multiple display
or selection fields for modifiers, or you can use the built-in
C<[PREFIX-accessories ...]> tags available in most Interchange list operations.
The modifier value can then be used to select data from an arbitrary database
for attribute selection and display.
Below is a fragment from a shopping basket display form which
shows a selectable size with "sticky" setting. Note that this
would always be contained within the C<[item_list]> C<[/item-list]>
> <SELECT NAME="[modifier-name size]">
> <OPTION [selected [modifier-name size] S]> S
> <OPTION [selected [modifier-name size] M]> M
> <OPTION [selected [modifier-name size] L]> L
> <OPTION [selected [modifier-name size] XL]> XL
It could just as easily be done with a radio button group combined
with the C<[checked ...]> tag.
Interchange will automatically generate the above select box
when the C<[accessories <code> size]> or C<[item-accessories size]>
tags are called. They have the syntax:
> [item_accessories attribute*, type*, field*, database*, name*, outboard*]
> [accessories code attribute*, type*, field*, database*, name*, outboard*]
=over 4
=item code
Not needed for item-accessories, this is the product code of the item to
=item attribute
The item attribute as specified in the UseModifier configuration
directive. Typical are C<size> or C<color>.
=item type
The action to be taken. One of:
> select Builds a dropdown <SELECT> menu for the attribute.
> NOTE: This is the default.
> multiple Builds a multiple dropdown <SELECT> menu for the
> attribute. The size is equal to the number of
> option choices.
> display Shows the label text for *only the selected option*.
> show Shows the option choices (no labels) for the option.
> radio Builds a radio box group for the item, with spaces
> separating the elements.
> radio nbsp Builds a radio box group for the item, with &nbsp;
> separating the elements.
> radio left n Builds a radio box group for the item, inside a
> table, with the checkbox on the left side. If "n"
> is present and is a digit from 2 to 9, it will align
> the options in that many columns.
> radio right n Builds a radio box group for the item, inside a
> table, with the checkbox on the right side. If "n"
> is present and is a digit from 2 to 9, it will align
> the options in that many columns.
> check Builds a checkbox group for the item, with spaces
> separating the elements.
> check nbsp Builds a checkbox group for the item, with &nbsp;
> separating the elements.
> check left n Builds a checkbox group for the item, inside a
> table, with the checkbox on the left side. If "n"
> is present and is a digit from 2 to 9, it will align
> the options in that many columns.
> check right n Builds a checkbox group for the item, inside a
> table, with the checkbox on the right side. If "n"
> is present and is a digit from 2 to 9, it will align
> the options in that many columns.
The default is 'select', which builds an HTML select form entry for
the attribute. Also recognized is 'multiple', which generates a
multiple-selection drop down list, 'show', which shows the list of
possible attributes, and 'display', which shows the label text for the
selected option only.
=item field
The database field name to be used to build the entry (usually a field
in the products database). Defaults to a field named the same as the
=item database
The database to find B<field> in, defaults to the first products file
where the item code is found.
=item name
Name of the form variable to use if a form is being built. Defaults to
mv_order_B<attribute> -- i.e. if the attribute is B<size>, the form
variable will be named B<mv_order_size>.
=item outboard
If calling the item-accessories tag, and you wish to select from an
outboard database, you can pass the key to use to find the accessory
When called with an attribute, the database is consulted and looks for
a comma-separated list of attribute options. They take the form:
> name=Label Text, name=Label Text*
The label text is optional -- if none is given, the B<name> will
be used.
If an asterisk is the last character of the label text, the item is
the default selection. If no default is specified, the first will be
the default. An example:
> [item_accessories color]
This will search the product database for a field named "color". If
an entry "beige=Almond, gold=Harvest Gold, White*, green=Avocado" is found,
a select box like this will be built:
> <SELECT NAME="mv_order_color">
> <OPTION VALUE="beige">Almond
> <OPTION VALUE="gold">Harvest Gold
> <OPTION VALUE="green">Avocado
In combination with the C<mv_order_item> and C<mv_order_quantity> variables
this can be used to allow entry of an attribute at time of order.
If used in an item list, and the user has changed the value, the generated
select box will automatically retain the current value the user has selected.
The value can then be displayed with C<[item-modifier size]> on the
order report, order receipt, or any other page containing an
H2: Product Discounts
Product discounts can be set upon display of any page. The discounts
apply only to the customer receiving them, and are of one of three types:
> 1. A discount for one particular item code (key is the item-code)
> 2. A discount applying to all item codes (key is ALL_ITEMS)
> 3. A discount for an individual line item (set the mv_discount attribute
> with embedded Perl)
> 4. A discount applied after all items are totaled
> (key is ENTIRE_ORDER)
The discounts are specified via a formula. The formula is scanned for
the variables $q and $s, which are substituted for with the item
I<quantity> and I<subtotal> respectively. The variable $s is saved between
iterations, so the discounts are cumulative. In the case of the item and
all items discount, the formula must evaluate to a new subtotal for all
items I<of that code> that are ordered. The discount for the entire
order is applied to the entire order, and would normally be a monetary
amount to subtract or a flat percentage discount.
Discounts are applied to the effective price of the product, including
any quantity discounts or price adjustments.
To apply a straight 20% discount to all items:
> [discount ALL_ITEMS] $s * .8 [/discount]
or with named attributes:
> [discount code=ALL_ITEMS] $s * .8 [/discount]
To take 25% off of only item 00-342:
> [discount 00-342] $s * .75 [/discount]
To subtract $5.00 from the customer's order:
> [discount ENTIRE_ORDER] $s - 5 [/discount]
To reset a discount, set it to the empty string:
> [discount ALL_ITEMS][/discount]
Perl code can be used to apply the discounts, and variables are
saved between items and are shared with the C<[calc]> tag. This
example gives 10% off if two items are ordered, with 5% more for
each additional up to a maximum of 30% discount:
> [calc]
> [item-list]
> $totalq{"[item-code]"} += [item-quantity];
> [/item-list]
> return '';
> [/calc]
> [item-list]
> [discount code="[item-code]"]
> return ($s) if $totalq{"[item-code]"} == 1;
> return ($s * .70) if $totalq{"[item-code]"} > 6;
> return ($s * ( 1 - 0.05 * $totalq{"[item-code]"} ));
> [/discount]
> [/item-list]
Here is an example of a special discount for item code 00-343 which prices
the I<second> one ordered at 1 cent:
> [discount 00-343]
> return $s if $q == 1;
> my $p = $s/$q;
> my $t = ($q - 1) * $p;
> $t .= 0.01;
> return $t;
> [/discount]
If you want to display the discount amount, use the C<[item-discount]> tag.
> [item-list]
> Discount for [item-code]: [item-discount]
> [/item-list]
Finally, if you want to display the discounted subtotal, you need to
use the C<[calc]> capability:
> [item-list]
> Discounted subtotal for [item-code]: [currency][calc]
> [item-price] * [item-quantity]
> [/calc][/currency]
> [/item-list]
H1: Taxing
Interchange allows taxing in a number of ways.
LI1: Simple salestax.asc table
The {{CMD[jump="icconfig.html#SalesTax"]SalesTax}} directive is
set to a form field or fields for user input, and those form fields
are used look up the tax rate in salestax.asc.
LI1: Fly tax
Another simple tax method. A series of Interchange Variable settings
are read to develop a salestax rate for one or a few localities, usually
a state in the US.
LI1: Salestax multi -- VAT taxing
The {{CMD[jump="icfoundation.html#country"]country}}
and {{CMD[jump="icfoundation.html#state"]state}} tables are used
to develop complex VAT or salestax rate calculations based on
country and state, possibly with different rates based on product
LI1: Levies -- multiple levels of tax
Using the {{CMD[jump="icconfig.html#Levies"]Levies}} setting
and the {{CMD[jump="icconfig.html#Levy"]Levy}} structure, any or all of
the above methods is used to implement one or more taxes.
H2: Sales Tax -- simple salestax.asc table
Interchange allows calculation of sales tax on a straight percentage basis,
with certain items allowed to be tax-exempt. To enable this feature,
the directive I<SalesTax> is initialized with the name of a field (or
fields) on the order form. Commonly, this is zipcode and/or state:
> SalesTax zip,state
This being done, Interchange assumes the presence of a file F<salestax.asc>,
which contains a database with the percentages. Each line of
F<salestax.asc> should be a code (again, usually a five-digit zip or
a two letter state) followed by a tab, then a percentage. Example:
!block example
45056 .0525
61821 .0725
61801 .075
IL .0625
OH .0525
VAT .15
WA .08
Based on the user's entry of information in the order form, Interchange
will look up (for our example SalesTax directive) first the zip, then
the state, and apply the percentage to the SUBTOTAL of the order. The
subtotal will include any taxable items, and will also include the
shipping cost if the state/zip is included in the I<TaxShipping> directive.
It will add the percentage, then make that available with the C<[salestax]>
tag for display on the order form. If no match is found, the entry
C<DEFAULT> is applied -- it is normally zero.
If business is being done on a national basis, it is now common to have
to collect sales tax for multiple states. If you are doing so, it is possible
to subscribe to a service which issues regular updates of the sales tax
percentages -- usually by quarterly or monthly subscription. Such a
database should be easily converted to Interchange format -- but some systems
are rather convoluted, and it will be well to check and see if the
program can export to a flat ASCII file format based on zip code.
If some items are not taxable, then you must set up a field in your
database which indicates that. You then place the B<name> of that field
in the I<NonTaxableField> directive. If the field for that item
evaluates true on a yes-no basis (i.e. is set to C<yes>, C<y>, 1, or the
like), sales tax will not be applied to the item. If it evaluates false,
it will be taxed.
If your state taxes shipping, use the I<TaxShipping> directive.
Utah and Nevada are known to tax shipping -- there may be others.
If you want to set a fixed tax for all orders, as might occur for VAT
in some countries, just set the I<SalesTax> directive to a value like
C<tax_code>, and define a variable in the user session to reflect the
proper entry in the C<salestax.asc> file. To set it to 15% with the
above C<salestax.asc> file, you would put in a form:
> <INPUT TYPE=hidden NAME=tax_code VALUE="VAT">
or to do it without submitting a form:
> [perl] $Values->{tax_code} = 'VAT'; return; [/perl]
H2: Fly tax
The {{CMD[jump="ictags.html#fly-tax"][fly-tax]}} tag is placed
in the DEFAULT setting of salestax.asc, and the variables
C<TAXAREA>, C<TAXRATE>, and C<TAXSHIPPING> are used to build
the rates.
A space-separated or comma-seperated list of states to apply
tax to. Not needed for anything in the calculation, it is used
to build the UI list of states to tax.
An Interchange accessory-list style of value, with the
!block example
where XX is the two-letter state code and N.NN is the tax rate
in percent. To apply a tax of 7.25% for Illinois and 5.5% for
Nevada, you would use:
IL=7.25, NV=5.5
A space- or comma-separated list of states where shipping is
taxed. For the above example, if Nevada taxed shipping and Illinois
did not, you would make TAXSHIPPING equal to "NV".
LI1: The Salestax Directive
To set the field that is used for the state code, you use the
standard Interchange {{CMD[jump="icconfig.html#SalesTax"]SalesTax}} directive. It would almost always
be set to C<state>.
H2: Salestax "multi" -- VAT taxing
If the SalesTax directive is set to "multi", then the type of
tax is read from the {{CMD[jump="icfoundation.html#country"]country}} table. To see the tax type in
force for the UK, you can place in a page:
!block example
[data table=country col=tax key="UK"].
.NOTE: We mention the "country" table above. In actual practice, most
everything is configurable for variable name and field name via
different Variable settings. They are:
!block example
MV_COUNTRY_TABLE Table for country info (default "country")
MV_COUNTRY_FIELD Form field determining country (default "country")
MV_COUNTRY_TAX_FIELD Table column for country-wide tax (default "tax")
MV_STATE_TABLE Table for state/province info (default "state")
MV_STATE_FIELD Form field determining state/province (default "state")
MV_STATE_TAX_FIELD Table column for state-wide tax (default "tax")
MV_TAX_TYPE_FIELD Table column enumerating tax types (default "tax_type")
MV_TAX_CATEGORY_FIELD Table column for product type (default tax_category)
Below, we refer to the tables, columns, and fields by their default names.
The first lookup is done in table C<country> based on the user input
of C<country> (i.e. C<[value country]>). The C<tax> field is read and one
of the following is done:
1. If no string is found, tax returns 0.
2. If string "simple:XX" is found, uses [fly-tax] with the area
specifed in XX.
3. If string "state" is found, does a re-lookup with
!block example
select tax from state where country = country and state = state
and value is applied as below.
4. If just digits are found, rate applied directly -- i.e. "0.05"
5. If N.NN% is found, applied as percentage.
6. If C<category = N.NN%, default = N.NN%> is found, the C<tax_category>
field in the {{CMD[jump="icfoundation.html#products"]products}} table is used to determine tax basis.
If no tax_category is found for the product, C<default> rate is used.
This product data
!block example
sku price tax_category
os28003 10.00 tools
os28004 20.00 food
with this country and state data:
!block example
code name tax
US U.S.A. state
JP Japan tools=10%, default=15%
code country state name tax
0001 US IL Illinois 6.5%
0002 US OH Ohio default = 5.5%, food = 1%
0003 US AZ Arizona
Will yield tax for one each of os28003 and os28004 of:
!block example
Japan $4.00
US/IL $1.95
US/OH $0.75
US/AZ $0.00
H2: Advanced Multi-level Order Pages
An unlimited number of order checking profiles can be defined with the
I<OrderProfile> directive, or by defining order profiles in scratch
variables. This allows a multi-level ordering process, with checking
for format and validity at every stage.
To custom-configure the error message, place it after the format check
Specifications take the form of an order page variable (like name
or address), followed by an equals sign and one of five check types:
=over 4
=item required
A non-blank value is required
=item mandatory
Must be non-blank, and must have been specified on this
form, not a saved value from a previous form
=item phone
The field must look like a phone number, by a very
loose specification allowing numbers from all countries
=item phone_us
Must have US phone number formatting, with area code
=item state
Must be a US state, including DC and Puerto Rico.
=item province
Must be a Canadian province or pre-1997 territory.
=item state_province
Must be a US state or Canadian province.
=item zip
Must have US postal code formatting, with optional ZIP+4.
Also called by the alias C<us_postcode>.
=item ca_postcode
Must have Canadian postal code formatting. Checks for a valid
first letter.
=item postcode
Must have Canadian or US postal code formatting.
=item true
Field begins with B<y>, B<1>, or B<t> (Yes, 1, or True) - not case sensitive
=item false
Field begins with B<n>, B<0>, or B<f> (No, 0, or False) - not case sensitive
=item email
Rudimentary email address check, must have an '@' sign,
a name, and a minimal domain
=item regex
One or more regular expressions (space-separated) to check against. To
check that all submissions of the "foo" variable have "bar" at the
beginning, do:
> foo=regex ^bar
You can add an error message by putting it in quotes at the end:
> foo=regex ^bar "You must have bar at the beginning of this"
You can require that the value B<not> match the regex by preceding the regex with a B<!> character (and no space afterwards):
> foo=regex !^bar "You may not have bar at the beginning!"
=item length
A range of lengths you want the input to be:
> foo=length 4-10
That will require C<foo> be from 4 to 10 characters long.
=item unique
Tests to see that the value would be a unique key in a table:
> foo=unique userdb Sorry, that username is already taken
=item filter
Runs the value through an Interchange filter and checks that the returned value is equal
to the original value.
> foo=filter entities Sorry, no HTML allowed
To check for all lower-case characters:
> foo=filter lower Sorry, no uppercase characters
Also, there are pragmas that can be used to change behavior:
=over 4
=item &charge
Perform a real-time charge operation. If set to any value but
"custom", it will use Interchange's CyberCash routines. To set to
something else, use the value "custom ROUTINE". The ROUTINE should
be a GlobalSub which will cause the charge operation to occur -- if
it returns non-blank, non-zero the profile will have succeeded. If
it returns 0 or undef or blank, the profile will return failure.
=item &credit_card
Checks the mv_credit_card_* variables for validity. If set to
"standard", it will use Interchange's C<encrypt_standard_cc> routines.
This destroys the CGI value of mv_credit_card_number -- if you don't
want that to happen (perhaps to save it for sending to CyberCash)
then add the word C<keep> on the end.
> # Checks credit card number and destroys number after encryption
> # The charge operation can never work
> &credit_card=standard
> &charge=custom authorizenet
> # Checks credit card number and keeps number after encryption
> # The charge operation can now work
> &credit_card=standard keep
> &charge=custom authorizenet
You can supply your own check routine with a GlobalSub:
> &credit_card=check_cc
The C<GlobalSub> check_cc will be used to check and encrypt the
credit card number, and its return value will be used to determine
profile success.
=item C<&>fail
Sets the mv_failpage value.
> &fail=page4
If the submit process succeeds, the user will be sent to the
page C<page4>.
=item C<&>fatal
Set to '&fatal=yes' if an error should generate
the error page.
=item C<&>final
Set to '&final=yes' if a successful check should cause the order to be placed.
=item C<&>update
Set to '&update=yes' if a successful check should cause the variable to be copied from the CGI space to the Values space. This is like [update values] except only
for that variable.
This is typically used when using a C<mv_form_profile> check so that
a failing check will not cause all values to be reset to their former
state upon returning to the form.
=item C<&>return
Causes profile processing to terminate with either a success
or failure depending on what follows. If it is non-blank and
non-zero, the profile succeeds.
> # Success :)
> &return 1
> # Failure :\
> &return 0
Will ignore the &fatal pragma, but &final is still in effect if set.
=item C<&>set
Set a user session variable to a value, i.e. C<&set=mv_email [value email]>.
This will not cause failure if blank or zero.
=item C<&>setcheck
Set a user session variable to a value, i.e. C<&set=mv_email [value
email]>. This B<will> cause failure if set to a blank or zero. It is
usually placed at the end after a &fatal pragma would have caused the
process to stop if there was an error -- can also be used to determine
pass/fail based on a derived value, as it will cause failure if it
evaluates to zero or a blank value.
=item C<&>success
Sets the mv_successpage value. Example:
> &success=page5
If the submit process succeeds, the user will be sent to the
page C<page5>.
As an added measure of control, the specification is evaluated for the
special Interchange tags to provide conditional setting of order
parameters. With the C<[perl]> C<[/perl]> capability, quite complex checks
can be done. Also, the name of the page to be displayed on an error can
be set in the C<mv_failpage> variable.
The following file specifies a simple check of formatted parameters:
> name=required You must give us your name.
> address=required Oops! No address.
> city=required
> state=required
> zip=required
> email=required
> phone_day=phone_us XXX-XXX-XXXX phone-number for US or Canada
> &fatal=yes
> email=email Email address missing the domain?
> &set=mv_email [value email]
> &set=mv_successpage ord/shipping
The profile above only performs the &set directives if all of the
previous checks have passed -- the &fatal=yes will stop processing after
the check of the email address if any of the previous checks failed.
If you want to place multiple order profiles in the same file,
separate them with __END__, which must be on a line by itself.
User-defined check routines can be defined in a GlobalSub:
> GlobalSub <<EOF
> sub set_up_extra_check {
> package Vend::Order;
> sub _pt_postcode {
> # $ref is to Vend::Session->{'values'} hash
> # $var is the passed name of the variable
> # $val is current value of checked variable
> my($ref, $var, $val) = @_;
> if ($ref->{country} =~ /^(PT|portugal)$/i) {
> return $val =~ /^\d\d\d\d$/ ?
> (1, $var, '') : (undef, $var, "not a Portugese postal code");
> }
> else {
> return (1, $var, '');
> }
> }
> }
> }
Now you can specify in an order profile:
> postcode=pt_postcode
Very elaborate checks are possible. There must be an underscore
preceding the routine name. The return value of the subroutine
should be a three-element array, consisting of:
^ the pass/fail ('1' or 'undef') status of the check;
+ the name of the variable which was checked;
+ a standard error message for the failure, in case a custom one has
not been specified in the order profile.
The latter two elements are used by the C<[error]> tag for on-screen
display of form errors. The checkout page of the Foundation demo includes
examples of this.
H2: Simple Order Report File
The simple order report file, "report", defines the layout of the order
report which gets mailed on the completion of the order. For example,
> Order Date: $date
> Name: $name
> Email address: $email
> Shipping address: $addr
> Town, State, Zip: $town, $state $zip
> Country: $country
Any input field from the order page can be included using the dollar
sign notation.
Interchange defines some values for use in the search form -- they begin
with C<mv_> and are automatically ignored.
H2: Fully-configurable Order Reports
You can specify a fully-configurable order report by setting the hidden
field "mv_order_report" to a legal Interchange page. This page will be
interpolated with all Interchange tags before sending by email. The order
number as set by backend ordering is in the variable mv_order_number,
and available for your use.
You could if you wish include HTML in the file, which will be interpreted
by many mailers, but you can choose to use standard ASCII format.
An example report is provided in the demo file <pages/ord/report.html>.
H2: Order Receipts
The file can of course be configured with all Interchange tags, and
will be interpolated for the ordered items before they are deleted from
the user session. You can set the default receipt with the C<receipt>
key in SpecialPage. If using order I<Route>s, as in the C<foundation> demo,
you set it with the C<receipt> key to C<Route>.
H2: The Order Counter
An order counter can be enabled if the I<OrderCounter> directive
is set to a file name. An incrementing count of all orders will be
kept and assigned as orders are placed. By default, the number
starts at 0, but you can edit the file and change the default
starting number at any time.
This capability is made possible by the File::CounterFile module,
available (as a part of the fine libwww modules) at the same place you
got Interchange. It is included with the distribution.
H2: Customer Input Fields
On the order (or shopping basket) page, by default order.html, you will
have a number of input fields allowing the customer to enter information
such as their name and address. You can add more fields simply by
putting more input elements on the order.html page, and the information
will automatically be included in the order report. Input elements
should be written in this way:
> <input type="text" name="town" value="[value town]" size=30>
Choose a name for this input field such as "email" for an email
address. Set the name attribute to the name you have chosen.
The value attribute specifies the default value to give the field when
the page is displayed. Because the customer may enter information on
the order page, return to browsing, and come back to the order page,
you want the default value to be what was entered the first time. This
is done with the C<[value var]> element, which returns the last value of an
input field. Thus,
> value="[value name]"
will evaluate to the name entered on the previous order screen, such
> value="Jane Smith"
which will be displayed by the browser.
The size attributes specifies how many characters wide the input field
should be on the browser. You do not need to set this to fit the
longest possible value since the browser will scroll the field, but
you should set it large enough to be comfortable for the customer.
N:Copyright 2002-2004 Interchange Development Group. Copyright 2001-2002 Red Hat, Inc. Freely redistributable under terms of the GNU General Public License.