Questions about Publishing

[news.microsoft.com]

Hi,

For some time an administrator at our company has used FrontPage to edit
files on our intranet site. She edits them directly on the server. Now, I
am faced with doing some troubleshooting of a problem with the search
function not working, and I need to "Publish" the website.

So, my understanding of "publishing" is that generally one has the web site
structure on their workstation, and the "publish" function would copy the
files to the actual live web server.

In our case, we don't have a local workstation copy, can I just publish it
anyway by:

--opening the server's physical file location "c:\intranet2" for example, in
Front Page.

---Then doing a "publish".

The reason for this is that the Front Page Extensions report the error: "

So if I do this, what affect does it have, since the files are already on
the server?

 

[Ronx]

If you are editing directly on the server, the site should be accessed
using http://websitename.com or http://ipaddress.

If you access the site using a file address (example v:\path\website )
then
1) you cannot publish to the http:// address - you are already there, and
FP will be attempting to change meta data files both on the local web
(v:\path\website) and on the http:// site; these are the same files.

2) Components that need the FPextensions to run will probably not work,
since these will be in disc-based web state. Forms (including the search)
will be affected by this.

Open the site using the http:// protocol, then run Tools->Recalculate
Hyperlinks. This should revert the FP components to the web-server
condition. There is no need to publish (except to create a backup) when
editing against the web-server.

 

[news.microsoft.com]

Thank you!

If you are editing directly on the server, the site should be accessed
using http://websitename.com or http://ipaddress.

If you access the site using a file address (example v:\path\website )
then
1) you cannot publish to the http:// address - you are already there, and
FP will be attempting to change meta data files both on the local web
(v:\path\website) and on the http:// site; these are the same files.

2) Components that need the FPextensions to run will probably not work,
since these will be in disc-based web state. Forms (including the search)
will be affected by this.

Open the site using the http:// protocol, then run Tools->Recalculate
Hyperlinks. This should revert the FP components to the web-server
condition. There is no need to publish (except to create a backup) when
editing against the web-server.