Shared Boreders

L

Lucy

I'm using FP 2000. I have shared borders and navigation bar. My problem is I don't really understand child, parent, same level pages. My navigation bar shows correctly on all pages except my main page. When I make it show up on that page the bars disappear on all the other pages. So I add another bar to my main page. It shows up perfect in my previews, when I publish, there are two bars on every page. Please help somebody! (www.friendshipmissionary.com).
 
A

Andrew Murray

I don't quite understand it much either but in simplified terms: using the
'family' analogy below:

Father (Home)

John.htm Lucy.htm Jim.htm
Bob.htm
Hobbies.htm School.htm


Index is the PARENT page "John", "Lucy", "Jim" and "Bob" are the CHILD pages -
i.e. on the SAME LEVEL, Index is the level above them.

Hobbies.htm and School.htm school are CHILD pages of "John" (and pattern follows
for the others)

Anyway this is a simplified explanation. I hope someone else can verify or
explain further. Put simply it is just the system that Frontpage uses to link
pages to each other, and keep track if pages are removed etc and using the
'recalculate hyperlinks' I suppose it rearranges the pages in the hierarchy.

The navigation bars you insert have the page links and also "Up" and "Home" the
"Up" link goes to the parent page in the level above, so if you go "Up" from
hobbies.htm in the above example, you end up at John.htm.

I hope this makes sense.

The home page can't have an "Up" link because you're at the top level - after all
you can't go higher than the top storey of a building can you - think of it in
that context - the top level - literally is the TOP level.

The Index.htm (frontpage calls it "home" and the navigation structure view
indicates this with a house icon) or whatever your server default is) is the top
page you can go to. So if you leave the nav bar as it is, all the pages should
have the correct links.

Lucy said:
I'm using FP 2000. I have shared borders and navigation bar. My problem is I
don't really understand child, parent, same level pages. My navigation bar shows
correctly on all pages except my main page. When I make it show up on that page
the bars disappear on all the other pages. So I add another bar to my main page.
It shows up perfect in my previews, when I publish, there are two bars on every
page. Please help somebody! (www.friendshipmissionary.com).
 
L

Lucy

Thank you Andrew. It helped a little. My main page is not the home page, that's why there's an Up link. My home (Index.html) has no borders, which is what I want, but my main page should. and I can't get the bar to stay on that page and athe others to. I look forward to more responses. take a look at it and you'll see what I mean.
 
A

Andrew Murray

OK, I didn't realise.....so your index.htm is like a "splash" page and "main.htm"
is your home page kind of thing.

In that case I don't know.....but I see, there are no links (navigation) to
speak of (I entered your site and clicked the photo on index.htm, which led to
main.htm but can't navigate further except to the contact.html file, but from the
contact file, can find my way around the rest of the site.

Perhaps Frontpage 2000 itself has an issue (i.e. bug) with navigation bars in
shared borders.

I suggest you try a work-around and make a separate navigation page and use the
include content feature instead (or SSI if your host supports it). e.g. call
the navigation "nav_inc.html" (to specify it as an include page or to save
confusion - then insert it in each and every page you need the navigation on.
(this is the long way around the problem but probably will solve it in the long
run, and worth the extra work.). Using SSI you'll need to rename pages with
shtml extension.

However, one of the regulars on this group (Thomas Rowe....etc) might be able to
give their expert opinion on the shared borders/navigation bars issue.




Lucy said:
Thank you Andrew. It helped a little. My main page is not the home page,
that's why there's an Up link. My home (Index.html) has no borders, which is
what I want, but my main page should. and I can't get the bar to stay on that
page and athe others to. I look forward to more responses. take a look at it and
you'll see what I mean.
 
C

Crash Gordon®

The easiest way to understand it is to look at Navigation, and move your pages around there. Be forewarned, sometimes using fps navigation in shared borders will make you a little looney trying to figure it out. You just gotta mess around a little. Keep in mind you can have more than one navigation bar in a shared border this will help sometimes.

Personally, I think sometimes it's simpler to just do it manually in a included page (or several), a little more work initially but much easier to sort out.

hth.




| Thank you Andrew. It helped a little. My main page is not the home page, that's why there's an Up link. My home (Index.html) has no borders, which is what I want, but my main page should. and I can't get the bar to stay on that page and athe others to. I look forward to more responses. take a look at it and you'll see what I mean.
|
| "Andrew Murray" wrote:
|
| > I don't quite understand it much either but in simplified terms: using the
| > 'family' analogy below:
| >
| > Father (Home)
| >
| > John.htm Lucy.htm Jim.htm
| > Bob.htm
| > Hobbies.htm School.htm
| >
| >
| > Index is the PARENT page "John", "Lucy", "Jim" and "Bob" are the CHILD pages -
| > i.e. on the SAME LEVEL, Index is the level above them.
| >
| > Hobbies.htm and School.htm school are CHILD pages of "John" (and pattern follows
| > for the others)
| >
| > Anyway this is a simplified explanation. I hope someone else can verify or
| > explain further. Put simply it is just the system that Frontpage uses to link
| > pages to each other, and keep track if pages are removed etc and using the
| > 'recalculate hyperlinks' I suppose it rearranges the pages in the hierarchy.
| >
| > The navigation bars you insert have the page links and also "Up" and "Home" the
| > "Up" link goes to the parent page in the level above, so if you go "Up" from
| > hobbies.htm in the above example, you end up at John.htm.
| >
| > I hope this makes sense.
| >
| > The home page can't have an "Up" link because you're at the top level - after all
| > you can't go higher than the top storey of a building can you - think of it in
| > that context - the top level - literally is the TOP level.
| >
| > The Index.htm (frontpage calls it "home" and the navigation structure view
| > indicates this with a house icon) or whatever your server default is) is the top
| > page you can go to. So if you leave the nav bar as it is, all the pages should
| > have the correct links.
| >
| > | > > I'm using FP 2000. I have shared borders and navigation bar. My problem is I
| > don't really understand child, parent, same level pages. My navigation bar shows
| > correctly on all pages except my main page. When I make it show up on that page
| > the bars disappear on all the other pages. So I add another bar to my main page.
| > It shows up perfect in my previews, when I publish, there are two bars on every
| > page. Please help somebody! (www.friendshipmissionary.com).
| >
| >
| >
 
T

Thomas A. Rowe

The problem with using FP navigation component, is that it is always based on starting from the
site's home page (default document).

The only way to effective using a splash page with FP navigation components is to place the splash
page (default document) in the root of the web, then move the remaining content into a folder, then
convert the folder to a subweb, then reapply your theme and (re-)build you navigation structure in
the subweb. Use a absolute URL to and from the subweb.

This is only doable if the web host allow you to create subwebs, and some don't allow this.

--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)

FrontPage Resources, WebCircle, MS KB Quick Links, etc.
==============================================
 
Top