|
FAQ:
Publishing your site with FrontPage
General
comments
When
you order your account, we ask if you wanted the FrontPage
2000 extensions installed in your website which allow for
you to manage and publish your site with Microsoft FrontPage.
FrontPage
is a versatile product from the point of view of the developer
as it allows you to use various functions (forms, counters,
forums and others) easily and without the need for programming
skills.
Blacklab
fully supports FrontPage 2000 and we recommend users of any
earlier versions to upgrade to FrontPage 2000 as there does
appear to be some compatibility issues between users of Front
Page 98 and our latest server extensions.
Recognising
some of the issues with FrontPage, Blacklab will work with
clients to resolve problems and make publishing easy.
FrontPage
2002. Blacklab will support these new extensions in the
near future. Please watch this space.
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.webco.co.uk).
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 html as part of its
name (ie 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 passowrd specified by you when the account has
ordered. Front Page will then start uploading all files.
Error
messages
FrontPage is prone to errors on publishing. 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 LINIX. 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 LINIX, 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.
Questions
Common questions include:
Q
- How do you get the Guestbook log to insert entries at the
top of the page rather than at the bottom?
A - Add
the reverse chronology line to your webot parameters in the
html:
<!--webbot
bot="SaveResults" u-file="guestlog.htm"
s-format="HTML/DL" b-reverse-chronology="TRUE"
s-label-fields="TRUE" s-builtin-fields="Date
Time REMOTE_USER" s-form-fields -->
More:
Microsoft
Knowledge Base Articles - General FrontPage Publishing Information
|
