While it is true that you can insert many simple properties like the current date and time into a page using JavaScript, and it is even possible to use JavaScript includes to create simple page templates there are disadvantages to relying on the surfer's web browser to do all of this rather than using your server. The main problem with using JavaScript comes from the fact that it relies on the visitor's web browser, it's version and it's settings.

We'd like to help you out, but we all have school or jobs in addition to doing the site. You should Google any of those terms to find information on them.

You can make arbitrary changes to static documents by configuring an Action which launches a CGI script. The CGI is then responsible for setting a content-type and delivering the requested document (the location of which is passed in the PATH_TRANSLATED environment variable), along with whatever footer is needed. Busy sites may not want to run a CGI script on every request, and should consider using an Apache module to add the footer.

There are a number of SSI tutorials available on the web. By default, only .shtm and .shtml files are parsed for SSI statements but you can modify your .htaccess file to allow .htm and/or .html files to be parsed. For example, to parse .htm files for SSI, add the following line to your .

SSI makes it easy to bring changes to your website. There are some changes you will need to make to every page or to every page in a specific section. Your website might start out with just 10 pages, and you might figure that it is no big deal to cut-and-paste a change to the navigation menu 10 times. But each time you add a page, you have to update that menu. And with each new page added, you have to paste one more time.

Have a look at this document. It shows in example form how you can a combination of XSSI and negotiation to tailor a set of ErrorDocuments to your personal taste, and returning different internationalized error responses based on the client's native language.

Unfortunately there is one slight downside to using SSI rather than having a plain, static HTML document and that is speed. With a normal static web page all that the server does when it receives a request is read the file from the disk and then send it straight out to the requesting browser, however with an SSI document the server has to read through the document and run extra commands to insert the required information.

JavaScript is an enhancement to HTML (web documents) that allows your computer to perform actions beyond just displaying a static web page. Generally JavaScript is enabled in all major browsers, but can be disabled. We use JavaScript on every page to provide mouse-over graphic effects. We also use JavaScript to help display submission tips on the final secure checkout page.

Yes. Those are client-side technologies, so the host doesn't have to do anything to support or enable them. Any browser (such as Internet Explorer or Netscape) that supports them is enough, so any host will do. It doesn't matter whether Java or Flash are listed among the plan's features, they are supported by default.

Most browsers have JavaScript automatically enabled. If, however, you have disabled JavaScript you could encounter problems when purchasing on our site. We recommend that you have JavaScript enabled when using our site. Please refer to your browsers' support page for details on how to turn on JavaScript.

this time JavaScript is the method of delivery we are currently offering. We may offer server side propositions in the future.

The first thing that you need is a host that supports SSI, unfortunately most free and cheap hosts (including Geocities, Tripod and Angelfire) do not support SSI. If your host allows CGI scripts then they probably also support SSI but if in doubt check their FAQs or contact them directly, unfortunately you may find that some hosts will charge extra for SSI support. Many hosts also require you to rename any pages using SSI to have a filename ending with ".shtml" rather than ".

Unfortunately there is no set standard for SSI commands that all server vendors adhere to. What this means that there are a core few commands that will work on most servers, and a number of additional commands that will only work on certain brands of server. You should check your hosts FAQs or check the documentation for your server (see below) for an absolute list of commands that will work for you.

Sure -- simply make sure that the name of your document with server-side includes ends with ".shtml" See also: Apache Tutorial: Server Side Includes

Yes, you can use SSI on our servers. SSI stand for "server side include", it work in files with .shtml, .html, .htm extensions.

This must be one of the most useful features of SSI- the ability to include one document inside another. For your information, SSI supports relative/absolute paths. Put that code inside your Web page, and your-file.htm shows up in the specific place where the SSI code inserted. The file doesn't have to be a ".htm" file. It could also be a ".txt" file (ie: your-file.txt, your-file.inc, your-file.text).

Yes! Just use .shtml for any files you want the server to parse. It's as easy as that -- we don't charge you anything for using SSI.

For security purposes, we do not enable Telnet/SSH access by default. You must contact our support department or open a support ticket to enable this feature. Please note that we strongly encourage the use of SSH instead of Telnet, to ensure that your login to the server remains secure. SSH is a powerful service which allows you to log into the server remotely to perform specific tasks. Common tasks include checking for new mail (via pine) or sending outgoing mail (via sendmail).

No, SSI is not required. All Count works on Unix, Linux and Windows NT servers. All you need is a cgi-bin folder.