Updating Navigation Bars/structure when publishing

[Guest]

Often, when I publish from a local site to the remote website, the
navigational structure doesn't seem to work on the remote site. The only
solution I've figured out so far is to overwrite all the files, but it takes
long to do. Is there any other way of forcing the FP2003 to overwite
navigational structure only on the remote site every time the changes are
made and published? Many thanks.

 

[Kathleen Anderson [MVP - FrontPage]]

Try opening the remote site in FrontPage (when the publish is complete) and
do a Tools | Recalculate Hyperlinks.

--

~ Kathleen Anderson
Microsoft MVP - FrontPage
Spider Web Woman Designs
web: http://www.spiderwebwoman.com/resources/

 

[Guest]

Thanks,

I suspect that all the FP03 navigation information is held in either a
single file or a set of files that somehow, sometimes do not get updated on
the server, even if changes to navigation are made on the local website
version. If I knew what these files are, I would be able to force FP to
replace them on the server every time I publish the changes. Is that a good
idea, and would you know what files there are and where I should be looking
for them? Perhaps there is a way of replacing navigation files at the time
of publishing (I recall that sometimes FP asks if that needs to be done, but
sometimes there is no such option). Thanks again.

 

[Thomas A. Rowe]

FP never publish it configuration files between location/servers. The FP extensions on the server
create and maintain the configuration files needed for the web on the 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]

Thank you, but why then it often happens that several FP navigation bars do
not work when published (and only of few pages were updated). They start
working again when all the files on the servers are overwritten.

Also, sometimes during the publishing process there is a question if I want
to update/overwrite the navigation structure on the server. If I could
somehow force FP to update it everytime, that would solve the problem.
Cheers.

 

[Thomas A. Rowe]

When you publish, you must publish with the Change Pages Only option selected. However is sound like
you local copy is out of sync with the live/remote copy, which can happen when you use Publish
Selective Page option.

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

Thanks Thomas,

It's not the case (i.e. the navigational bars go berseck sometimes when the
Changes Pages Only option is selected, and no individual pages were
published). I'm trying to get to the bottom of it: I was told that there is
a hidden file that is published containing the navigation structure info -
perhaps in _vti_pvt folder?). If I could only force FP to update this file
every time I publish the changes, that would be great. Any ideas? Thanks.

 

[Stefan B Rusynko]

Although the final nav structure is stored on the server in _vti_pvt (in structure), that file is never "published"
Instead the FP SE reads all the individual _vti_cnf files and rebuilds that file (generate a new one) each time

If your nav view is not correct it may be due to corrupt meta data stored on your PC
Delete all FP web cache files (*.web) at
%APPDATA%\Microsoft\Web Server Extensions\Cache

Then open FP and your local site, make any change in Nav view, and run a Tools Recalculate Hyperlinks
- that should refresh all meta data for your next publishing
If not, do the same on your online site (making the change to nav view different there)
- when you publish from PC to online FP should advise you the 2 nav views are different
(always select the replace option)

--

_____________________________________________
SBR @ ENJOY (-: [ Microsoft MVP - FrontPage ]
"Warning - Using the F1 Key will not break anything!" (-;
To find the best Newsgroup for FrontPage support see:
http://www.frontpagemvps.com/FrontPageNewsGroups/tabid/53/Default.aspx
_____________________________________________


| Thanks Thomas,
|
| It's not the case (i.e. the navigational bars go berseck sometimes when the
| Changes Pages Only option is selected, and no individual pages were
| published). I'm trying to get to the bottom of it: I was told that there is
| a hidden file that is published containing the navigation structure info -
| perhaps in _vti_pvt folder?). If I could only force FP to update this file
| every time I publish the changes, that would be great. Any ideas? Thanks.
|
| "Thomas A. Rowe" wrote:
|
| > When you publish, you must publish with the Change Pages Only option selected. However is sound like
| > you local copy is out of sync with the live/remote copy, which can happen when you use Publish
| > Selective Page option.
| >
| > --

 

[Guest]

Perfect, thanks Stefan,

One more question: what's the easiest way of tricking the FP into asking me
to replace the navigational view on the remote site every time I publish
changes made on the local machine? Sometimes I seem to have trouble making
changes to navigational view on the remote site - I was hoping that there is
perhaps a single file that could be changed or deleted on the remote site via
FTP that would cause FP to conclude that the remote and local navigational
structures are different, and ask me te replace it with the local (i.e.
proper) navigational structure. Many thanks.

 

[Stefan B Rusynko]

All you need to do is change anything in your nav view
- even a page name that is set to not be included in navigation

--

_____________________________________________
SBR @ ENJOY (-: [ Microsoft MVP - FrontPage ]
"Warning - Using the F1 Key will not break anything!" (-;
To find the best Newsgroup for FrontPage support see:
http://www.frontpagemvps.com/FrontPageNewsGroups/tabid/53/Default.aspx
_____________________________________________


| Perfect, thanks Stefan,
|
| One more question: what's the easiest way of tricking the FP into asking me
| to replace the navigational view on the remote site every time I publish
| changes made on the local machine? Sometimes I seem to have trouble making
| changes to navigational view on the remote site - I was hoping that there is
| perhaps a single file that could be changed or deleted on the remote site via
| FTP that would cause FP to conclude that the remote and local navigational
| structures are different, and ask me te replace it with the local (i.e.
| proper) navigational structure. Many thanks.
|
| "Stefan B Rusynko" wrote:
|
| > Although the final nav structure is stored on the server in _vti_pvt (in structure), that file is never "published"
| > Instead the FP SE reads all the individual _vti_cnf files and rebuilds that file (generate a new one) each time
| >
| > If your nav view is not correct it may be due to corrupt meta data stored on your PC
| > Delete all FP web cache files (*.web) at
| > %APPDATA%\Microsoft\Web Server Extensions\Cache
| >
| > Then open FP and your local site, make any change in Nav view, and run a Tools Recalculate Hyperlinks
| > - that should refresh all meta data for your next publishing
| > If not, do the same on your online site (making the change to nav view different there)
| > - when you publish from PC to online FP should advise you the 2 nav views are different
| > (always select the replace option)