Can't get nav bar props to apply to only one page

[tcarp]

After I upgraded to FP2003 (from 2000) I've had a problem setting nav bars
the way I want them. In 2000 I was used to being asked whether I wanted to
apply the properties to the current page or all pages. In 2003 I don't seem
to get that option.

What's happening is that I change the props at a parent level and all
children change to the same nav props. Specifically, I set the nav props on
a page to show child level however I want all the child level to show same
level. If I change the parent to show child level all the children get the
same change.

In 2003 how to you control nav bar props differently at different levels?

Thanks

Tom

 

[Ronx]

I think you are confusing applying shared borders with changing nav.
bar properties. The same system is in use in FP2003 as in FP2000,
just more options for styling the nav. bar.

The page that is different to the others should not have a shared
border, or if you are using a DWT or include page, then apply a copy
of that DWT/include with different settings for the navigation bar.

 

[tcarp]

Maybe I am confused, but I think I have it right. I'm talking about a
navigation bar (I think it's called a link bar in FP2003). In a shared
border, in this case, I have a link bar. In FP2000 I was able to edit the
properties of that bar (as I can in 2003), however, in 2000 I could set each
page's link bar independently of all others.

In the site I'm working with, when I set the properties of a link bar on a
page, all the child pages inherit the same structure. By the same token, if
I change the link bar in one of the child pages, the parent's also changes.

What I want to be able to do is set a page to have the link bar contain the
children, and the children pages to have their peers (same level).

Tom

 

[tcarp]

Ron, one other thing.

I'm using link bars as part of a shared border since that's all I knew how
to do. These shared borders come from themes and I don't think themes (at
least for the borders and link bars) is what I'm going to ultimately want to
do.

From what I'm learning it appears that there are other ways in 2003 to
better set up and control the navigation elements that are better than the
theme solutions.

Is the better practice to master include pages (or other techniques) to
create the borders and navigation components? If so, are there some simple
guidelines to get started building this for my sites?

Thanks

Tom

 

[Ronx]

Inline
--
Ron Symonds - Microsoft MVP (FrontPage)
Reply only to group - emails will be deleted unread.
FrontPage Support: http://www.frontpagemvps.com/

Maybe I am confused, but I think I have it right. I'm talking about
a
navigation bar (I think it's called a link bar in FP2003). In a
shared
border, in this case, I have a link bar. In FP2000 I was able to
edit the
properties of that bar (as I can in 2003), however, in 2000 I could
set each
page's link bar independently of all others.

That facility does not exist in FP2000. A link bar in a shared border
is shared with every page using that shared border, and this applied
to every version of FrontPage that supports shared borders.
If you change the properties of the link bar, it changes the
properties of the linkbar in the shared border file, which is then
used in every page.

In the site I'm working with, when I set the properties of a link
bar on a
page, all the child pages inherit the same structure. By the same
token, if
I change the link bar in one of the child pages, the parent's also
changes.

That is expected if the link bar is in a shared border. It has worked
like this in every version of FrontPage.

What I want to be able to do is set a page to have the link bar
contain the
children, and the children pages to have their peers (same level).

Let the child pages use the shared border, but remove the shared
border from the parent page, and replace it with your own design,
based on the shared border.
If the parent page is the Home Page, then use Children under Home as
the link bar properties, and all pages can have the shared border.

Since you are using FP2003, try using a Dynamic Web Template for the
child pages, and copy the template and use the copy for the parent
pages (if they are not also children.) On the copy, change the link
bar properties.

Or use FP included pages and use different includes depending on the
status of the page (child or parent)

Or insert two link bars - one set to Children, one set to Same Level.

 

[Ronx]

Include pages and Dynamic Web Templates are, in my opinion, the way to
set up consistent layouts and navigation, together with CSS for
styling.

See http://accessfp.net/frontpageincludedcontent.htm
and also the DWT e-book at http://frontpage-ebooks.com/

 

[tcarp]

Thanks. I must have it wrong. Apparently I was thinking about pages that
didn't have shared borders.

I'll experiment with DWT, include pages, and inserting link bars. I like
some of the differences between 2000 and 2003.

Tom