Here are your paths to the common server resources that CGI scripts often require:

Look at the window in your FTP or Telnet client to see whether your site resides on /home/ or /home2/.

Put your cgi-bin scripts in the www subdirectory named "cgi-bin". If you have given full POP/FTP/Telnet accounts to other people, each of them will have their own separate cgi-bin inside the main cgi-bin. When they login with their username and password, they will only have access to their own cgi-bin.

Below are solutions to some of the more common CGI script problems, in question and answer format.

When I activate my CGI program, I get back a page that says "Internal Server Error. The server encountered an internal error or misconfiguration and was unable to complete your request."

This is generally caused by a problem within the script. Log in via Telnet and test your script in local mode to get a better idea of what the problem is. To do this, go into the directory in which your script is located, then execute the script. To execute the script, you can do it by two ways:

1. Type "perl myscript.pl" (Perl being the language interpreter in this case).
2. Or simply type "myscript.pl" alone, that will work if the first line is well written to indicate the location of Perl.

In order for your SSI to work, the web page must have either .sht or .shtml extensions. Sample SSI:
<!--#exec cgi="/cgi-bin/count.cgi"-->
Please note that the url must be relative as shown above. Following would not work:
<!--#exec.cgi="http://yourdomain.com/cgi-bin/count.cgi"-->
All directives to the server are formatted as SGML comments within the document. This is in case the document should ever find itself in the client's hands unparsed. Each directive has the following format:
<!--#command tag1="value1" tag2="value2" -->
Each command takes different arguments, most only accept one tag at a time. Here is a breakdown of the commands and their associated tags:

• config
  The config directive controls various aspects of the file parsing. There are two valid tags:
  • errmsg controls what message is sent back to the client if an error includes while parsing the document. When an error occurs, it is logged in the server's error log.
  • timefmt gives the server a new format to use when providing dates. This is a string compatible with the strftime library call under most versions of UNIX.
  • sizefmt determines the formatting to be used when displaying the size of a file. Valid choices are bytes, for a formatted byte count (formatted as 1,234,567), or abbrev for an abbreviated version displaying the number of kilobytes or megabytes the file occupies.
• include
  include will insert the text of a document into the parsed document. Any included file is subject to the usual access control. This command accepts two tags:
  • virtual gives a virtual path to a document on the server. You must access a normal file this way, you cannot access a CGI script in this fashion. You can, however, access another parsed document.
  • file gives a pathname relative to the current directory. ../ cannot be used in this pathname, nor can absolute paths be used. As above, you can send other parsed documents, but you cannot send CGI scripts.
• echo prints the value of one of the include variables (defined below). Any dates are printed subject to the currently configured timefmt. The only valid tag to this command is var, whose value is the name of the variable you wish to echo.
• fsize prints the size of the specified file. Valid tags are the same as with the include command. The resulting format of this command is subject to the sizefmt parameter to the config command.
• flastmod prints the last modification date of the specified file, subject to the formatting preference given by the timefmt parameter to config. Valid tags are the same as with the include command.
• exec executes a given shell command or CGI script. It must be activated to be used. Valid tags are:
  • cmd will execute the given string using /bin/sh. All of the variables defined below are defined, and can be used in the command.
  • cgi will execute the given virtual path to a CGI script and include its output. The server does not perform error checking to make sure your script didn't output horrible things like a GIF, so be careful. It will, however, interpret any URL Location: header and translate it into an HTML anchor.

• DOCUMENT_NAME: The current filename.
• DOCUMENT_URI: The virtual path to this document (such as /docs/tutorials/foo.shtml).
• QUERY_STRING_UNESCAPED: The unescaped version of any search query the client sent, with all shell-special characters escaped with \.
• DATE_LOCAL: The current date, local time zone. Subject to the timefmt parameter to the config command.
• DATE_GMT: Same as DATE_LOCAL but in Greenwich mean time.
• LAST_MODIFIED: The last modification date of the current document. Subject to timefmt like the others.

MajorCool is a web-based interface to Majordomo allowing users to add and delete themselves from lists and manage lists that they own.

To access this program please enter http://domain.com/cgi-bin/majorcool into your browser.

Should you require help using the program please hit the "Help" button at the bottom of the main page. The program is pretty self-explanatory with just 3 buttons at the top:

