Microsoft Knowledge Base Email Alertz

How to resolve conflicting files when you publish a Web site to a server in FrontPage 2003

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

Article ID: 911594 - Last Review: January 4, 2006 - Revision: 1.2

How to resolve conflicting files when you publish a Web site to a server in FrontPage 2003

INTRODUCTION

This article describes how to resolve conflicting files when you publish a Web site to a server in Microsoft Office FrontPage 2003.

MORE INFORMATION

When you use FrontPage 2003 to publish a Web site to a server, you may notice that the Status column displays Conflict for some of the files in the Remote Web Site view. This conflict status is indicated if the following conditions are true:
  • You change a file on the remote Web site.
  • You do not make the same changes on the local Web site.
You must first decide on the version of the file that you want to keep. Then, publish that version to the remote Web site. If both versions contain changes, you must open both files and then merge the changes manually.

To prevent file conflicts, use one of the following methods:
  • Always change the local Web site first. Then, publish to the remote Web site.
  • Use the Synchronize option in the Remote Web Site view. The Synchronize option publishes files from the local Web site to the remote Web site or from the remote Web site to the local Web site. This option guarantees that both Web sites contain the most recent version of any file.
Note If both the local version and the remote version of a file contain changes, the Synchronize option will keep the most recent version and overwrite the earlier one.

APPLIES TO
  • Microsoft Office FrontPage 2003
Keywords: 
kbhowto KB911594
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate

Anonymous User Report As Irrelevant  
Written: 1/8/2006 1:52 PM
This is a very simplistic article. But what about issues like resolving files that conflict because they are pages containing Javascript that won't run on a specific server? Generally, there is presently an imperative that you are running the server you publish to, since every debug umltimately ties into adjusting server configuration. What FrontPage needs is a Microsoft operated site that classifies server types and provides feedback to the FrontPage user specific to the user's hosting server acount. This "Server Resolution" site would have to be a large disc. Too large to fit into the boxed FrontPage product. The Server Resolution site is essentially just a public extension of existing Product Development networks. It would be a WONDERFUL CHERRY ON THE CAKE IF VISTA ALLOWS SERVER RESOLUTION FOR THE ENTIRE OFFICE PRODUCT LINE.

Steve Report As Irrelevant  
Written: 2/6/2006 6:38 PM
Javascript doesn't run on a server, it runs in the client browser.