Are there a lot of problems with FrontPage 2003 navigation link bar?
Often some buttons don't have images or the home page button is missing...

Currently, I publish my website like this: Safest procedure that I know (am
new though).
1. Save files that are to be included elsewhere
2. Save each .dwt file and propagate the changes.
3. Publish the entire web, overwriting all files, (not just changed ones)

Problem: Why does the page I am viewing on a published site either local
file system or web server have the current page navigation button blank,
i.e. without the button image?
I have recreated the nav bar but still have the same problem.

Re: Why is the navigation link bar button blank in FP 2003 for the current page I am viewing? by Dan

Dan
Thu Feb 19 14:19:49 CST 2004

I should mention that the Navigation link button bar is on every page in the
site using an include.
I did setup a custom link bar and the navigation is set. I do want the same
navigation links on every page in the site. I use the same nav bar for the
footer but that uses text not buttons and that displays fine.
It is strange that the buttons work fine in designer but not when published.
All buttons work fine when I am on a different page not linked to a button
on the nav bar. The button does not work for the current page linked to the
nav bar, the button image for the current page is missing.


"Dan V." <danv@yah.com> wrote in message
news:OrNC1yx9DHA.2308@TK2MSFTNGP09.phx.gbl...
> Are there a lot of problems with FrontPage 2003 navigation link bar?
> Often some buttons don't have images or the home page button is missing...
>
> Currently, I publish my website like this: Safest procedure that I know
(am
> new though).
> 1. Save files that are to be included elsewhere
> 2. Save each .dwt file and propagate the changes.
> 3. Publish the entire web, overwriting all files, (not just changed ones)
>
> Problem: Why does the page I am viewing on a published site either local
> file system or web server have the current page navigation button blank,
> i.e. without the button image?
> I have recreated the nav bar but still have the same problem.
>
>



You must turn off optimizing HTML (every option), publish, then turn back on every option. Smells like a bug. by Dan

Dan
Thu Feb 19 15:25:03 CST 2004

I found the problem. You must turn off optimizing every option when in FP
2003 (I had every option selected) when publishing. Then you can turn back
on every optimizing option again and publish and all navigation buttons work
properly. Sounds like a bug to me.


"Dan V." <danv@yah.com> wrote in message
news:e7HA$Wy9DHA.1472@TK2MSFTNGP11.phx.gbl...
> I should mention that the Navigation link button bar is on every page in
the
> site using an include.
> I did setup a custom link bar and the navigation is set. I do want the
same
> navigation links on every page in the site. I use the same nav bar for
the
> footer but that uses text not buttons and that displays fine.
> It is strange that the buttons work fine in designer but not when
published.
> All buttons work fine when I am on a different page not linked to a button
> on the nav bar. The button does not work for the current page linked to
the
> nav bar, the button image for the current page is missing.
>
>
> "Dan V." <danv@yah.com> wrote in message
> news:OrNC1yx9DHA.2308@TK2MSFTNGP09.phx.gbl...
> > Are there a lot of problems with FrontPage 2003 navigation link bar?
> > Often some buttons don't have images or the home page button is
missing...
> >
> > Currently, I publish my website like this: Safest procedure that I know
> (am
> > new though).
> > 1. Save files that are to be included elsewhere
> > 2. Save each .dwt file and propagate the changes.
> > 3. Publish the entire web, overwriting all files, (not just changed
ones)
> >
> > Problem: Why does the page I am viewing on a published site either
local
> > file system or web server have the current page navigation button blank,
> > i.e. without the button image?
> > I have recreated the nav bar but still have the same problem.
> >
> >
>
>



Re: You must turn off optimizing HTML (every option), publish, then turn back on every option. Smells like a bug. by Stefan

Stefan
Fri Feb 20 03:46:59 CST 2004

You should carefully read each of the optimization options
- many of them are NOT intended to be used w/ a FP Site using FP Design and Run time components, and will cripple or disable FP some
components (converting your page to straight html), or even prevent the ability to open the FP site in FP again once published
- they can even cripple your local FP site design time tools if you publish to a remote w/ all optimizations selected and then sync
the remote back to the local
- using "all" the options is probably only viable when publishing to a FTP site where you do not have the FP SE and do not use any
of the FP SE features

--

_____________________________________________
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.net-sites.com/sitebuilder/newsgroups.asp
_____________________________________________


