Publishing - how do you automatically delete unmatched pages

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Is there a way to manage one site that 2 people are both modifing? We tried
the syncronization method but it does delete any old unmatched pages. we
then tested having the www. as local and publishing all changed pages from
local to remote (File copy) which seemed to work. We then open our file copy
as local, modify and publish local to remote. This tested out okay but now I
made some directory name changes and corrupted the template. So went back to
www. as local and published local to remote but the changed directories
stayed on my remote site (file copy). A dialog box appeared during the
transfer and ask me to delete a file and I answered yes to all but that was
the only file deleted. I will manually restore my folders but would like to
find a rock solid way to manage our updates and ensure that we have exact
copies and don't leave stray files on the server or file copies.

Any help would be appreciated.
Tad
 
You should always publish between location using the Change Pages Only option, from remote to local
and then local to remote. Remember with FP2003, the local copy is the first site you open, which can
be either the live/remote or your actual local PC copy.

--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WebMaster Resources(tm)

FrontPage Resources, WebCircle, MS KB Quick Links, etc.
==============================================
If you feel your current issue is a results of installing
a Service Pack or security update, please contact
Microsoft Product Support Services:
http://support.microsoft.com
If the problem can be shown to have been caused by a
security update, then there is usually no charge for the call.
==============================================
 
I use this method but FP occasionally leaves pages on the remote (file copy
or server) and I'm not certain why. The problem is compounded because an
asspociate is going to make changes to the site and then pas the torch if you
will and I will update my file copy by having the server as local and publish
local to remote, close and open my file copy as local and then publish local
to remote. When doing this it has tested okay at times and FP has aslo left
pages on the server and it could get missy. Any ingenoius ideas on how to
share one site? Tad
 
Option1: Always make changes on the live/remote site and each publish to their local as a backup
copy only.

Option 2: First person opens the live/remote site, then publish a copy to their local, make changes
and then re-publish to live/remote, in the meantime the second person is waiting for the first
person to republish. Repeat the above as needed, this will ensure that all copies of the site are in
sync.

--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WebMaster Resources(tm)

FrontPage Resources, WebCircle, MS KB Quick Links, etc.
==============================================
If you feel your current issue is a results of installing
a Service Pack or security update, please contact
Microsoft Product Support Services:
http://support.microsoft.com
If the problem can be shown to have been caused by a
security update, then there is usually no charge for the call.
==============================================
 
Short of comparing the 2 sites folder by folder in Remote Web Site view, No
From time to time a Publish All from your local to the online site will eliminate stray files

PS
A good idea whenever multiple authors are working on the site is to always check View Reports (Files recently Added and Files
recently Changed) whenever you start a work session in the online site
--




|I use this method but FP occasionally leaves pages on the remote (file copy
| or server) and I'm not certain why. The problem is compounded because an
| asspociate is going to make changes to the site and then pas the torch if you
| will and I will update my file copy by having the server as local and publish
| local to remote, close and open my file copy as local and then publish local
| to remote. When doing this it has tested okay at times and FP has aslo left
| pages on the server and it could get missy. Any ingenoius ideas on how to
| share one site? Tad
|
| "Thomas A. Rowe" wrote:
|
| > You should always publish between location using the Change Pages Only option, from remote to local
| > and then local to remote. Remember with FP2003, the local copy is the first site you open, which can
| > be either the live/remote or your actual local PC copy.
| >
| > --
| > ==============================================
| > Thomas A. Rowe (Microsoft MVP - FrontPage)
| > WebMaster Resources(tm)
| >
| > FrontPage Resources, WebCircle, MS KB Quick Links, etc.
| > ==============================================
| > If you feel your current issue is a results of installing
| > a Service Pack or security update, please contact
| > Microsoft Product Support Services:
| > http://support.microsoft.com
| > If the problem can be shown to have been caused by a
| > security update, then there is usually no charge for the call.
| > ==============================================
| >
| > | > > Is there a way to manage one site that 2 people are both modifing? We tried
| > > the syncronization method but it does delete any old unmatched pages. we
| > > then tested having the www. as local and publishing all changed pages from
| > > local to remote (File copy) which seemed to work. We then open our file copy
| > > as local, modify and publish local to remote. This tested out okay but now I
| > > made some directory name changes and corrupted the template. So went back to
| > > www. as local and published local to remote but the changed directories
| > > stayed on my remote site (file copy). A dialog box appeared during the
| > > transfer and ask me to delete a file and I answered yes to all but that was
| > > the only file deleted. I will manually restore my folders but would like to
| > > find a rock solid way to manage our updates and ensure that we have exact
| > > copies and don't leave stray files on the server or file copies.
| > >
| > > Any help would be appreciated.
| > > Tad
| >
| >
| >
 
In remote web site view (FP2003), if you change the View dropdown from
"Folder Contents" to "Files in Conflict" you will see the conflicting
and unmatched files on the Remote server.
Change the publish direction (using the radios on bottom right) to
will show the conflicting and unmatched on the local web.
 
Back
Top