<%@ Language=VBScript %>
<%
'*************************************************************************
' DO NOT MODIFY THIS SCRIPT IF YOU WANT UPDATES TO WORK!
' Function : Modify Store General Settings - Help
' Product : CandyPress Store Frontend
' Version : 2.5
' Modified : February 2004
' Copyright: Copyright (C) 2004 CandyPress.Com
' See "license.txt" for this product for details regarding
' licensing, usage, disclaimers, distribution and general
' copyright requirements. If you don't have a copy of this
' file, you may request one at webmaster@candypress.com
'*************************************************************************
Option explicit
Response.Buffer = true
const adminLevel = 0
'Variables
dim helpField
'*************************************************************************
%>
Store Configuration - Help
Store Configuration - Help
Close Window
<%
'Determine which field we are showing help for
helpField = trim(Request.QueryString("helpField"))
'Display Help Field Name
%>
NAME: <%=helpField%>
DESCRIPTION:
<%
'Display Help text
select case lCase(helpField)
case "urlnonssl"
%>
Full non-SSL (ie. non-secure) URL to your store's "scripts"
folder. This value should start with the characters "http://"
and end with "/scripts/".
EXAMPLE:
http://www.myServer.com/CandyPress/scripts/
<%
case "urlssl"
%>
Full SSL (ie. secure) URL to your store's "scripts" folder.
Typically, this value would start with the characters "https://"
and end with "/scripts/".
EXAMPLE:
https://www.myServer.com/CandyPress/scripts/
Note : If you simply want to test the
store, or you don't have SSL yet, you can enter the same
value you entered into the non-SSL field. The store would
still be fully functional, but the checkout process will not
be secure.
<%
case "pdownloaddir"
%>
Location of you Software Download Directory RELATIVE to the
"scripts" folder. If your store will sell items that are
downloadable from your web site, you must enter the path to the
folder in which the downloadable items will be stored into this
field. If you don't plan on selling downloadable items, you can
simply set this value to "../". The location must start with "../"
and end with "/".
EXAMPLE:
../Downloads/
<%
case "pimagesdir"
%>
Location of your Product Images Directory RELATIVE to the "scripts"
folder. The location must start with "../" and end with "/".
EXAMPLE:
../ProdImages/
<%
case "mailcomp"
%>
This tells the software what type of email component you will be
using to send email from your store. Check with your web hosting
company if you don't know what email component(s) are available
to you. We provide for several of the most popular components.
<%
case "psmtpserver"
%>
This is the address of your SMTP server.
EXAMPLE:
mail.myServer.com
<%
case "pemailsales"
%>
This is the email address of the person or department that will
be responsible for sales related queries.
EXAMPLE:
sales@myServer.com
<%
case "msxmlprogid"
%>
This is the program ID of the MS XML HTTP component
you have at your disposal.
NB : Only change if you
are experiencing problems with functions that require
MSXML, such as realtime shipping rates, PayPal
IPN, etc.
EXAMPLE:
MSXML2.ServerXMLHTTP
MSXML2.ServerXMLHTTP.4.0
MSXML2.ServerXMLHTTP.3.0
<%
case "xmldomprogid"
%>
This is the program ID of the MS XML DOM component
you have at your disposal.
NB : Only change if you
are experiencing problems with functions that require
MSXML, such as realtime shipping rates, PayPal
IPN, etc.
EXAMPLE:
Microsoft.XMLDOM
<%
case "pemailadmin"
%>
This is the email address of the
person or department which will be responsible for technical issues
related to your store.
EXAMPLE:
webmaster@myServer.com
<%
case "pcompany"
%>
The name of your store or company. This value is diplayed in
various places in your store.
EXAMPLE:
Madison Shoe Store Inc.
<%
case "pcompanyaddr"
%>
Your company's address.
Maximum number of characters allowed is 250. Enter address info
on seperate lines in the text box. Try to limit the number of
address lines to no more than 5 or 6 to ensure proper display
on invoices etc.
<%
case "pcatalogonly"
%>
Sets the store to run in "Catalog" mode.
This means that the customer will be able to browse
your store, but won't be able to add any of the products to a
shopping cart.
<%
case "prodviewlayout"
%>
Selects the type of layout to use when displaying the product's
details.
<%
case "listviewlayout"
%>
Selects the type of layout to use on the product list page.
The Extended layout is the same as the Classic layout,
except for the additional display of Stock Levels, Ratings, and Free
Shipping messages. Both layouts display one product per row.
The 2, 3 and 4 Column layout arranges the products in a grid.
When using this layout, keep in mind the setting for maximum number
of products per page. It is a good idea to enter a number
that is divisible by the number of columns to ensure that there are
no empty spaces on each page. Also, it will be best if all the
product thumbnail images are the same height and width to
ensure a uniform display.
<%
case "hideaddonprodlist"
%>
This will always hide the "Add" button on the product list pages.
<%
case "homeviewlayout"
%>
Selects the type of layout to use on the home page. The
"Extended" layout is the same as the "Classic" layout, except for
the additional display of Stock Levels, Free Shipping, List Price
and Savings.
<%
case "homeviewrandom"
%>
Determines the number of "Featured" products that will randomly be
displayed on the home page.
If the number entered is greater than the total number of "Featured"
products in the database, all the "Featured" products will be displayed
but the products will be shown in random sort order.
If the number entered is -1 or 0, all "Featured" products in the database
will be displayed and sorted by the sort field for the product.
Note that activating this feature may slightly decrease the load time
for the home page.
<%
case "categorylayout"
%>
The Multi-Level layout will show both parent categories and sub-categories
in a hierarchial "threaded" layout on the same page. This method is more
resource intensive and is better suited for smaller catalogs.
The Single-Level layout will only show one level of categories at a
time. When a customer clicks on a category, they will be shown the next
level of categories. The customer will therefore "drill down" the
category tree. This method is less resource intensive is better suited for
larger catalogs.
<%
case "shipdisplaytype"
%>
Selects the type of layout to use when displaying shipping rates
for the order.
<%
case "allowshipaddr"
%>
If set to Yes, the customer will be able to enter a shipping
address that is different from their billing address. If set to
No, the customer will not have the opportunity to enter a seperate
shipping address, and the system will assume that the shipping
address is the same as the billing address.
<%
case "taxonshipping"
%>
Determines if the total shipping cost will be included when taxes
are calculated for the order.
<%
case "handlingfeeamt"
%>
Use this setting to add a Handling Fee to orders. The handling
fee will apply to all orders where the total shipping weight is
greater than 0.
<%
case "handlingfeetax"
%>
If a handling fee is charged, this setting will determine if the
fee is taxable or not.
<%
case "taxbillorship"
%>
Determines if taxes for the order must be calculated based on the
Billing or Shipping address for the order. Note : If no shipping
address was entered, the billing and shipping address is the same.
<%
case "phidepricingzero"
%>
Hides all pricing information
on Product List and Detail pages, but only if the price of the product
is 0.00 (zero), otherwise show prices. This setting is usefull if you
want to carry products where the entire product price is made up of
options. This way you can enter a product price of '0.00', and link
'required' options with a price value to that product.
<%
case "phtmlarea"
%>
The HTMLarea component allows you to edit the contents of a field
in WYSIWIG format. In other words, you don't have to know any HTML
to create something visually appealing. For example, you can edit
your product description using the HTMLarea editor and add different
fonts, colors, etc. using the built-in editor buttons. The HTMLarea
component requires JavaScript to be enabled and IE 5.5 or later
browsers.
Note : The HTMLarea component is a freeware component created by
InterActiveTools.Com.
It is included with the CandyPress Store Frontend download.
<%
case "pshowstockview"
%>
If set to "Yes", the system will display "In Stock" or "Out of
Stock" messages on the product list and detail pages if required.
<%
case "phideaddstocklevel"
%>
The product list and
product detail pages will check the product's stock level against
the value you enter into this field. If the product's stock level
is at or below the level you specify, the 'Add' buttons will
automatically be hidden, and an "Out of Stock" message will be
displayed. To disable stock levels checking, enter a "-1" into
this field. This will result in the product always being displayed
as "In Stock" regardless of actual stock levels.
<%
case "pemailstocklevel"
%>
When a product's stock level is updated, the system will check to
see if the new stock level is at or below the number you specify
in this field. If it is, an email warning will be sent. To disable
this feature, enter -1 into this field.
<%
case "statupdpending"
%>
Normally, an item's stock level is reduced when the order status
changes to "Paid", "Complete" or "Shipped". In addition to these,
you may specify if the item's stock level must be reduced when the
order status changes to "Pending". This normally happens when the
order is saved, and before payment is made.
<%
case "pmaxcartqty"
%>
Maximum number of items (quantity) per Order.
<%
case "pmaxitemqty"
%>
Maximum number of items per Product per Order.
<%
case "pmincartamount"
%>
Minimum total purchase
price per Order BEFORE Tax and Shipping. Note : If you offer free
items (free downloads, brochures, etc.) there is a possibility that
you can have an order where the total is 0.00. Setting
the minimum order amount to a value greater than 0.00 will
disallow such orders.
<%
case "pmaxitemsperpage"
%>
The maximum number of Items you want
to display, per page, on the Product Search/View pages.
<%
case "porderprefix"
%>
Prefix to be displayed as part of the Order Number throughout
the store.
<%
case "pcurrencysign"
%>
Currency symbol for your Store.
EXAMPLE:
$, CAN$, £
<%
case "defaultcountrycode"
%>
Default Country Code for the store. This setting is mainly used
on the Customer Information page during checkout. The country
code must correspond to the country code for that country in the
database.
<%
case "pstorelcid"
%>
Locale Identifier (LCID) for the store. An LCID is a decimal
numeric value that tells the web server what format to use when it
works with dates, numbers, etc. For example, the default locale
used by this software for it's internal date functions is '1033'
(US English). This can not be changed. You can however, override
the external (displayed) date format. We listed a few LCID
examples below. The entire list can be found at
DevGuru.Com.
| LCID |
Description |
Date |
Number |
| 3081 |
English - Australia |
17/04/2002 |
1,350.15 |
| 4105 |
English - Canada |
17/04/2002 |
1,350.15 |
| 2057 |
English - United Kingdom |
17/04/2002 |
1,350.15 |
| 1033 |
English - USA |
4/17/2002 |
1,350.15 |
| 1036 |
French - Standard |
17/04/2002 |
1 350,15 |
| 1031 |
German - Standard |
17.04.2002 |
1.350,15 |
| 1040 |
Italian - Standard |
17/04/2002 |
1.350,15 |
| 1034 |
Spanish - Standard |
17/04/2002 |
1.350,15 |
<%
case "timeoffset"
%>
You can adjust the time offset if your server is located in a
different time zone than you are. A value of 0 will effectively
mean that the server time will always be used. You can subtract
or add 12 hours from the server time.
<%
case "pemailfriendsec"
%>
If you set this value to "Yes", the
customer will no longer be able to modify the "Email To Friend"
message body. If set to "No", the customer will be able to enter
their own message in the message body. The problem with allowing
anyone to enter their own message, is that they could possibly
use the script to send personal email messages to others
"anonymously".
<%
case "usesecuredownload"
%>
If you use this feature, the download file will be streamed to
the client (ie. web browser) without the customer being able to
see the URL of the file. Otherwise, it will use normal http for
the download.
Streaming downloads provide a bit of extra security, but
it is also much more resource intensive. The download script will
run for the duration of the download which, for large
files, can be several hours depending on the speed of the customer's
internet connection. Some browsers may also not support this functionality. If
you are experiencing problems with streaming downloads, you will
have to disable this function to use HTTP downloads instead.
HTTP downloads offer a bit less security, but it is much less demanding
on your server's resources. HTTP downloads are handled directly
between the customer's web browser and the web server, so no script
is required to run for the duration of the download.
<%
case "pmaxdownloadhours"
%>
This setting specifies the
maximum number of hours you will allow a customer to download
software from your store after the FIRST download has taken place.
Be carefull to allow enough time as some customers may need to try
several times due to bad connections, etc. Enter a "0" if you
want to disable this feature (ie. "0" allows for unlimited download
hours).
<%
case "pmaxdownloadcount"
%>
This setting specifies the
maximum number of times you will allow a customer to download
software from your store. Enter a "0" if you want to disable this
feature (ie. "0" allows for unlimited download times).
<%
case "pprodthumbs"
%>
If set to "Yes", the system will display a thumbnail image and the
long description of each related product in the product detail view.
If no thumbnail image is available, none will be displayed.
Note : This option works best if all your thumbnails are the same
width and height.
<%
case "pmailin"
%>
Allow/Disallow Mail-In payments such as
Checks, Money Orders, Cash, etc.
<%
case "paycallin"
%>
Allow/Disallow Call-In payments where
the customers phones you, or you phone the
customer to gather payment information.
<%
case "payfaxin"
%>
Allow/Disallow Fax-In payments where the
customer faxes their payment information to you.
<%
case "paycod"
%>
Allow/Disallow COD payments.
<%
case "ppaypal"
%>
Allow/Disallow payments via PayPal.
If enabled, the customer would be directed to PayPal's web site
for payment.
<%
case "paypalmemberid"
%>
If you accept PayPal payments
on your site, specify your PayPal Membership ID (this is usually in
the form of an email address).
<%
case "paypalcurrcode"
%>
PayPal accepts payments in several different currencies. Your
products should be priced in the same currency as the one
you select here. In other words, if you select US Dollar as
your PayPal currency, your products should also be priced in
US Dollars in your store.
Note : This feature will only be available during mid November,
2002. Please check the PayPal web site to ensure that this
feature is available before you use it. Until PayPal implements
the feature, all payments will be in US Dollars only.
<%
case "twocheckout"
%>
Allow/Disallow payments via 2CheckOut.
If enabled, the customer will be directed to 2CheckOut.Com's web
site for payment.
<%
case "twocheckoutsid"
%>
If you accept 2CheckOut payments
on your site, specify your 2CheckOut Account Number.
<%
case "twocheckoutmd5"
%>
If you accept 2CheckOut payments
on your site, and want to automatically update the order's status,
then you must enter your MD5 "Secret Word" here. Please
note that this is NOT the same as the password that you use to
logon to 2CheckOut.Com's website. At the time of writing, this
value is found and modified by logging on to your 2CheckOut.Com
account, and clicking on "Account Details -> Return". At the
very bottom of the page, you will see a box named "Secret Word".
This is the value you must enter.
<%
case "pcreditcard"
%>
Allow/Disallow Credit Card payments.
If enabled, the customer will enter their Credit Card information
in a form on your store's web site, and the information will be
saved in your database for processing later on. Note
that you would typically need to have some form of Merchant Account
with a bank to use this form of payment. See below for more settings
related to credit card payments.
<%
case "pcctype"
%>
If you are able to
directly accept and process transactions for Credit Cards, enter
the list of Credit Cards you are able to accept, seperated by commas,
into this field.
EXAMPLE:
Visa,MasterCard,American Express
<%
case "pauthnetfrontend"
%>
Allow/Disallow Authorize.Net payments.
If enabled, the customer will be redirected to Authorize.Net's web
site for payment (SIM), or the payment info will be entered on a
form on your web site and sent silently to Authorize.Net for
validation and authorization (AIM).
<%
case "pauthnettype"
%>
The SIM method will redirect the customer to a payment screen located
on the Authorize.Net servers. After completing the payment form, the
customer is redirected back to your web site.
The AIM method will display a payment form on your web site. After
completing the payment form, the Authorize.Net payment servers will
be called silently to authorize and process the payment. In other
words, the customer never actually leave your web site. This method
requires the MS XML components to be installed on your server.
<%
case "pauthnet"
%>
If you use Offline Credit Card payments to collect credit
card details from the customer, you can use your Authorize.Net
account to authorize the payment via your store's Admin area. This
saves you from manually entering the offline credit card info into
your Authorize.Net virtual terminal screen.
Note : If you use Authorize.Net in your Storefront then you would
typically not need this function. That is because the payment will
be authorized and processed during the checkout process.
<%
case "authnetlogin"
%>
The Login given to you when you opened your Authorize.Net account.
<%
case "authnettxkey"
%>
The transaction key is used to create a secure fingerprint for each
transaction processed through Authorize.Net.
<%
case "authnetcurrcode"
%>
The Authorize.Net Currency Code in which your Credit Card
transactions must settle (eg. "USD"). Contact Authorize.Net
for assistance if you are not sure what the Currency Code for
your account is.
<%
case "paydefault"
%>
This will be the default payment type
when the customer checks out (ie. it will be pre-selected in the
drop down list of payment types available at your store).
Naturally, the default payment type should be one that you
support in your store.
<%
case "paymsgmailin"
%>
The description that will be displayed
for "Mail In" payment types (eg. "Mail-In").
<%
case "paymsgcallin"
%>
The description that will be displayed
for "Call In" payment types (eg. "Call-In").
<%
case "paymsgfaxin"
%>
The description that will be displayed
for "Fax In" payment types (eg. "Fax-In").
<%
case "paymsgcod"
%>
The description that will be displayed
for "COD" payment types (eg. "COD").
<%
case "paymsgcreditcard"
%>
The description that will be displayed
for "Credit Card" payment types (eg. "Credit Card").
<%
case "paymsgpaypal"
%>
The description that will be displayed
for "PayPal" payment types (eg. "PayPal").
<%
case "paymsgtwocheckout"
%>
The description that will be displayed
for "2CheckOut" payment types (eg. "2CheckOut").
<%
case "paymsgauthnet"
%>
The description that will be displayed
for "AuthorizeNet" payment types (eg. "Authorize.Net").
<%
case "paymsgother"
%>
The description that will be displayed
when a Payment Type could not be determined or if a Payment Type was
not entered (eg. "Unknown").
<%
case "paymsgnotreq"
%>
This special Payment Type description
deals with Orders that are free to the customer (eg. "Payment not
Required"). This could happen, for instance, when you provide for
free downloads of software items. It is likely that you would then
have an order where the total is 0.00.
<%
case "paycustom"
%>
Allow/Disallow custom payment routine.
Before you enable this payment method, you will have
to add the necessary code in the custom payment user exit files
to send the appropriate order information to the payment gateway,
and receive the payment status from the gateway. See the
"readme.htm" file, and the notes and examples inside
"_INCpayOut_.asp" and "_INCpayIn_.asp" for more details.
Some ASP knowledge will be required.
<%
case "paymsgcustom"
%>
The description that will be displayed
for "Custom" payment types (eg. "Custom Payment").
<%
case "feemailin","feecallin","feefaxin","feecod","feeoffcc","feepaypal","fee2co","feeauthnet","feecustom"
%>
Specify a fixed fee that will be added to the order if the customer selects this payment method.
<%
case else
%>
Invalid help field was passed...
<%
end select
%>
Close Window