Microsoft KB Archive/299867

= FP2002: Web Changes Are Not Visible on the Destination Server =

Article ID: 299867

Article Last Modified on 8/20/2007

-

APPLIES TO


 * Microsoft FrontPage 2002 Standard Edition

-



This article was previously published under Q299867



For a Microsoft FrontPage 2000 version of this article, see 266430.



SYMPTOMS
In Microsoft FrontPage 2002, 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 published your Web 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 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 several locations where you can exclude a file from publishing:
 * The Folders View.
 * The Page Properties dialog box.
 * The Publish Status report.



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

http://www.microsoft.com

the Web server displays the following default document:

http://www.microsoft.com

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 rather than 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 &quot;Publish your FrontPage Web to an Unextended Web Server by Using FTP&quot; 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, use one of the following methods:

In Folders view

 * 1) On the View menu, click Folders.
 * 2) Right-click the file, and then click Don't Publish on the menu that appears to remove the check mark from this option.

In the Page Properties dialog box

 * 1) On the View menu, click Folders.
 * 2) Right-click the page, and then click Page Properties on the menu that appears.
 * 3) Click the Workgroup tab.
 * 4) Click to clear the Exclude this file when publishing the rest of the Web check box.
 * 5) Click OK.

From the Publish Status Report

 * 1) On the View menu, point to Reports, point to Workflow, and then click Publish Status.
 * 2) Under the Publish column, click the cell that corresponds to the page for which you want to change the publish status and then click Publish.



MORE INFORMATION
For more information about Web Publishing in FrontPage 2002, click Microsoft FrontPage Help on the Help menu, type Web publishing in the Office Assistant or the Answer Wizard, and then click Search to view the topic.

Additional query words: prb

Keywords: kbprb KB299867

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.