You've already run into part of the awkwardness if using fp's
navigation...very tricky to get it the way you want within shared borders if
you have a big web it'll drive ya nuts. Easier, at least for me, to use
includes for navs. much more control, takes a little longer to setup because
they're not automatic (on or off) but you can then control which page has
what set of navigation depending on what included page you include on the
page.
Or DWT's, but I haven't messed with those very much.
"MarkB" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
| Thanks for your reply... can you exlpain what you mean by "awkward?"
|
| "Rob Giordano (Crash)" <(E-Mail Removed)> wrote in message
| news:e$(E-Mail Removed)...
| > You can have more than one nav bar in a shared border...but it does get
| > awkward.
| >
| > Or don't use shared borders, you can use included content or dwt's.
| >
| >
| > "MarkB" <(E-Mail Removed)> wrote in message
| > news:uf%(E-Mail Removed)...
| > | Can you have different navigation bars (e.g.,. parent, child, same
| > level)
| > on
| > | different pages within a website.
| > |
| > | For instance, on the home page have a "Child Pages under Home" link
bar,
| > | while on the Press Section page, have a "Child Level" link bar to go
to
| > the
| > | press releases, press contact info, etc. pages under the Press Section
| > page.
| > |
| > | It seems that once you set the navigation bar on one page, it changes
| > all
| > | other pages to the same navigation bar so that there is no way to get
to
| > | some of your pages embedded further down in your navigation chart.
| > |
| > |
| >
| >
|
|
|