"Dan V." <danv@yah.com> wrote in message news:OZQtX7y9DHA.3792@TK2MSFTNGP09.phx.gbl...
| I found the problem. You must turn off optimizing every option when in FP
| 2003 (I had every option selected) when publishing. Then you can turn back
| on every optimizing option again and publish and all navigation buttons work
| properly. Sounds like a bug to me.
|
|
| "Dan V." <danv@yah.com> wrote in message
| news:e7HA$Wy9DHA.1472@TK2MSFTNGP11.phx.gbl...
| > I should mention that the Navigation link button bar is on every page in
| the
| > site using an include.
| > I did setup a custom link bar and the navigation is set. I do want the
| same
| > navigation links on every page in the site. I use the same nav bar for
| the
| > footer but that uses text not buttons and that displays fine.
| > It is strange that the buttons work fine in designer but not when
| published.
| > All buttons work fine when I am on a different page not linked to a button
| > on the nav bar. The button does not work for the current page linked to
| the
| > nav bar, the button image for the current page is missing.
| >
| >
| > "Dan V." <danv@yah.com> wrote in message
| > news:OrNC1yx9DHA.2308@TK2MSFTNGP09.phx.gbl...
| > > Are there a lot of problems with FrontPage 2003 navigation link bar?
| > > Often some buttons don't have images or the home page button is
| missing...
| > >
| > > Currently, I publish my website like this: Safest procedure that I know
| > (am
| > > new though).
| > > 1. Save files that are to be included elsewhere
| > > 2. Save each .dwt file and propagate the changes.
| > > 3. Publish the entire web, overwriting all files, (not just changed
| ones)
| > >
| > > Problem: Why does the page I am viewing on a published site either
| local
| > > file system or web server have the current page navigation button blank,
| > > i.e. without the button image?
| > > I have recreated the nav bar but still have the same problem.
| > >
| > >
| >
| >
|
|



Re: You must turn off optimizing HTML (every option), publish, then turn back on every option. Smells like a bug. by Dan

Dan
Fri Feb 20 09:32:12 CST 2004

thank you I have been warned. (I did not notice this warning in the help
documentation for navigation bars... - I wasted a lot of time on this - bug
I still call it) -Crippling your site with no warnings is not good.
By the way what is FP SE?

"Stefan B Rusynko" <sbr_enjoy@hotmail.com> wrote in message
news:e35q%23Z59DHA.1632@TK2MSFTNGP12.phx.gbl...
> You should carefully read each of the optimization options
> - many of them are NOT intended to be used w/ a FP Site using FP Design
and Run time components, and will cripple or disable FP some
> components (converting your page to straight html), or even prevent the
ability to open the FP site in FP again once published
> - they can even cripple your local FP site design time tools if you
publish to a remote w/ all optimizations selected and then sync
> the remote back to the local
> - using "all" the options is probably only viable when publishing to a FTP
site where you do not have the FP SE and do not use any
> of the FP SE features
>
> --
>
> _____________________________________________
> 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.net-sites.com/sitebuilder/newsgroups.asp
> _____________________________________________
>
>
> "Dan V." <danv@yah.com> wrote in message
news:OZQtX7y9DHA.3792@TK2MSFTNGP09.phx.gbl...
> | I found the problem. You must turn off optimizing every option when in
FP
> | 2003 (I had every option selected) when publishing. Then you can turn
back
> | on every optimizing option again and publish and all navigation buttons
work
> | properly. Sounds like a bug to me.
> |
> |
> | "Dan V." <danv@yah.com> wrote in message
> | news:e7HA$Wy9DHA.1472@TK2MSFTNGP11.phx.gbl...
> | > I should mention that the Navigation link button bar is on every page
in
> | the
> | > site using an include.
> | > I did setup a custom link bar and the navigation is set. I do want
the
> | same
> | > navigation links on every page in the site. I use the same nav bar
for
> | the
> | > footer but that uses text not buttons and that displays fine.
> | > It is strange that the buttons work fine in designer but not when
> | published.
> | > All buttons work fine when I am on a different page not linked to a
button
> | > on the nav bar. The button does not work for the current page linked
to
> | the
> | > nav bar, the button image for the current page is missing.
> | >
> | >
> | > "Dan V." <danv@yah.com> wrote in message
> | > news:OrNC1yx9DHA.2308@TK2MSFTNGP09.phx.gbl...
> | > > Are there a lot of problems with FrontPage 2003 navigation link bar?
> | > > Often some buttons don't have images or the home page button is
> | missing...
> | > >
> | > > Currently, I publish my website like this: Safest procedure that I
know
> | > (am
> | > > new though).
> | > > 1. Save files that are to be included elsewhere
> | > > 2. Save each .dwt file and propagate the changes.
> | > > 3. Publish the entire web, overwriting all files, (not just changed
> | ones)
> | > >
> | > > Problem: Why does the page I am viewing on a published site either
> | local
> | > > file system or web server have the current page navigation button
blank,
> | > > i.e. without the button image?
> | > > I have recreated the nav bar but still have the same problem.
> | > >
> | > >
> | >
> | >
> |
> |
>
>