1. BROWSE-
   You can search for lists that contain a certain email address or contain a specific string in their names. You can also get info on any list such as the owner's email address, the info file that is sent to new subscribers, etc. You can even see the entire list of subscribers for each list. All of this part is completely public, you don't need any password.
2. MODIFY-
   Here is where a list owner can enter their admin password to change anything about the list: add or delete subscribers, change the config file, change the description and info file associated with the list, etc. However they cannot delete the list entirely, or create new lists, or rename any lists.
3. PREFS-
   This is no big deal, just controls the onscreen display of MajorCool such as changing the layout of the features.

First to view the current version of PHP which is installed on your domain or to see the most common settings please direct your browser to http://www.youractualdomain.com/phpinfo.php

Create a file named hello.php and in it put the following lines:

<html><head><title>PHP Test</title></head>
<body><?php echo "Hello World<p>"; ?></body></html>

The colours you see are just a visual aid to make it easier to see the PHP tags and the different parts of a PHP expression. Note also that this is not like a CGI script. The file does not need to be executable or special in any way. Think of it as a normal HTML file which happens to have a set of special tags available to you that do a lot of interesting things.

This program is extremely simple and you really didn't need to use PHP to create a page like this. All it does is display: Hello World

If you tried this example and it didn't output anything, chances are that the server you are on does not have PHP enabled. Ask your administrator to enable it for you.

The point of the example is to show the special PHP tag format. In this example we used . You may jump in and out of PHP mode in an HTML file like this all you want.

Something Useful

Let's do something a bit more useful now. We are going to check what sort of browser the person viewing the page is using. In order to do that we check the user agent string that the browser sends as part of its request. This information is stored in a variable. Variables always start with a dollar-sign in PHP. The variable we are interested in is $HTTP_USER_AGENT. To display this variable we can simply do:

<?php echo $HTTP_USER_AGENT; ?>

For the browser that you are using right now to view this page, this displays:

Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; DigExt)

There are many other variables that are automatically set by your web server. You can get a complete list of them by creating a file that looks like this:

<?php phpinfo(); ?> Then load up this file in your browser and you will see a page full of information about PHP along with a list of all the variables available to you.

You can put multiple PHP statements inside a PHP tag and create little blocks of code that do more than just a single echo. For example, if we wanted to check for Internet Explorer we could do something like this:

<?php
if(strstr($HTTP_USER_AGENT,"MSIE")) {
echo "You are using Internet Explorer<br>";
}
?>

Here we introduce a couple of new concepts. We have an "if" statement. If you are familiar with the basic syntax used by the C language this should look logical to you. If you don't know enough C or some other language where the syntax used above is used, you should probably pick up any introductory C book and read the first couple of chapters. All the tricky string and memory manipulation issues you have to deal with in C have been eliminated in PHP, but the basic syntax remains.

The second concept we introduced was the strstr() function call. strstr() is a function built into PHP which searches a string for another string. In this case we are looking for "MSIE" inside $HTTP_USER_AGENT. If the string is found the function returns true and if it isn't, it returns false. If it returns true the following statement is executed.

We can take this a step further and show how you can jump in and out of PHP mode even in the middle of a PHP block:

<?php
if(strstr($HTTP_USER_AGENT,"MSIE")) {
?>
<center><b>You are using Internet Explorer</b></center>
<?
} else {
?>
<center><b>You are not using Internet Explorer</b></center>
}
?>

Instead of using a PHP echo statement to output something, we jumped out of PHP mode and just sent straight HTML. The important and powerful point to note here is that the logical flow of the script remain intact. Only one of the HTML blocks will end up getting sent to the viewer. Running this script right now results in:

You are using Internet Explorer

Dealing with Forms

One of the most powerful features of PHP is the way it handles HTML forms. The basic concept that is important to understand is that any form element in a form will automatically result in a variable with the same name as the element being created on the target page. This probably sounds confusing, so here is a simple example. Assume you have a page with a form like this on it:

<form action="action.php" method="post">
Your name: <input type="text" name="name">
You age: <input type="text" name="age">
<input type="submit"></form>

There is nothing special about this form. It is a straight HTML form with no special tags of any kind. When the user fills in this form and hits the submit button, the action.php page is called. In this file you would have something like this:

Hi <?php echo $name; ?>.
You are <?php echo $age; ?> years old.

It should be obvious what this does. There is nothing more to it. The $name and $age variables are automatically set for you by PHP.

