Publishing causes references to staging (development) server when

[Guest]

Hi,

I'm using FP 2002 (v10.2623.3501). When my site gets published from a
(staging) server behind the firewall to a public server (in the DMZ), many of
the hyperlinks point to the staging server (http://stage...) rather than the
public web site server. So, of course, users cannot view pages because they
refer to a URL behind our firewall. This is particularly true for the FP
search webbot.

What settings/options do I need to ensure this does not happen?

Thank you in advance for your response.

Geoff

 

[Thomas A. Rowe]

On the staging server make sure you are always working on the site via http (File Menu | Open Web)
and that all content is either created in or imported into the current open web prior to using it.

--
==============================================
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.
==============================================

 

[Guest]

I assume by "imported" you mean published from FP from another box?

I develop content on my workstation (I have FrontPage but no IIS-makes ASP
development a pain). Then I publish to the staging server, typically
selected pages and occasionally the whole site. In fact, recently the search
webbot was broken so I published the whole site from my workstation to
staging. That appeared to fix the problem until someone noticed the
incorrect URL (and thus no access) in search results.

Another person actually publishes from the staging server to the public
site. I don't have access to much, I can't even look in the registry on my
own machine as the Navy locks these box up so tight.

I suppose it's a no-no to manually edit "search.htm0.idq"?

Do you know where I can find some good documentation about what goes on
underneath the covers of FrontPage?

 

[Thomas A. Rowe]

You need to publish the complete site, avoid using Selective publishing as it doesn't update
references to external content or upload images.

--
==============================================
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.
==============================================

 

[Guest]

I just found out from the network guy that he uses Site Server to publish to
the public site. Could this cause a problem?

 

[Thomas A. Rowe]

If the site is hosted on a server with the FP extensions, then it must be published via FP to the
live/remote server.
--
==============================================
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.
==============================================

 

[Guest]

Forgot to thank you. That resolved our problem. Keep up the good work!