Web Hosting - HTML Support

First of all, check that the link is correctly spelled, and that the correct case is used - INDEX.HTML is not the same as index.html.

Next, check the file paths. A common error is to leave the location relative to another computer's filesystem, eg:-

<a href="C:\Documents\MySite\mysite.html">Link</a>

This is incorrect as it refers to a file on your PC, not on our servers. File paths should either be absolute, eg:-

<a href="http://mysite.com/mysite.html">Link</a>

or relative, eg:-

<a href="mysite.html">Link</a>, if mysite.html is in the same directory as the page that it's linking from.

Finally, check that there are no conflicts with other scripts on the site. Many major CMSes such as Wordpress and Joomla use URL rewriting that will interfere with the correct operation of links.

You may be seeing a cached version of the page; please force refresh the page in the browser by simultaneously pressing Ctrl and F5 or delete all the cache/stored pages in the options/settings menu of your browser. If this doesn't help, check you're putting your site in the right place; it should go under the "public_html" folder.

If your site is written in PHP, the default index.html page may still be visible - you should delete this in order to show your site.

The Formmail Script is provided via the eXtend Control Panel, full usage instructions can be found after installation.

Assuming that you have successfully installed the formmail script via the eXtend Control Panel, then all the files will be present and the file permissions are correct. Therefore the only other reason for a problem would be your form that is calling the script.

In your eXtend control panel when you installed the script you were given a link for "Usage Instruction" and example HTML code to use, please take a look at that and make sure yours is the same. You are able to make modifications to this to add your own fields, but the basic structure is there to follow.

In order for the form to fully display on a web page the page should be saved with a .cgi extension.

This error indicates that there is no valid home page, or that permissions have been set on a page which does not allow you to view it.

Cause 1: Missing or wrongly named index file

When you don't specify a file name when accessing a site (eg visiting the domain directly as most do at http://www.domainname.com), the server searches through a list of default filenames and will display the first one it finds. Common default names are index.php, default.htm, index.htm and index.html - The first page of your website should use one of these names, with all lowercase letters.

When we create your web hosting account, we place a simple index.html file on the server so that there is something there before you upload your site. If you delete this file and don't replace it, then you will see the error message above. To fix this, ensure that the first page in you site is called index.html and that the file is uploaded to the public_html directory.

Cause 2: Incorrect Access Control Settings

This error will also be displayed if the directory access settings for your site's root directory are set with access criteria which you do not meet. Usually these settings are contained in a file called ".htaccess". This file is sometimes generated manually, but can also be configured by some web development tools, such as MS FrontPage.

If you are using FrontPage, then you should alter the web permissions using this program, and republish your site. In most other cases, manually removing the .htaccess file usually solves the problem.

There are a great many ways of achieving that and if you do not know how to code it yourself then we do provide access to a CGI script from the eXtend Control Panel of any hosted domain. It is called "404/500 Error Page" and it can be configured so that Our file not found and server error pages can be configured to email you when an error occurs.

Once enabled, you will be able to customise the look and feel of the errors by downloading and editing the relevant HTML files.

Yes we do. SSI (Server Side Includes) are tags that are placed in HTML pages, and evaluated on the server while the pages are being served. They allow our customers to add dynamically generated content to an existing HTML page, without having to generate the entire page via a CGI program, or other dynamic technology.

Pages that use Server Side Includes should have filenames which end with the suffix .shtml to be recognised by the server as such.

The path to your website is partially determined by your domain name, but is in the following format:

/home/sites/your-domain-name.com/public_html
If you are using PHP, you can find out this path by entering the following into a php script:

echo getcwd();

It is possible to name your default index page something other than index.html, index.cgi, index.php, etc., by using a directive in a special configuration file in your webspace. That file is called '.htaccess' (a dot followed by 'htaccess'). The directive needed is

DirectoryIndex foo.html
That will make the default page (i.e., the file name that will be requested if there's no filename in the URL, www.domain.com/) 'foo.html'. The change will affect the directory the .htaccess file is placed in and all sub-directories.

XML is browser based, and it is not dependant on the type of server that you are running your website on.

XML stands for Extensible Markup Language. It was developed as a way to improve on HTML and SGML. XML is not a language in the true sense, but rather a system for defining other languages. XML tags are not predefined in XML. You must define your own tags. XML uses a Document Type Definition (DTD) or an XML Schema to describe the data.

If you wish to use XML, you should have some basic understanding of WWW, HTML and the basics of building Web pages Web scripting languages like JavaScript or VBScript.

XML is not a replacement for HTML.
XML and HTML were designed with different goals:

XML was designed to describe data and to focus on what data is.
HTML was designed to display data and to focus on how data looks.

HTML is about displaying information, while XML is about describing information.

XML does not DO anything. XML is created to structure, store and to send information.

The following example is a note, stored as XML:

<note>
<to>Jonathan</to>
<from>Rob</from>
<heading>Reminder</heading>
<body>Don't forget the meeting today!</body>
</note>

The note has a header and a message body. It also has sender and receiver information. But still, this XML document does not DO anything. It is just pure information wrapped in XML tags. Someone must write a piece of software to send, receive or display it.

XML tags are not predefined. You must "invent" your own tags.

The tags used to mark up HTML documents and the structure of HTML documents are predefined. The author of HTML documents can only use tags that are defined in the HTML standard.

XML allows the author to define his own tags and his own document structure.

The tags in the example above (like <to> and <from>) are not defined in any XML standard. These tags are "invented" by the author of the XML document.

It is important to understand that XML is not a replacement for HTML. In future Web development it is most likely that XML will be used to describe the data, while HTML will be used to format and display the same data.