The script is one from Matt's Script Archive which we have installed and preconfigured for your domain. FormMail is a generic www form to e-mail gateway, which will parse the results of any form and send them to the specified user. This script has many formatting and operational options, most of which can be specified through the form, meaning you don't need any programming knowledge or multiple scripts for multiple forms. This also makes FormMail the perfect system-wise solution for allowing users form-based user feedback capabilities without the risks of allowing freedom of CGI access.
There is only one form field that you must have in your form, for FormMail to work correctly. This is the recipient field. Other hidden configuration fields can also be used to enhance the operation of FormMail on your site. The action of your form needs to point towards this script (obviously), and the method must be POST in capital letters.
Here's an example of the form fields to put in your form:
<FORM METHOD=POST ACTION="http://yourdomain.com/cgi-bin/formmail.cgi">
<input type=hidden name="recipient" value="whoever@yourdomain.com">
<input type=hidden name="subject" value="Order">
<input type=hidden name="return_link_url" value="http://yourdomain.com/">
<input type=hidden name="return_link_title" value="Back to Main Page">

The following are descriptions and proper syntax for fields you can use with FormMail.
Recipient Field
Description: This form field allows you to specify to whom you wish for your form results to be mailed. Most likely you will want to configure this option as a hidden form field with a value equal to that of your email address.

Syntax: <input type=hidden name="recipient" value="email@yourdomain.com">

Subject Field
Description: The subject field will allow you to specify the subject that you wish to appear in the email that is sent to you after this form has been filled out. If you do not have this option turned on, then the script will default to a message subject: "WWW Form Submission".

Syntax: If you wish to choose what the subject is: <input type=hidden name="subject" value="Your Subject">

To allow the user to choose a subject: <input type=text name="subject">

Email Field
Description: This form field will allow the user to specify their return email address. If you want to be able to return e-mail to your user, I strongly suggest that you include this form field and allow them to fill it in. This will be put into the From: field of the message you receive. If you want to require an email address with valid syntax, add this field name to the 'required' field.

Syntax: <input type=text name="email">

Realname Field
Description: The realname form field will allow the user to input their real name. This field is useful for identification purposes and will also be put into the From: line of your message header.

Syntax: <input type=text name="realname">

Redirect Field
Description: If you wish to redirect the user to a different URL, rather than having them see the default response to the fill-out form, you can use this hidden variable to send them to a pre-made HTML page.

Syntax: To choose the URL they will end up at:
<input type=hidden name="redirect" value="http://yourdomain.com/to/file.html">

To allow them to specify a URL they wish to travel to once the form is filled out:
<input type=text name="redirect">

Required Field
Description: You can require certain fields in your form to be filled in before the user can successfully submit the form. Simply place all field names that you want to be mandatory into this field, separated by commas. If the required fields are not filled in, the user will be notified of what they need to fill in, and a link back to the form they just submitted will be provided.
To use a customized error page, see 'missing_fields_redirect'

Syntax: If you want to require that they fill in the email and phone fields in your form, so that you can reach them once you have received the mail, use the syntax like:
<input type=hidden name="required" value="email,phone">

