|
| |
| |
FrontPage How To
Volume 1 - Issue 24 - October 2004
Fixes to Common FrontPage Publishing Problems
By David Pfeiffer of FrontLook.com
|
|
Here are some common FrontPage Publishing
problems and the typical fixes for these problems:
Problem: The local site works fine, but after
publishing the site to the remote server, the Java, JavaScripts, PHP or
ASP code stops working.
Solutions: This type of problem usually has to do with the settings in
FrontPage or the server you are publishing to:
 |
If you are using FrontPage 2003 and you
have the HTML optimization turned on, you are probably deleting critical
script on the way to the server. Turn off HTML optimization! Also make
sure your server is not filtering HTML as well, most servers do not
perform HTML filtering.
|
|
If you are publishing ASP script to a
Linux, Apache or Unix server it will not operate. In regards to PHP,
some servers require the PHP file extension reflect the version of PHP.
EarthLink has been know to require all PHP files to have the extension
".php4". |
Problem: The local site works fine,
but after publishing the site my FrontPage navigation has disappeared or
has nothing but broken images where the buttons should be.
Solutions: This type of problem
usually has to do with one of several problems
|
FrontPage has a nasty habit of changing
the name of default page on the web server (some non-Microsoft servers
require the home page be named "index.htm"). This causes the navigation
to disappear. Fix this buy inspecting the server for the name of the
default page, you can adjust this on the local web and then publish the
entire web to the server again (not just the changes).
|
|
Some non-Microsoft servers have problems
creating "_" underscore directories. By inspecting the folders on the
server with an FTP program, you can see if the "_derived" folder is
present. This folder contains all the navigation button images for the
navigation and link bars. |
Problem: The local site looks fine,
but after publishing the site remote copy doesn't seemed to be updated or
things are broken or missing.
|
Sometimes the local web and remote web
does not sync up, first try recalculating (Tools->Recalculate
Hyperlinks...) the web locally and then publishing the web. If that
doesn't work, then try publishing the entire web to the server, not just
the changes (see the Publishing properties dialog for this switch). You
can also try bringing up the web live in FrontPage and selecting the
"Tools->Recalculate Hyperlinks..." menu item. If that doesn't work, ask
your hoster to delete the web from the server and republish the web.
|
|
Shared Borders - Sometimes when using
shared borders on the web, the local web and remote web does not sync up
, first try recalculating (Tools->Recalculate Hyperlinks) the web
locally and then publishing the web. If that doesn't work, then try
publishing the entire webs to the server, not just the changes (see the
Publishing properties dialog for this switch). If that doesn't work,
then manually update the contents of the shared "_border" files by
right-clicking on the "_borders" folder and selecting the "Publish
Selected Files..." menu item. You can also try bring up the web live in
FrontPage and selecting the "Tools->Recalculate Hyperlinks..." menu
item.
|
|
Sometimes the broken image has a
reference to a location on your hard drive and there the image is not
accessible from the server. Correct the image link. |
Problem:
When trying to publish the web to the remote server,
I get an error on certain files or a FrontPage Extensions Error or
SharePoint Extensions Error.
Solutions: This type of error is
typically caused by the FrontPage Extension being corrupted on the server.
|
If you have "_" underscore folders on
your web, the server might not allow these folders to be created by the
FrontPage extensions because they are Unix system folders (if you can't
see the "_" folders on your web, then select the "Tools->Web
Settings..." menu item and then the advanced tab and check the "Show
documents in hidden folders" check box). This can be fixed by using an
FTP program to make the missing folders and then publishing again. The
hoster can also add these folders or change the permission on the web to
allow the creation of "_" folders.
|
|
Other errors are typically because of
corrupted FrontPage server Extensions. The Hoster should uninstall and
reinstall the FrontPage server extension for the web site.
|
|
If you are getting a server is locked
error after aborting a publishing operation, the extensions might have
locked-out publishing to the web. This can be corrected by deleting the
"service.lck" file from the "_vti_pvt" folder. |
And That's it |
| |
|
