|
Publishing your
website with FrontPage
Once you are ready to publish your website through go to the File menu and
click on "Publish Web". A screen appears asking you for the "location" of
your website. Enter the full address of your domain name (i.e
http://www.skaggsweb.com).
If this is the first
time you are publishing, click on Options, then click on "Publish all pages,
overwriting any already on the destination". This makes sure FrontPage
replaces the default index page places on your main directory during account
configuration. It is important that the index page has .htm or .html as part
of its name (i.e. index.html) in lower case. In fact it is sensible to use
lower case for all file names.
Then, click on the
Publish button. FrontPage will then connect to the server and ask for your
username and password. Use the username and password specified by you when
the account has ordered. Front Page will then start uploading all files.
Error messages
Earlier versions of Front Page are prone to errors on publishing and has
some compatibility problems with the Front Page 2000 extensions used on our
servers.
Typical error
messages include:
Error:
The
following pages in your front-page web contain dynamic FrontPage Components,
such as a search form or a FrontPage form handler. They will not work
because the server you are publishing to does not have the FrontPage Server
Extensions installed.
Response:
What ever the
error message says, all our servers have the FrontPage Server Extensions
installed. This error usually appears before you start to publish, even
while you are making your website. Ignore it - it is a stupid message and
quite meaningless.
Error:
This form
is being created on a Disk-Based Web or the FrontPage Server Extensions have
not been configured to send e-mail. Please direct your system administrator
or Internet Service Provider to the instructions in "Setting up E-Mail
Options in Windows" or "Setting up E-Mail options on UNIX" in the Server
Extensions Resource Kit. If you do not have the Server Extensions Resource
Kit, you can find it at http://www.microsoft.com/FrontPage/wpp/serk.
Would you like to
remove the E-Mail recipient?
Response:
Ignore it.
FrontPage Server Extensions on our servers are configured to send e-mail.
Error:
The
server could not complete your request. Contact your Internet Service
Provider or web server administrator to make sure that the server has the
FrontPage Server Extensions installed. For more information, click Details.
Response:
The connection
between your computer and our servers is slow or has problems. Because of
this, FrontPage gets tired of waiting for the server to respond for an
upload to finish. Contact us and we'll give you an alternative dial-up
connection that might be faster and more reliable at no extra cost - apart
from local telephone charges.
Error:
After
uploading, some pages or images are broken. They work fine on my computer.
Why?
Response:
This common
problem when moving files from Windows to LINUX. Uppercase and lowercase
letters do make a difference on LINUX. If your HTML code links to image.jpg
but the file is named image.JPG, the image will be displayed on the page. On
LINUX, the link won't find image.jpg, because the file is named image.JPG.
Simply make sure all your files are lower case - including the extensions
(.jpg, .gif, .html).
Error:
Some
webbots (like counters, search functions, etc) don't work, or, I get the
following message when submitting data through a FrontPage generated form:
FrontPage Run-Time
Component Page - You have submitted a form or followed a link to a page that
requires a web server and the FrontPage Server Extensions to function
properly.
This form or other
FrontPage component will work correctly if you publish this web to a web
server that has the FrontPage Server Extensions installed.
Response:
If you get this
message, FrontPage did not correctly configure the form's HTML code to
correctly point to the webbot on the server. Forms are configured while
FrontPage is *uploading* them. If you upload the pages without FrontPage
Publish We or via FTP software, you will get such error.
If you are correctly
uploading them via FrontPage (using the http:// method) and you still get
that, choose "Publish all pages, overwriting any already on the destination"
when publishing. If you still get it, then it's a problem of your browser's
cache or ISP's cache which require clearing. If this still occurs after
cache
clearance - contact us for the extensions to be re-installed.
Error:
I still
see the default set up page when I go to my website, even after I've already
published my site. How can I eliminate that page?
Response:
Make sure the
filename of your site's main page is called index.html. That is the file the
server looks for when someone goes to your website. If it's already called
that, choose "Publish all pages, overwriting any already on the destination"
when publishing so that your FrontPage software replaces the default
index.html file on your account. If you still see it, then it's a problem of
your browser's/ISP's cache. See our page entitled "Common mistakes" for an
explanation on cache features in your browser and/or ISP
|
