Publishing Problem (FP2002/Windows 2000)

Topic

New Reply

Hi there,

I am must about to start using a disk-based copy of my web so that we will not be working on the Production copy on the main server. The server where the disk-based web will sit does not have IIS nor FP Server Extensions installed (nor can they be installed), so from what I can gather working on the disk-based web will be OK if text on a page needs to be changed, or a few pages need to be linked up. But if any changes need to be made on a page the requires FP Server extensions, the changes can only then be made on the Production server. Am I right so far??

Assuming my thinking makes sense to this point, my difficulty is that if a page is changed on the production server, and then someone makes another change on the backup disk-based web, when they then go to publish the web Frontpage rightly notices the difference in timestamps from the page that required FPserver extensions, but will then try to overwrite the newer version of that file on the production server.

I realise that Frontpage identifies all the files that it will publish and that you have the option to stop a file being published, but I can see disaster looming….we are using this for our company intranet, and there are many thousands of files – way too many to physically check each folder to see what files are going to be published and I see important files being overwritten by older versions. Is there a way that I can setup FrontPage to recognise where there is a newer datestamp on a file on the production server that it should not be overwritted…or is there a better way that I can achieve the same goal?

Thanks in anticipation

Lor

Reply | Quote

Replies

You can edit pages regardless of whether the extensions are installed, but you cannot preview them accurately. Depending on your application, for example reading from and writing to a database, this could be a deal breaker. In a perfect world, you either would install IIS and FPSE on your local computer, or publish to a test machine in your local network.

Reply | Quote

When you use the FP Publish Web function you will find these options (see attached picture) are available. The publish web option does not require FP Server Extensions. So, the best solution is to specify the options you want all of your web authors to use as standard.

Cheers

Reply | Quote

Hi,

Thanks for getting back to me on this!

I am finding that since I have to connect to the backup copy as a file path rather than http: that I cannot get access to some of the Frontpage features such as checking a form properties or a search properties..so any changes to these files are having to be completed on the live server. Therefore the copy on the live server is newer than the backup version. So even if I select either the option to “Determine the changes by comparing source and destination webs” or to “use the source timestamps to determine changes since last published” when publishing it will pick out the fact that the file on the live server has changed and will try to overwrite the newer version on the live server with the outdated version from the backup.

Is there anyway that I can set the program to determine whether a file is older or newer (rather than just different) than the one on the live server, and to not publish files where the date stamp is newer on the live server?? Even anywhere within the server extensions?

Thanks again!

Lor

Reply | Quote

I’m finding your scenario a little confusing, is everyone updating everything?
However, have you considered marking the files that you are worried about as “Do not publish” files?

Reply | Quote

I’m finding your scenario a little confusing, is everyone updating everything?
However, have you considered marking the files that you are worried about as “Do not publish” files?

Reply | Quote

Hi,

Thanks for getting back to me on this!

I am finding that since I have to connect to the backup copy as a file path rather than http: that I cannot get access to some of the Frontpage features such as checking a form properties or a search properties..so any changes to these files are having to be completed on the live server. Therefore the copy on the live server is newer than the backup version. So even if I select either the option to “Determine the changes by comparing source and destination webs” or to “use the source timestamps to determine changes since last published” when publishing it will pick out the fact that the file on the live server has changed and will try to overwrite the newer version on the live server with the outdated version from the backup.

Is there anyway that I can set the program to determine whether a file is older or newer (rather than just different) than the one on the live server, and to not publish files where the date stamp is newer on the live server?? Even anywhere within the server extensions?

Thanks again!

Lor

Reply | Quote

When you use the FP Publish Web function you will find these options (see attached picture) are available. The publish web option does not require FP Server Extensions. So, the best solution is to specify the options you want all of your web authors to use as standard.

Cheers

Reply | Quote