Env_report Field
Description: Allows you to have Environment variables included in the email message you receive after a user has filled out your form. Useful if you wish to know what browser they were using, what domain they were coming from or any other attributes associated with environment variables. The following is a short list of valid environment variables that might be useful:
REMOTE_HOST - Sends the hostname making the request.
REMOTE_ADDR - Sends the IP address of the remote host.
HTTP_USER_AGENT - The browser the client is using. (Note: In our case, both REMOTE_HOST and REMOTE_ADDR are the same, since our servers don't do the reverse DNS lookup needed to generate the true REMOTE_HOST string).

Syntax: If you wanted to find all the above variables, you would put the following into your form:
<input type=hidden name="env_report" value="REMOTE_HOST,REMOTE_ADDR,HTTP_USER_AGENT">

Sort Field
Description: This field allows you to choose the order in which you wish for your variables to appear in the email form that FormMail generates. You can choose to have the field sorted alphabetically or specify a set order in which you want the fields to appear in your mail message. By leaving this field out, the order will simply default to the order in which the browsers send the information to the script (which is usually the exact same order as they appeared in the form). When sorting by a set order of fields, you should include the phrase "order:" as the first part of your value for the sort field, and then follow that with the field names you want to be listed in the email message, separated by commas.

Syntax: To sort alphabetically:
<input type=hidden name="sort" value="alphabetic">

To sort by a set field order:
<input type=hidden name="sort" value="order:name1,name2,etc...">

Print_config Field
Description: print_config allows you to specify which of the config variables you would like to have printed in your e-mail message. By default, no config fields are printed to your email. This is because the important form fields, like email, subject, etc. are included in the header of the message. However some users have asked for this option so they can have these fields printed in the body of the message. The config fields that you wish to have printed should be in the value attribute of your input tag separated by commas.

Syntax: If you want to print the email and subject fields in the body of your message, you would place the following form tag:
<input type=hidden name="print config" value="email, subject">

Print_blank_fields Field
Description: print_blank_fields allows you to request that all form fields are printed in the return HTML, regardless of whether or not they were filled in. FormMail defaults to turning this off, so that unused form fields aren't emailed.

Syntax: <input type=hidden name="print_blank_fields" value="1">

Title Field
Description: This form field allows you to specify the title and header that will appear on the resulting page if you do not specify a redirect URL.

Syntax: If you wanted a title of 'Feedback Form Results':

<input type=hidden name="title" value="Feedback Form Results">

Return_link_url Field
Description: This field allows you to specify a URL that will appear, as return_link_title, on the following report page. This field will not be used if you have the redirect field set, but it is useful if you allow the user to receive the report on the following page, but want to offer them a way to get back to your main page.

Syntax: <input type=hidden name="return_link_url" value="http://yourdomain.com/index.htm">

Return_link_title
Description: This is the title that will be used to link the user back to the page you specify with return_link_url. The two fields will be shown on the resulting form page as:
Back to Main Page

Syntax:<input type=hidden name="return_link_title" value="Back to Main Page">

Guestbook allows you to set up your own comments page. From there, visitors can add entries to your guestbook and they will be displayed with the most recent at the top and scrolling down, or vice versa. Other options include the ability to limit HTML in the entry, link to e-mail address with mailto tag, use a log to log entries, redirect to a different page after signing, emailing whenever a new entry is added, and much more.
Guestbook is already set up for use on your server. You can simply use the following URL to access it: http://yourdomain.com/Guestbook/guestbook.html
If you want to change any of the configuration options, locate the guestbook.cgi file in your Guestbook directory (inside your www directory). Download it to your hard drive in ASCII mode, and save it somewhere safe. Create a copy of the file and give it the same name, then edit the options as specified below. Keep your backup of the original guestbook.cgi in case you run into problems.

Option 1: $mail
This option will allow you to be notified via an E-mail address when a new entry arrives in your guestbook. The entry will be mailed to you as a notification. If you should choose to turn this variable on you will need to fill in the 2 variables that go along with it:
$recipient - Your email address, so that the mailing program will know who to mail the entry to.
$mailprog - The location of your sendmail program on your host machine.

Option 2: $uselog
This will allow you the ability to use the short log feature. It is already turned on so you will have to change it to 0 if you do not wish to use it. It has been implemented since there are probably many people who feel no need to have a log when people are making entries to a file anyway. Keep in mind that it will show errors which is one nice aspect about it.

Option 3: $linkmail
Turning this option on will make the address links in your guestbook become hyperlinked. So instead of simply having (name@some.host) it will put (<a href="mailto:name@some.host">name@somehost</a> so that anyone can simply click on the address to email them.

Option 4: $separator
This allows you to choose whether you want guestbook entries to be separated by a Paragraph Separator <p>, or a Horizontal Rule <hr>. By changing the 0 in the script to a 1, you will turn on the <hr> separator and turn off the <p> separator. The 0 option will do the reverse of that; turn on the <p> and turn off the <hr>.

Option 5: $redirection
By choosing 1 you will enable auto redirection and 0 will return a page to the user telling them their entry has been received and click here to get back to the guestbook.

Option 6: $entry_order
Set this option to 0 and the newest entries will be added below the rest of the entries. Keep this option at 1 and the guestbook will add the newest entries at the top.

Option 7: $remote_mail
Many users of the guestbook have requested that a form letter be automatically sent to the remote user when they fill in the guestbook. Turning this option on will tell the script to automatically mail any user who leaves an email address. You can specify the contents of the mail message by editing the section of the script that sends mail to the remote user. By default it sends a message that says, "Thank you for adding to my guestbook." and then shows them their entry. If you should choose to turn this variable on, you will need to fill in the 2 variables that go along with it:
$recipient - Your email address so that the mailing program will know who to mail the entry to.
$mailprog - The location of your sendmail program on your host machine.

Option 8: $allow_html
This option allows you to turn on or off the use of HTML tags by users of your guestbook. Setting this variable to 1 allows users to embed html tags such as <b> or <H1> or <a href=" "></a> into your html document. Setting this variable to 0 will not allow them to use any html syntax in their comments or any other field. You can still link to their comments or any other field. You can still link to their email address by turning $link_mail to 1.

There is also the ability for users to add their own URL and then their name is referenced to their URL in the guestbook.html file. This helps to eliminate the need for allow_html to be turned on, and lets users point you to a spot that will tell you more about them. Several users of the guestbook script have asked for this option. If you wish to disable the option, simply delete the following line from your addguest.html file:
URL: <input type=text name=url size=50><br>

These are the rest of the important guestbook files found in your Guestbook directory:
guestbook.html
This is the file that you will link to that will contain the Guestbook Entries. You may want to edit the title and heading spaces and customize the look any way you desire. Do not delete the line <!--begin--> from this guestbook, or else the script will have no way of knowing where to begin the editing. The <!--begin--> line is the only necessary line in your guestbook.html file, but the link to the addguest.html file is also a good idea. :-)

addguest.html
This is a fill-out form to add a new entry into the guestbook. This is also customizable as long as the action tags and basic field names in the form remain the same.

guestlog.html
This is a short log that lists domains and times that entries were created. Much easier to browse and it will point out those failed entries when users did not specify a name or comments. You will need to give the file read/write access.

Visitor Link Page allows you to set up a web page which your users can then add links to in specified categories. Newest links are added to the top of each category. A running total of the number of links present as well as the time when the last link was added is shown at the top of the page. Your preconfigured Visitor Links page is already set up on your server at http://www.yourdomain.com/links/links.htm. The only configuration you may want to do is to customize the look of the links.htm page. Just leave the method and input tags the way they are. If you decide to change the category names, you must do so in the links.htm document, AS WELL AS the links.pl file in your cgi-bin.

Normally, any text (such as your credit card number) sent from your browser to the web server is sent as plain text. This means that a hacker could potentially intercept (however unlikely) the information sent from your browser and read it. However, by using the secure server, the information is encrypted before it is sent from your browser. It would be practically impossible for anyone to decrypt it without knowing the key. Please use the secure server only when necessary, as when requesting sensitive information from your visitors.
The domains hosted by us are housed on any number of computers and all of them have a different machine name. To find out what machine name to use for your secure order access calls, check the faq file of your domain at:

http://www.yourdomain.com/faq.html

Each server has its own site-secure.net site, and although you will be putting your form on your own domain, it must be called through the site-secure.net server in order for the form to be secure.
To do this, create your form as usual and put it somewhere in your www directory. You can put your form anywhere you want to, but for this example, let's assume the normal URL for your form can be accessed from a browser with this URL:

http://www.yourdomain.com/signup/secureform.html

To call the form through the secure-order server, you need to use the following URL to access your pages via the secure server (even though your form resides on your own domain space):

https://machinename.site-secure.net/yourdomain/signup/secureform.html

That would be the URL you would put as an <HREF> to link to your form from whatever page you have your visitors link from. Don't forget the "s" in "https."
Your cgi-bin dir is:

https://machinename.site-secure.net/yourdomain/cgi-bin/

Special instructions for using FormMail.cgi with the Secure Server
If you are using formmail.cgi through the secure server, you can still place your form anywhere on your webspace you want to, but you MUST use the following URL as the ACTION of your form:

https://crimson.site-secure.net/cgi-bin/formmail.cgi

Here's an example of how the first parts of your form might look:

<FORM METHOD=POST ACTION="https://crimson.site-secure.net/cgi-bin/formmail.cgi">
<input type=hidden name="recipient" value="whoever@yourdomain.com">
<input type=hidden name="subject" value="Order">
<input type=hidden name="return_link_url" value="http://yourdomain.com/">
<input type=hidden name="return_link_title" value="Back to Main Page">

It is still important that you call your order page through a secure URL in order to work properly. For example: https://crimson.site-secure.net/yourdomain/order.htm.

This script is preconfigured for your server. There is a directory in your www directory called "random." Inside that directory is a file called random.txt. Just download this file to your hard drive and edit it with any random text you would like placed in an html document. Remember to keep the %% separator between quotes. You can use any html formatting tags you want to, including <href> tags so you can configure it as a random link generator. You can put in as many quotes as you wish. Upload the random.txt file to your server in the same location you found it, remembering to upload it in ASCII or text mode.
The script uses SSI (Server Side Includes) so the page you want to use random text on must have the .sht, .shtm, or .shtml extension. On your page, just put this tag wherever you want the random text to appear:
<!--#exec cgi="/cgi-bin/randomtext.cgi"-->

That's all there is to it!

WWW Board is a threaded World Wide Web discussion forum and message board, which allows users to post new messages, follow-up to existing ones and more. It is already preconfigured for your server. Just go to http://www.yourdomain.com/bbs to post your messages there.
There are several options you may want to configure. First of all, the index.sht file in the bbs directory can be customized any way you wish as long as you leave the method and input tags the way they are.
Additionally, here are some options contained in the wwwboard.pl script itself (located in your cgi-bin directory) which you may want to change, depending on your needs:

$show_faq = 1;

This option allows you to choose whether or not you want to display a link to the FAQ on every individual message page or not. It defaults to 1 and the link will be put in at the top of the message along with links to Followups, Post Followup and Back to $title. Setting this to 0 will turn it off, and keeping it at 1 will keep the link. You need to create a faq.html file and put it inside the bbs directory. The FAQ can contain any information you want to give your visitors about how the board works, your organization, types of postings that will be allowed, etc.

$allow_html = 1;
This option lets you choose whether or not you want to allow HTML mark-up in your posts. If you do not want to allow it, then everything that a user submits that has <>'s around it will be cut out of the message. Setting this option to 1 will allow HTML in the posts and you can turn this option off by setting it to 0.

$quote_text = 1;
By keeping this option set to 1, the previous message will be quoted in the followup text input box. The quoted text will have a ':' placed in front of it so you can distinguish what had been said in the previous posts from what the current poster is trying to get across. Setting this option to 0 will leave the followup text box empty for the new poster.

$subject_line = 0;
There are three options for the way that you can display the subject line for the user posting a followup. Leaving this option at 0 which is the default value, will put the previous subject line into the followup form and allow users to edit the subject however they like. Setting this option to 1, however, will quote the subject, but simply display it to the user, not allowing him or her to edit the subject line. The third and final option can be achieved by setting the $subject_line variable to 2. If it is set to 2, the subject will not be quoted and instead the user will be prompted with an empty subject block in their followup subject line.

$use_time = 1;
This option allows you to choose whether or not you want to use the hour:minute:second time with the day/month/year time on the main page. Day/Month/Year will automatically be placed on the main wwwboard.html page when a new entry is added, but if you leave this variable at 1, the hour:minute:second time will also be put there. This is very useful for message boards that get a lot of posts, but if you would like to save space on your main page, you can set this to 0, causing the hour:minute:second display not to be added.

Search will look at all your html pages for words you enter, and return all pages on a list with links. This program is completely configured and ready to run, but for Search.cgi to return a response, it need to be activated. This is easily done by logging in via telnet and at the prompt after login type the following command: chmod +r /www/yourdomain

Now you can access search.cgi with the following URL: http://yourdomain.com/cgi-bin/search.cgi.

There is a configuration file called search_define.pl which accompanies search.cgi and sets up the variables for it. You can customize which files you wish to exclude from searches, and also the cosmetics of the search and results pages.

There should be a Single Page Shopping Cart program installed on your server. You can see what it looks like by going to this URL with your browser:

http://www.yourdomain.com/shop/boutique.html

If you want to customize the shopping cart, (and you will if you want to sell products using this program), you can visit:

http://virtualpublisher.com/

The Virtual Publisher Shopping Cart program is sophisticated and complex. Rather than reprint all their directions here, please go to their website and download the help files associated with it.
If the Single Page Shopping Cart program wasn't installed on your server and you want it, please send us email and we'll make sure it's installed right away!

There are 3 different types of page counters you can place on your pages. The first is a no-frills graphical counter which looks like this:



To use this one, put the following tag somewhere on your page, but change the yourpage.htm to be the address of the actual page you are putting this counter on. Also, don't break up the tag like we did. We had to do that to fit it on the page. The width=5 part refers to how many digits you want in your counter.

<IMG SRC="/cgi-bin/nph-count?width=5&link=http://yourdomain/yourpage.htm">

Graphical counter: A simple counter called using "img" tag. You can edit the count on any page by going to the counter directory off of your main www and changing the number in the txt file of the page you would like to correct. http://yourdomain.com/counter

Finally, the simplest kind of page counter is a text-based counter. It uses SSI so the page you are putting it on must have the .sht, .shtm, or .shtml extension. It will look like whatever text and size attributes you give it on your page. The tag looks like this:

<!--#exec cgi="/cgi-yourdomain/counters/counter.cgi"-->

After you've put the counter on your page, look at it with your browser. If you don't see the counter the first time, hit reload. Then you should see the number 1. If you want to change the page count, FTP to your site, and look in the counters directory in your cgi-bin. There will be a file there with the name of whatever page you placed this counter on. Just upload a new text file with a new number on it, and that will be the new count on the page next time you hit reload. Remember to upload the file in ASCII or text format.

AlienForm is an easy to use Form to Email gateway. It uses simple templates to format all aspects of its output. It can send out more than one email at once so , you can have it send one email to you, a different courtesy reply to the user, and another to a co-worker. It can write directly to files, allowing you to log every time the form is submitted, or to store order details securely on the server.

Features :

• Fully customizable output formatted by simple text templates.
• Supports both command line mailers (ie Sendmail) and network (SMTP) sending of email.
• Can send any number of different emails on every invocation.
• Can output (append) to any number of files per invocation.
• Can perform mathematical calculations on data supplied in the form- so you can total orders, work out shipping etc.
• Environment Settings (i.e. current time, user's hostname etc.) may be included in the templates.
• Can check that entered data matches a particular format- i.e. all digits, a syntactically correct email address, letters only, etc.
• Does not have to send email on every invocation- so you can have the form take a number of steps to fill out before finally being logged or emailed.
• Security measures include you being able to specify what forms & sites are allowed to send to the script.
• Simple, easy to understand error messages.

• alienform.html - an example HTML form that would use the templates given below
  
• af.cgi - the script itself
• email.txt - an example email template to be sent to you
• email2.txt - an example of an automatic courtesy reply, sent to the person using the form.
• error.txt - an example of an error template that would be outputted to the browser should something go wrong.
• output.txt - an example success template that would be outputted to the browser if everything went right.
• logfile.txt - an example of a log file template.

URL: http://hostingsupport.com/nuequiz/password.htm (passwd - nuedream)
To change the password edit the file named password.cgi in directory nuequiz. Change this enty: $password = "nuequiz";
Choose to edit an existing quiz or create a new one.
To create a new one, fill in all of the required fields (the question, the answers, checking the correct answer and the reasoning for the answer) and click "Add".

Access the quiz by using the number of the question in the URL as follows:
www.hostingsupport.com/nuequiz/quiz.cgi?expert=1
This will display the first question of the expert quiz.

This script includes everything needed to run your own market-place on the internet. Users can submit adverts, which are updated at once and also send to the webmaster if wanted. Setting up and adapting the script is easy and requires no knowledge of Perl/CGI.
Info for running and modifying the script is in: /www/user/dp_market/readme.txt

Letting visitors recommend your site to their friends, family and so on, is a great way of getting more and more visitors. This script uses a standard text-file as template, which not only makes setting it up a lot easier, but also makes changing the "look and feel" of the email very easy. Wanna se how it works ? Click 'demo' to recommend DanPromote - to someone you know - or to yourself.
http://www.hostingsupport.com/dp_tellafriend/tellafriend.html

The search engine receives the input from the CGI form and processes the required files in order to find the search terms.
The list of files is found in /www/user/dirscan/fileinfo.txt. The script would not work if it doesn't get the valid list of files. For compiling the list of files to process use the dirscan.pl utility (so you're actually getting two separate projects, disrcan.pl can be used separately for creating a valid list of your files on the disk).
Add the following html code to the page directly in your /www that you want the search button on. Note: be sure to change hostingsupport.com to your domain.

<FORM name=search action="dirscan/find.cgi" method="post"> <b>Search my Homepage:</b><br> <INPUT maxLength=128 size=40 name=string> <INPUT type=submit value="hostingsupport.com" name=Submit>

For every search term that is found in a file, a file gets one point. Thus if the search string was "really cool perl script", and the opened file contained the word "really" 0 times, word "cool" 3 times, word "perl" 11 times and word "script" 1 time, the resulting point count would be 15 points.
Search engine features
The search engine is case-insensitive, thus "pErl", "Perl", "perl" and "PERL" would be treated the same. The location of the search engine on the system is not sensitive, as long as it can get to the valid list of files provided in the fileinfo.txt file.
Is it the right one for me?
The search engine is optimized to work with the sites containing up to 300 documents, after that level the performance of the engine tends to be slow (since it has to open every file and count the number of points the file gets). By default it searches the documents with "*.htm" extension, but that can be tweaked in the script.
How do I exclude files from the search?
There is no option to exclude files from the search, if you want them excluded, an option for excluding directories exists in dirscan.pl, if you don't want a specific file to be indexed, exclude it from fileinfo.txt, and do it every time you run dirscan.pl, which basically re-indexes your system and compiles a new list of valid files.
Can I customize the results screen?
The results of the search can be published with the header and the footer, to provide HTML customization, the header and footer should be located in /www/user/dirscan/header.txt and /www/user/dirscan/footer.txt, if you don't need a header and a footer, comment out the function calls print_header() and print_footer() in find.pl.
How the results are published?
The results are published as the filenames on your Unix machine, not as the titles.

Sends email to your default address whenever someone receives any of the following errors when accessing your site. The 4 lines below need to be in a file named .htaccess in your main /www directory. That file needs to have the permission of chmod 644 (rw-r--r--).
Note that the Referer feature won't work unless you have referer logs installed.
ErrorDocument 401 /guardian/guardian.cgi?401
ErrorDocument 403 /guardian/guardian.cgi?403
ErrorDocument 404 /guardian/guardian.cgi?404
ErrorDocument 500 /guardian/guardian.cgi?500

http://hostingsupport.com/newspro/newspro.cgi (change to your own domain name) First time login: Username = setup, Password is left blank This takes you to a page to enter your choice of Username, Password and email address. Click continue and complete the setup process. At this stage NewsPro should be fully installed and working. Go back to http://hostingsupport.com/newspro/newspro.cgi and add a news item. The next step it to make your web pages work with NewsPro. When you Submit News to NewsPro it is stored in a database file. Build News takes the news entries from the database and builds them into web-usable files. If you install addons, you may end up building several files in several different locations, but NewsPro always builds a file called news.txt in your /newspro directory. news.txt contains HTML but is not a complete web page and should not be viewed directly in a web browser. It is designed to be included into an HTML page (often your site's home page).
SSI (server side includes) is used to add the text to your web page. When you include an SSI in your web page, you are telling the server to merge together two separate files before showing your page to the person visiting your site.
In order to use SSI in a web page, you will need to give the page an extension of .shtml rather than .html. The exact SSI code you use to include news.txt depends on where news.txt is located in relation to the HTML file it is being included it. If both files are in the same directory, use:
<!--#include virtual="news.txt" -->
in your HTML file at the point where you'd like your news to appear. If your HTML file and news.txt are in different directories, use the relative URL from your HTML file to news.txt. For instance, if the locations of the respective files are http://www.yoursite.com/index.html and http://www.yoursite.com/newspro/news.txt, use:
<!--#include virtual="newspro/news.txt" -->
NOTE: don't forget to change the index.html file name to index.shtml
(Be sure that you've submitted and built news, otherwise there's nothing to include.)
Once news.txt is being generated and included into your page, you should have a working news system set up. If you post a news item, it will appear on your page.
NewsPro is capable of much more than this. You can change what your news items look like, you can archive news items and create different categories of news.
For complete documentation see:
http://amphibianweb.com/newspro/docs/newspro_documentation.html

Admin login (first time password = web). Be sure to change the password by modifying the file named 2badmin.pl in the 2bguest directory. Change the following line to enter your new password:
$pass="web";
http://hostingsupport.com/cgi-bin/2bguest/2badmin.pl?action=login

http://marnie.cihost.com/2bguest/2 bguest.cgi?action=home (to guestbook)

A random link generator with an admin URL used to add and delete links, get the HTML code and test drive the random link. Visitors can also add their own sites through the browser. Change hostingsupport.com to your own