Re: You must turn off optimizing HTML (every option), publish, then turn back on every option. Smells like a bug. by Stefan

Stefan
Fri Feb 20 09:43:15 CST 2004

FP SE - FrontPage Server Extensions

--

_____________________________________________
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.net-sites.com/sitebuilder/newsgroups.asp
_____________________________________________


"Dan V." <danv@yah.com> wrote in message news:ehQN3a89DHA.3900@tk2msftngp13.phx.gbl...
| thank you I have been warned. (I did not notice this warning in the help
| documentation for navigation bars... - I wasted a lot of time on this - bug
| I still call it) -Crippling your site with no warnings is not good.
| By the way what is FP SE?
|
| "Stefan B Rusynko" <sbr_enjoy@hotmail.com> wrote in message
| news:e35q%23Z59DHA.1632@TK2MSFTNGP12.phx.gbl...
| > You should carefully read each of the optimization options
| > - many of them are NOT intended to be used w/ a FP Site using FP Design
| and Run time components, and will cripple or disable FP some
| > components (converting your page to straight html), or even prevent the
| ability to open the FP site in FP again once published
| > - they can even cripple your local FP site design time tools if you
| publish to a remote w/ all optimizations selected and then sync
| > the remote back to the local
| > - using "all" the options is probably only viable when publishing to a FTP
| site where you do not have the FP SE and do not use any
| > of the FP SE features
| >
| > --
| >
| > _____________________________________________
| > 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.net-sites.com/sitebuilder/newsgroups.asp
| > _____________________________________________
| >
| >
| > "Dan V." <danv@yah.com> wrote in message
| news:OZQtX7y9DHA.3792@TK2MSFTNGP09.phx.gbl...
| > | I found the problem. You must turn off optimizing every option when in
| FP
| > | 2003 (I had every option selected) when publishing. Then you can turn
| back
| > | on every optimizing option again and publish and all navigation buttons
| work
| > | properly. Sounds like a bug to me.
| > |
| > |
| > | "Dan V." <danv@yah.com> wrote in message
| > | news:e7HA$Wy9DHA.1472@TK2MSFTNGP11.phx.gbl...
| > | > I should mention that the Navigation link button bar is on every page
| in
| > | the
| > | > site using an include.
| > | > I did setup a custom link bar and the navigation is set. I do want
| the
| > | same
| > | > navigation links on every page in the site. I use the same nav bar
| for
| > | the
| > | > footer but that uses text not buttons and that displays fine.
| > | > It is strange that the buttons work fine in designer but not when
| > | published.
| > | > All buttons work fine when I am on a different page not linked to a
| button
| > | > on the nav bar. The button does not work for the current page linked
| to
| > | the
| > | > nav bar, the button image for the current page is missing.
| > | >
| > | >
| > | > "Dan V." <danv@yah.com> wrote in message
| > | > news:OrNC1yx9DHA.2308@TK2MSFTNGP09.phx.gbl...
| > | > > Are there a lot of problems with FrontPage 2003 navigation link bar?
| > | > > Often some buttons don't have images or the home page button is
| > | missing...
| > | > >
| > | > > Currently, I publish my website like this: Safest procedure that I
| know
| > | > (am
| > | > > new though).
| > | > > 1. Save files that are to be included elsewhere
| > | > > 2. Save each .dwt file and propagate the changes.
| > | > > 3. Publish the entire web, overwriting all files, (not just changed
| > | ones)
| > | > >
| > | > > Problem: Why does the page I am viewing on a published site either
| > | local
| > | > > file system or web server have the current page navigation button
| blank,
| > | > > i.e. without the button image?
| > | > > I have recreated the nav bar but still have the same problem.
| > | > >
| > | > >
| > | >
| > | >
| > |
| > |
| >
| >
|
|