FP2000: Web Changes Are Not Visible on the Destination Server (266430)



The information in this article applies to:

  • Microsoft FrontPage 2000

This article was previously published under Q266430

SYMPTOMS

When you make changes to your web on your local computer and publish the web to another Web server, the changes do not appear on the destination Web server.

CAUSE

This behavior may be caused by one of the following.

Cause 1: No Default Document Exists, or Default Document Is Incorrect

You have published your page without a default document, or your default document does not match the Web server's configuration.

Cause 2: You Are Viewing a Cached Web Page

You are viewing the old version of your web page that is stored in your Web browser's cache.

Cause 3: You Did Not Copy Essential Files via FTP

You did not copy all of the files to the Web server when you are using a third-party FTP program.

Cause 4: The Publish Operation Was Interrupted

The publishing operation was interrupted or canceled.

Cause 5: You Published to a Staging Server

You published your web site to a staging server, but you are viewing the production server.

Cause 6: The Page Is Marked to Be Excluded from Publish

The properties of the web page are set to exclude the page from the publishing process. There are two locations where you can exclude a file from publishing: the Page Properties dialog box and the Publish Status report.

RESOLUTION

Resolution 1: Rename or Create Your Default Document

To resolve this problem, create or rename your default document to match the configuration of the Web server.

NOTE: Microsoft Internet Information Server (IIS) typically uses Default.htm as its default document, and UNIX derivative Web servers generally use index.htm.

If you are unsure of the configuration of the Web server, contact the server's administrator for more information.

Web servers use a default document that is displayed if a specific web page is not specified. For example, if you browse to the following Web site the Web server displays the following default document:

Resolution 2: Clear Your Web Browser's Cache

To work around this issue, quit and restart your Web browser.

The image cache in Microsoft Internet Explorer loads images quicker and reduces network traffic. To increase performance, Internet Explorer opens images from the image cache in memory, instead of from the disk or server.

Resolution 3: Use the FTP Publishing Feature of FrontPage

When you use a third-party FTP program to copy your Web to an Internet server, you must copy all of the files in your Web's content directory. If all files are not copied to the destination Web, some FrontPage components (for example, a theme) may not appear or function as expected.

To correct this problem, use FrontPage to transfer your Web. For more information about how to use the FTP publishing feature of FrontPage, please see the "Publish your FrontPage Web to an Unextended Web Server by Using FTP" section of the following Microsoft Knowledge Base article:

198523 FP2000: How to Publish a FrontPage Web

NOTE: You may be able to correct the problem by recalculating the hyperlinks in your Web. To do this, follow these steps:
  1. Open your Internet Web site in FrontPage. To do this, click Open Web on the File menu.
  2. On the Tools menu, click Recalculate Hyperlinks.
  3. On the File menu, click Close Web.

Resolution 4: Republish Your Web

If the connection was lost during publishing, or the publishing process was canceled, use the publishing command to republish your web. For more information about publishing, see the following article in the Microsoft Knowledge Base:

198523 FP2000: How to Publish a FrontPage Web

Resolution 5: View the Changes on the Staging Server

Some larger organizations use staging and production servers. A staging server is used to test new webs. The production server is the server that stores the final web sites that are viewable on the Internet.

If you are publishing your site to a staging server, make sure that you view the changes from the staging server. The web will not be visible on the production server until it is copied there.

Resolution 6: Include the Page in Publishing

To include the file in the publishing process through the Page Properties dialog box, follow these steps:
  1. In Folder view, right-click the page, and then click Page Properties.
  2. Click the Workgroup tab, and then click to clear the Exclude this file when publishing the rest of the Web check box.
  3. Click OK.
To include the file in the publishing process through the Publish Status report, follow these steps:
  1. On the View menu, point to Reports, and then click Publish Status.
  2. Click to select the Publish cell for the page. (The property should be set to Don't Publish at this point.)
  3. Select Publish from the list.

Modification Type:MajorLast Reviewed:1/2/2002
Keywords:kbprb KB266430