Publishing

[Andrew C]

Hi

I am using Publisher 2003. and when publishing my site to my hosting server
when it finishes it shows the files still needing to be published. I have
published the files and frontpage still thinks the need to be published, but
in actually fact they are up-to-date on he server. What would be causing
this.

I have only just got this problem from when i switched over where i host my
site. Could this be a problem from their end or is it something at my end??

The hosting company has uninstalled and reinstalled Frontpage extensions and
are saying that its something from frontpage.

Please HELP

Thanks

Andrew

 

[Andrew Murray]

Are you publishing the site from Microsoft Publisher? If so, that's your
problem. Everytime you publish with anything except FP in http mode, you
risk corrupting the FPSE and that adds the need to check/resintall the
extensions.

Also I believe that FP doesn't recognise or keep track of any files outside
its "web" structure (i.e. the tracking feature that gives you the status
such as changed, conflict, unchanged, unmatched, etc). So you should
really be using Frontpage and open your web via File > Open Web to publish
it. (you don't actually mention if you use Frontpage or Publisher to
publish this site).

You're making yourself a lot of extra needless work by using Publisher at
all. However, if *you* know the site's up to date, does it really matter
what Frontpage says?

The best solution and suggestion is forget about using Publisher - it is not
designed for web development. Use Frontpage to develop and publish the
site.

 

[Thomas A. Rowe]

1. MS Publisher uses the FP extensions to publish.

2. However using Publisher, FP is not aware of changes made.

--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
==============================================
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.
==============================================