KompoZer User Guide - Section 10
Publishing a site means transferring the site, i.e. the pages, images and stylesheets involved, to a web server from which they may be accessed, usually but not necessarily, by the public. This process is called ‘Uploading’. Prior to publishing there are a few checks which should be carried out.
Validating simply means checking that the page or site operates as intended. Designers may by now have a plethora of files some of which are obsolete or are not required for the published site. A good practice is to create a new folder structure and in it place those files, and only those files, which are needed.
This can be done using your usual file manager e.g. Windows Explorer but the KompoZer File Manager can be set up to do this task by ‘Publishing’ these to a new folder.
KompoZer provides a Markup Cleaner Tools > Markup Cleaner which can be used to remove redundant code which clutters the file but does not contribute to the page content. This does not necessarily remove all redundant content but makes a good contribution to it.
The next stage of validation has already been taken care of by KompoZer. Users have a high assurance that the code generated represents valid HTML or CSS. The site should next be run using a browser. Possible problems include you having omitted to transfer files to the correct folders, naming the folders incorrectly, including getting the case wrong.
Tip. Those having access to only one computer running Windows XP may like to know that they can run several versions of Internet Explorer on it. Joe Maddalone developed the method and Yousif Al Saif has produced an installer. Initially this did not run on Windows Vista but a method of doing so has been developed.
The site should be checked on a range of different browsers. Several modern Mozilla based browsers behave very similarly so do not provide additional confidence. Check with browsers from other sources and be very conscious that a few visitors may still be using very old browsers.
In late 2007 a minimal set of browsers to test on might be Firefox (latest version), Opera (latest version), Internet Explorer 6 and Internet Explorer 7. Both these latter two behave differently from each other and also from other browsers so use both. In spite of the availability of Internet Explorer 7 version 6 remains the most widely deployed so it is essential to check with this.
Browsers are often very tolerant of incorrect code. A much more rigorous test is to submit pages to the W3C validators. There are two: one checks that the page code conforms to the HTML specification, the second that the style sheet (internal and external linked) code conforms to the CSS specification. KompoZer provides direct access to the first of these.
To validate a page. Open it in KompoZer. On the Menu choose Tools > Validate HTML. A validator window opens and the page is automatically submitted for validation. The result will be displayed in the window. (On Windows systems at least this validation is no longer possible for files on the local disk.)
To validate pages with internal stylesheets or separate external stylesheets the validators may be used independently. The URLs are given in the References (Appendix 2). Pages may be validated either from the local disk or after the files have been uploaded.
While the W3C validators check rigorously for conformity with specifications this does not guarantee that the code will run correctly. Unfortunately none of the current browsers fully support the specifications! This is why browser validation is an essential step.
You can publish your web pages to a web server on which you have an account. Your ISP probably offers limited free space but you can buy space from professional hosting providers.
To publish a site you need to know the settings for the space so that you can set up your system.
Files may be uploaded using any available FTP program but KompoZer has built-in facilities which are integrated with the Site Manager which makes this task very simple.
While uploading using KompoZer is simple the facilities and the folder structures supported are limited. You may prefer to use one of the available open source or freeware FTP programs.
In fact you are highly recommended to do this.
The rest of this page describes how KompoZer is supposed to work but only partially does.
It is not an exaggeration to say that KompoZer's publishing function is BROKEN so you should use it only if you want to play around and not if you hope to use it for anything other than an experiment. In fact you will be wasting your time in doing so.
Just use a decent FTP program to upload your pages. If you are using Windows FireFtp is probably the best.
This warning will be removed if the code ever becomes fixed.
While setting up Site Manager you may already have configured the ‘remote’ site (sections 8.4 and 8.2), if not, either proceed as detailed there, go directly to Publish Settings via Edit > Publishing Site settings.
Enter the following details:
If you have several sites set up and you have one site that you always or usually publish to you may wish to click on the name of this site then ‘Set as default’. This simplifies uploading.
Open the page that you want to upload. An easy way to do this is from the Site Manager.
The ‘Troubleshooting’ button takes you to the KompoZer help system but this is short of aid in this area at present.
Other possible problems include
Once you have published a page, if you need to publish it again, your settings (e.g. subdirectories) should be remembered by KompoZer. You will not see steps 2 to 4 again unless changes have been made to the page.