navigation, again, [heaaavvyy sighhhhh]

[judithbear]

OK, . Site first created some years ago with FP98. Has worked fine for years.
New computer using WXP HE, FP2003. Published remote site to local on new
machine.
Looks good on local and all links work as well. Server has all latest FP
extensions, however, it is a new Apache server.

I've been struggling with this for a while, you'll remember, I'm sure.

Online, the site: www.cancersurvivors.org shows the navigation links in
the top and left shared borders, however, instead of [home] and [up] it only
shows [up] and clicking it displays a "can't find msg".

I've tried everything you've suggested and in reading through all the other
Q&A in this GP I found this response to the same question posed by someone
else.

"Is it possible the site is on an Apache/UNIX server and that they just got
around to upgrading extensions which makes 98 unusable on an Apache/UNIX??"

Is there something intrinsically incompatible between Apache server w/the
latest FP extensions and a site originally generated on FP98. Even though
the site was generated on FP98, the "home" page when viewed in source
indicates it was generated in FP6,[which I think is FP2003] and the other
pages read as generated in FP3, [which I think is FP98]. Boy, they sure
don't make it easy for us non-computer guys, eh?

Does any of this provide enough information to solve my problem?

Sorry to be such a pest, but it's important to me that the information is
accessible. Most of the people I work with are newly diagnosed with cancer
and are in a panic mode anyway and I really don't want to add to their
frustration. I truly appreciate all the help you've given me to get this far.
TIA

 

[Ronx]

I can't shed any light on your problem, but the incompatibility is between
Unix FP2002 extensions and FrontPage98 program. An existing site should
work without problems when the server is upgraded, but using FP98 to edit
the site, or publish to the site, may be impossible.
Later versions of FrontPage will not have this editing/publish difficulty.

 

[Ronx]

Your home page is named default.htm (note the lower case "d" in default)
All the links to the home page that I looked at point to Default.htm (note
the UPPER case "D")

Unix is a case sensitive operating system - default.htm and Default.htm are
two different files as far as Unix is concerned, but the same file on
Windows.

In the local copy of your web you will have to rename Default.htm to
default.htm

This needs two steps:
In FrontPage with the web open,
1st - rename Default.htm to default.html
2nd - rename default.html to default.htm

The two steps are needed because Windows sees Default.htm and default.htm as
the same file, and will not allow the rename to take place.

You should also remove all spaces from file and folder names - some browsers
can't handle them.

Two FrontPage add-ins that might help with the renaming and spaces, both
obtainable from http://www.jimcoaddins.com/addins.aspx are the Space
Replacer and Case Changer, but using these may mean republishing the
entire web.

--
Ron

Reply only to group - emails will be deleted unread.

OK, . Site first created some years ago with FP98. Has worked fine for
years.
New computer using WXP HE, FP2003. Published remote site to local on new
machine.
Looks good on local and all links work as well. Server has all latest FP
extensions, however, it is a new Apache server.

I've been struggling with this for a while, you'll remember, I'm sure.

Online, the site: www.cancersurvivors.org shows the navigation links in
the top and left shared borders, however, instead of [home] and [up] it
only
shows [up] and clicking it displays a "can't find msg".

I've tried everything you've suggested and in reading through all the
other
Q&A in this GP I found this response to the same question posed by someone
else.

"Is it possible the site is on an Apache/UNIX server and that they just
got
around to upgrading extensions which makes 98 unusable on an
Apache/UNIX??"

Is there something intrinsically incompatible between Apache server w/the
latest FP extensions and a site originally generated on FP98. Even though
the site was generated on FP98, the "home" page when viewed in source
indicates it was generated in FP6,[which I think is FP2003] and the other
pages read as generated in FP3, [which I think is FP98]. Boy, they sure
don't make it easy for us non-computer guys, eh?

Does any of this provide enough information to solve my problem?

Sorry to be such a pest, but it's important to me that the information is
accessible. Most of the people I work with are newly diagnosed with cancer
and are in a panic mode anyway and I really don't want to add to their
frustration. I truly appreciate all the help you've given me to get this
far.
TIA

 

[Stefan B Rusynko]

It is a Case Problem
see http://www.cancersurvivors.org/default.htm




| Your home page is named default.htm (note the lower case "d" in default)
| All the links to the home page that I looked at point to Default.htm (note
| the UPPER case "D")
|
| Unix is a case sensitive operating system - default.htm and Default.htm are
| two different files as far as Unix is concerned, but the same file on
| Windows.
|
| In the local copy of your web you will have to rename Default.htm to
| default.htm
|
| This needs two steps:
| In FrontPage with the web open,
| 1st - rename Default.htm to default.html
| 2nd - rename default.html to default.htm
|
| The two steps are needed because Windows sees Default.htm and default.htm as
| the same file, and will not allow the rename to take place.
|
| You should also remove all spaces from file and folder names - some browsers
| can't handle them.
|
| Two FrontPage add-ins that might help with the renaming and spaces, both
| obtainable from http://www.jimcoaddins.com/addins.aspx are the Space
| Replacer and Case Changer, but using these may mean republishing the
| entire web.
|
| --
| Ron
|
| Reply only to group - emails will be deleted unread.
|
|
| | > OK, . Site first created some years ago with FP98. Has worked fine for
| > years.
| > New computer using WXP HE, FP2003. Published remote site to local on new
| > machine.
| > Looks good on local and all links work as well. Server has all latest FP
| > extensions, however, it is a new Apache server.
| >
| > I've been struggling with this for a while, you'll remember, I'm sure.
| >
| > Online, the site: www.cancersurvivors.org shows the navigation links in
| > the top and left shared borders, however, instead of [home] and [up] it
| > only
| > shows [up] and clicking it displays a "can't find msg".
| >
| > I've tried everything you've suggested and in reading through all the
| > other
| > Q&A in this GP I found this response to the same question posed by someone
| > else.
| >
| > "Is it possible the site is on an Apache/UNIX server and that they just
| > got
| > around to upgrading extensions which makes 98 unusable on an
| > Apache/UNIX??"
| >
| > Is there something intrinsically incompatible between Apache server w/the
| > latest FP extensions and a site originally generated on FP98. Even though
| > the site was generated on FP98, the "home" page when viewed in source
| > indicates it was generated in FP6,[which I think is FP2003] and the other
| > pages read as generated in FP3, [which I think is FP98]. Boy, they sure
| > don't make it easy for us non-computer guys, eh?
| >
| > Does any of this provide enough information to solve my problem?
| >
| > Sorry to be such a pest, but it's important to me that the information is
| > accessible. Most of the people I work with are newly diagnosed with cancer
| > and are in a panic mode anyway and I really don't want to add to their
| > frustration. I truly appreciate all the help you've given me to get this
| > far.
| > TIA
| >
| >
| > --
| > judith
|
|

 

[judithbear]

Ron, your response makes perfect sense to me, but as always there's a twist.
When I have the site open, not through FP, I see exactly the wording that
needs to be changed on each page. Default to default. However, when I open
the remote web through FP, or look at it on my local, those specific words
aren't there.

They are implied through a webot. The webot language is: <meta
name="Microsoft Border" content="tlb"> Now, logically, I would expect to see
the verbiage for this command in the _borders folders. The bottom border info
is in the folder, because it is not derived from a webot. The t/l border
files include this statement: [Add this page to the Navigation view to
display hyperlinks here] The code views for the left is: <!--webbot
bot="Navigation" s-type="children" s-orientation="vertical"
s-rendering="graphics" b-include-home="FALSE" b-include-up="FALSE" --> </p>
and for the top is: <!--webbot bot="Navigation" s-type="siblings"
s-orientation="horizontal" s-rendering="text" b-include-home="TRUE"
b-include-up="TRUE" --></small></td>

I don't know how to "add this page to the navigation view" I've tried
dragging and dropping and setting up link bars, etc, until I'm blue in the
face. I must be resisting the most simple advice. If someone could walk me
through that I would be ever grateful.

Secondly, when I open the remote site through FP, click on navigation view,
I see that there are in fact two top pages shown, each named
Cancer_Survivors_On_Line one in yellow which is linked with lines to the
entire site but for which the 'properties' option is greyed out so I can't
tell it's name; and one greyed out named default.htm which is off to the
left of the other, and linked to nothing. That logically seems to be the
problem. And is what you probably explained too me in your last post but I'm
just not getting it.

You indicated in your advice to make my changes in the locay copy of my web.
In the local copy, I do not have a page named Default.htm or Default.html.
It's default.htm And, in the navigation view there is only one top page and
it is correctly linked.

Dare I make the changes you suggested on the remote? And, again, on neither
the local nor the remote is there a folder in the folder view or folder pane
called Default.

Gosh, I'm so sorry to be taking up all this time and bandwidth. I feel so
foolish and pestering you all, I apologize for not being more clever. Once I
get this, I promise I'll never forget!

Your home page is named default.htm (note the lower case "d" in default)
All the links to the home page that I looked at point to Default.htm (note
the UPPER case "D")

Unix is a case sensitive operating system - default.htm and Default.htm are
two different files as far as Unix is concerned, but the same file on
Windows.

In the local copy of your web you will have to rename Default.htm to
default.htm

This needs two steps:
In FrontPage with the web open,
1st - rename Default.htm to default.html
2nd - rename default.html to default.htm

The two steps are needed because Windows sees Default.htm and default.htm as
the same file, and will not allow the rename to take place.

You should also remove all spaces from file and folder names - some browsers
can't handle them.

Two FrontPage add-ins that might help with the renaming and spaces, both
obtainable from http://www.jimcoaddins.com/addins.aspx are the Space
Replacer and Case Changer, but using these may mean republishing the
entire web.

--
Ron

Reply only to group - emails will be deleted unread.

OK, . Site first created some years ago with FP98. Has worked fine for
years.
New computer using WXP HE, FP2003. Published remote site to local on new
machine.
Looks good on local and all links work as well. Server has all latest FP
extensions, however, it is a new Apache server.

I've been struggling with this for a while, you'll remember, I'm sure.

Online, the site: www.cancersurvivors.org shows the navigation links in
the top and left shared borders, however, instead of [home] and [up] it
only
shows [up] and clicking it displays a "can't find msg".

I've tried everything you've suggested and in reading through all the
other
Q&A in this GP I found this response to the same question posed by someone
else.

"Is it possible the site is on an Apache/UNIX server and that they just
got
around to upgrading extensions which makes 98 unusable on an
Apache/UNIX??"

Is there something intrinsically incompatible between Apache server w/the
latest FP extensions and a site originally generated on FP98. Even though
the site was generated on FP98, the "home" page when viewed in source
indicates it was generated in FP6,[which I think is FP2003] and the other
pages read as generated in FP3, [which I think is FP98]. Boy, they sure
don't make it easy for us non-computer guys, eh?

Does any of this provide enough information to solve my problem?

Sorry to be such a pest, but it's important to me that the information is
accessible. Most of the people I work with are newly diagnosed with cancer
and are in a panic mode anyway and I really don't want to add to their
frustration. I truly appreciate all the help you've given me to get this
far.
TIA

 

[judithbear]

Yes, it causing some confusion. I understand that the name that is shown on
the blocks in navigation view is what I have named it and that the right
click/properties option should tell me the actual name of the file as the
computer will look for it. On the greyed out page in navigation view online
opened through my FP, I can click properties and see that the name of the
file is default.htm On the yellow page in the same view which is properly
linked the properties option is greyed out and I can't see what that page's
"real" name is. I would think that the folders view or folders pane would
show a page for each of the ones shown on the navigation view, but there is
only one default.htm shown. I know this is something incredibly simple, but
I'm truly stumped.

Hmmmm.

Navigation will display the page's Title, which is not necessarily what the name of the page file is named...maybe this is causing confusion for you.

In other words default.htm could display in Nav: My Wonderful Home Page.

hth


| Ron, your response makes perfect sense to me, but as always there's a twist.
| When I have the site open, not through FP, I see exactly the wording that
| needs to be changed on each page. Default to default. However, when I open
| the remote web through FP, or look at it on my local, those specific words
| aren't there.
|
| They are implied through a webot. The webot language is: <meta
| name="Microsoft Border" content="tlb"> Now, logically, I would expect to see
| the verbiage for this command in the _borders folders. The bottom border info
| is in the folder, because it is not derived from a webot. The t/l border
| files include this statement: [Add this page to the Navigation view to
| display hyperlinks here] The code views for the left is: <!--webbot
| bot="Navigation" s-type="children" s-orientation="vertical"
| s-rendering="graphics" b-include-home="FALSE" b-include-up="FALSE" --> </p>
| and for the top is: <!--webbot bot="Navigation" s-type="siblings"
| s-orientation="horizontal" s-rendering="text" b-include-home="TRUE"
| b-include-up="TRUE" --></small></td>
|
| I don't know how to "add this page to the navigation view" I've tried
| dragging and dropping and setting up link bars, etc, until I'm blue in the
| face. I must be resisting the most simple advice. If someone could walk me
| through that I would be ever grateful.
|
| Secondly, when I open the remote site through FP, click on navigation view,
| I see that there are in fact two top pages shown, each named
| Cancer_Survivors_On_Line one in yellow which is linked with lines to the
| entire site but for which the 'properties' option is greyed out so I can't
| tell it's name; and one greyed out named default.htm which is off to the
| left of the other, and linked to nothing. That logically seems to be the
| problem. And is what you probably explained too me in your last post but I'm
| just not getting it.
|
| You indicated in your advice to make my changes in the locay copy of my web.
| In the local copy, I do not have a page named Default.htm or Default.html.
| It's default.htm And, in the navigation view there is only one top page and
| it is correctly linked.
|
| Dare I make the changes you suggested on the remote? And, again, on neither
| the local nor the remote is there a folder in the folder view or folder pane
| called Default.
|
| Gosh, I'm so sorry to be taking up all this time and bandwidth. I feel so
| foolish and pestering you all, I apologize for not being more clever. Once I
| get this, I promise I'll never forget!
|
|
|
| "Ronx" wrote:
|
| > Your home page is named default.htm (note the lower case "d" in default)
| > All the links to the home page that I looked at point to Default.htm (note
| > the UPPER case "D")
| >
| > Unix is a case sensitive operating system - default.htm and Default.htm are
| > two different files as far as Unix is concerned, but the same file on
| > Windows.
| >
| > In the local copy of your web you will have to rename Default.htm to
| > default.htm
| >
| > This needs two steps:
| > In FrontPage with the web open,
| > 1st - rename Default.htm to default.html
| > 2nd - rename default.html to default.htm
| >
| > The two steps are needed because Windows sees Default.htm and default.htm as
| > the same file, and will not allow the rename to take place.
| >
| > You should also remove all spaces from file and folder names - some browsers
| > can't handle them.
| >
| > Two FrontPage add-ins that might help with the renaming and spaces, both
| > obtainable from http://www.jimcoaddins.com/addins.aspx are the Space
| > Replacer and Case Changer, but using these may mean republishing the
| > entire web.
| >
| > --
| > Ron
| >
| > Reply only to group - emails will be deleted unread.
| >
| >
| > | > > OK, . Site first created some years ago with FP98. Has worked fine for
| > > years.
| > > New computer using WXP HE, FP2003. Published remote site to local on new
| > > machine.
| > > Looks good on local and all links work as well. Server has all latest FP
| > > extensions, however, it is a new Apache server.
| > >
| > > I've been struggling with this for a while, you'll remember, I'm sure.
| > >
| > > Online, the site: www.cancersurvivors.org shows the navigation links in
| > > the top and left shared borders, however, instead of [home] and [up] it
| > > only
| > > shows [up] and clicking it displays a "can't find msg".
| > >
| > > I've tried everything you've suggested and in reading through all the
| > > other
| > > Q&A in this GP I found this response to the same question posed by someone
| > > else.
| > >
| > > "Is it possible the site is on an Apache/UNIX server and that they just
| > > got
| > > around to upgrading extensions which makes 98 unusable on an
| > > Apache/UNIX??"
| > >
| > > Is there something intrinsically incompatible between Apache server w/the
| > > latest FP extensions and a site originally generated on FP98. Even though
| > > the site was generated on FP98, the "home" page when viewed in source
| > > indicates it was generated in FP6,[which I think is FP2003] and the other
| > > pages read as generated in FP3, [which I think is FP98]. Boy, they sure
| > > don't make it easy for us non-computer guys, eh?
| > >
| > > Does any of this provide enough information to solve my problem?
| > >
| > > Sorry to be such a pest, but it's important to me that the information is
| > > accessible. Most of the people I work with are newly diagnosed with cancer
| > > and are in a panic mode anyway and I really don't want to add to their
| > > frustration. I truly appreciate all the help you've given me to get this
| > > far.
| > > TIA
| > >
| > >
| > > --
| > > judith
| >
| >
| >

 

[Ronx]

Comments inline below

--
Ron

Reply only to group - emails will be deleted unread.

Ron, your response makes perfect sense to me, but as always there's a
twist.
When I have the site open, not through FP, I see exactly the wording that
needs to be changed on each page. Default to default. However, when I open
the remote web through FP, or look at it on my local, those specific words
aren't there.

They are implied through a webot. The webot language is: <meta
name="Microsoft Border" content="tlb"> Now, logically, I would expect to
see
the verbiage for this command in the _borders folders. The bottom border
info
is in the folder, because it is not derived from a webot. The t/l border
files include this statement: [Add this page to the Navigation view to
display hyperlinks here] The code views for the left is: <!--webbot
bot="Navigation" s-type="children" s-orientation="vertical"
s-rendering="graphics" b-include-home="FALSE" b-include-up="FALSE" -->
</p>
and for the top is: <!--webbot bot="Navigation" s-type="siblings"
s-orientation="horizontal" s-rendering="text" b-include-home="TRUE"
b-include-up="TRUE" --></small></td>

I don't know how to "add this page to the navigation view" I've tried
dragging and dropping and setting up link bars, etc, until I'm blue in the
face. I must be resisting the most simple advice. If someone could walk me
through that I would be ever grateful.

There is no need to add the border pages to the navigation. The code you
quoted is what I would expect to be there. When the borders are added to
the pages using them, the webbot code is expanded into the Navigation Bar.
Changing anything in the Nav bars will not help (and you can't change them
through HTML anyway).

Secondly, when I open the remote site through FP, click on navigation
view,
I see that there are in fact two top pages shown, each named
Cancer_Survivors_On_Line one in yellow which is linked with lines to the
entire site but for which the 'properties' option is greyed out so I can't
tell it's name; and one greyed out named default.htm which is off to the
left of the other, and linked to nothing. That logically seems to be the
problem. And is what you probably explained too me in your last post but
I'm
just not getting it.

It's not quite what I attempted to explain, but it does explain a lot!

The greyed out object is the default.htm and has been excluded from the link
bars.
Right-click on the grey box, and click "Included in Link Bars". This should
turn it yellow, and your Home page links should come to life on the pages.
Then drag all the links from the mystery yellow box over to the default.htm.
Finally, Tools-> Recalculate Hyperlinks.

It seems that the navigation has become corrupt (the mystery box that has
taken over the home page: I guess that this is a "phantom" page named
Default.htm), so this exercise may cure it, or fail.

You indicated in your advice to make my changes in the locay copy of my
web.
In the local copy, I do not have a page named Default.htm or Default.html.
It's default.htm And, in the navigation view there is only one top page
and
it is correctly linked.

Ignore my advise, for the time being.

Dare I make the changes you suggested on the remote?

See above regarding grey boxes and mysteries.

And, again, on neither
the local nor the remote is there a folder in the folder view or folder
pane
called Default.

There is no need for such a folder.

Gosh, I'm so sorry to be taking up all this time and bandwidth. I feel so
foolish and pestering you all, I apologize for not being more clever. Once
I
get this, I promise I'll never forget!

Knowledge is the key, and one way to gain knowledge is by asking questions.

Your home page is named default.htm (note the lower case "d" in
default)
All the links to the home page that I looked at point to Default.htm
(note
the UPPER case "D")

Unix is a case sensitive operating system - default.htm and Default.htm
are
two different files as far as Unix is concerned, but the same file on
Windows.

In the local copy of your web you will have to rename Default.htm to
default.htm

This needs two steps:
In FrontPage with the web open,
1st - rename Default.htm to default.html
2nd - rename default.html to default.htm

The two steps are needed because Windows sees Default.htm and default.htm
as
the same file, and will not allow the rename to take place.

You should also remove all spaces from file and folder names - some
browsers
can't handle them.

Two FrontPage add-ins that might help with the renaming and spaces, both
obtainable from http://www.jimcoaddins.com/addins.aspx are the Space
Replacer and Case Changer, but using these may mean republishing the
entire web.

--
Ron

Reply only to group - emails will be deleted unread.

OK, . Site first created some years ago with FP98. Has worked fine for
years.
New computer using WXP HE, FP2003. Published remote site to local on
new
machine.
Looks good on local and all links work as well. Server has all latest
FP
extensions, however, it is a new Apache server.

I've been struggling with this for a while, you'll remember, I'm sure.

Online, the site: www.cancersurvivors.org shows the navigation links
in
the top and left shared borders, however, instead of [home] and [up] it
only
shows [up] and clicking it displays a "can't find msg".

I've tried everything you've suggested and in reading through all the
other
Q&A in this GP I found this response to the same question posed by
someone
else.

"Is it possible the site is on an Apache/UNIX server and that they just
got
around to upgrading extensions which makes 98 unusable on an
Apache/UNIX??"

Is there something intrinsically incompatible between Apache server
w/the
latest FP extensions and a site originally generated on FP98. Even
though
the site was generated on FP98, the "home" page when viewed in source
indicates it was generated in FP6,[which I think is FP2003] and the
other
pages read as generated in FP3, [which I think is FP98]. Boy, they
sure
don't make it easy for us non-computer guys, eh?

Does any of this provide enough information to solve my problem?

Sorry to be such a pest, but it's important to me that the information
is
accessible. Most of the people I work with are newly diagnosed with
cancer
and are in a panic mode anyway and I really don't want to add to their
frustration. I truly appreciate all the help you've given me to get
this
far.
TIA

 

[judithbear]

It worked!!!!!! Logically I thought that was the problem, but didn't know the
process to change it. I also knew that I was trying to make it much more
complicated than it was, as is my wont.

Thank you, Ron, and all else who helped me on this. I am so grateful. I
could crawl through the site and give you all a hug, but, well, you know.....

Thanks again.

Comments inline below

--
Ron

Reply only to group - emails will be deleted unread.

Ron, your response makes perfect sense to me, but as always there's a
twist.
When I have the site open, not through FP, I see exactly the wording that
needs to be changed on each page. Default to default. However, when I open
the remote web through FP, or look at it on my local, those specific words
aren't there.

They are implied through a webot. The webot language is: <meta
name="Microsoft Border" content="tlb"> Now, logically, I would expect to
see
the verbiage for this command in the _borders folders. The bottom border
info
is in the folder, because it is not derived from a webot. The t/l border
files include this statement: [Add this page to the Navigation view to
display hyperlinks here] The code views for the left is: <!--webbot
bot="Navigation" s-type="children" s-orientation="vertical"
s-rendering="graphics" b-include-home="FALSE" b-include-up="FALSE" -->
</p>
and for the top is: <!--webbot bot="Navigation" s-type="siblings"
s-orientation="horizontal" s-rendering="text" b-include-home="TRUE"
b-include-up="TRUE" --></small></td>

I don't know how to "add this page to the navigation view" I've tried
dragging and dropping and setting up link bars, etc, until I'm blue in the
face. I must be resisting the most simple advice. If someone could walk me
through that I would be ever grateful.

There is no need to add the border pages to the navigation. The code you
quoted is what I would expect to be there. When the borders are added to
the pages using them, the webbot code is expanded into the Navigation Bar.
Changing anything in the Nav bars will not help (and you can't change them
through HTML anyway).

Secondly, when I open the remote site through FP, click on navigation
view,
I see that there are in fact two top pages shown, each named
Cancer_Survivors_On_Line one in yellow which is linked with lines to the
entire site but for which the 'properties' option is greyed out so I can't
tell it's name; and one greyed out named default.htm which is off to the
left of the other, and linked to nothing. That logically seems to be the
problem. And is what you probably explained too me in your last post but
I'm
just not getting it.

It's not quite what I attempted to explain, but it does explain a lot!

The greyed out object is the default.htm and has been excluded from the link
bars.
Right-click on the grey box, and click "Included in Link Bars". This should
turn it yellow, and your Home page links should come to life on the pages.
Then drag all the links from the mystery yellow box over to the default.htm.
Finally, Tools-> Recalculate Hyperlinks.

It seems that the navigation has become corrupt (the mystery box that has
taken over the home page: I guess that this is a "phantom" page named
Default.htm), so this exercise may cure it, or fail.

You indicated in your advice to make my changes in the locay copy of my
web.
In the local copy, I do not have a page named Default.htm or Default.html.
It's default.htm And, in the navigation view there is only one top page
and
it is correctly linked.

Ignore my advise, for the time being.

Dare I make the changes you suggested on the remote?

See above regarding grey boxes and mysteries.

And, again, on neither
the local nor the remote is there a folder in the folder view or folder
pane
called Default.

There is no need for such a folder.

Gosh, I'm so sorry to be taking up all this time and bandwidth. I feel so
foolish and pestering you all, I apologize for not being more clever. Once
I
get this, I promise I'll never forget!

Knowledge is the key, and one way to gain knowledge is by asking questions.

Your home page is named default.htm (note the lower case "d" in
default)
All the links to the home page that I looked at point to Default.htm
(note
the UPPER case "D")

Unix is a case sensitive operating system - default.htm and Default.htm
are
two different files as far as Unix is concerned, but the same file on
Windows.

In the local copy of your web you will have to rename Default.htm to
default.htm

This needs two steps:
In FrontPage with the web open,
1st - rename Default.htm to default.html
2nd - rename default.html to default.htm

The two steps are needed because Windows sees Default.htm and default.htm
as
the same file, and will not allow the rename to take place.

You should also remove all spaces from file and folder names - some
browsers
can't handle them.

Two FrontPage add-ins that might help with the renaming and spaces, both
obtainable from http://www.jimcoaddins.com/addins.aspx are the Space
Replacer and Case Changer, but using these may mean republishing the
entire web.

--
Ron

Reply only to group - emails will be deleted unread.


OK, . Site first created some years ago with FP98. Has worked fine for
years.
New computer using WXP HE, FP2003. Published remote site to local on
new
machine.
Looks good on local and all links work as well. Server has all latest
FP
extensions, however, it is a new Apache server.

I've been struggling with this for a while, you'll remember, I'm sure.

Online, the site: www.cancersurvivors.org shows the navigation links
in
the top and left shared borders, however, instead of [home] and [up] it
only
shows [up] and clicking it displays a "can't find msg".

I've tried everything you've suggested and in reading through all the
other
Q&A in this GP I found this response to the same question posed by
someone
else.

"Is it possible the site is on an Apache/UNIX server and that they just
got
around to upgrading extensions which makes 98 unusable on an
Apache/UNIX??"

Is there something intrinsically incompatible between Apache server
w/the
latest FP extensions and a site originally generated on FP98. Even
though
the site was generated on FP98, the "home" page when viewed in source
indicates it was generated in FP6,[which I think is FP2003] and the
other
pages read as generated in FP3, [which I think is FP98]. Boy, they
sure
don't make it easy for us non-computer guys, eh?

Does any of this provide enough information to solve my problem?

Sorry to be such a pest, but it's important to me that the information
is
accessible. Most of the people I work with are newly diagnosed with
cancer
and are in a panic mode anyway and I really don't want to add to their
frustration. I truly appreciate all the help you've given me to get
this
far.
TIA

 

[judithbear]

Oh, BTW, what should I do with that mystery box or phantom page now that it's
unlinked...should I delete it? Will it cause any trouble just to leave it
hanging there. [I'm kinda timid about deleting things now that it's working
well again LOL]

Comments inline below

--
Ron

Reply only to group - emails will be deleted unread.

Ron, your response makes perfect sense to me, but as always there's a
twist.
When I have the site open, not through FP, I see exactly the wording that
needs to be changed on each page. Default to default. However, when I open
the remote web through FP, or look at it on my local, those specific words
aren't there.

They are implied through a webot. The webot language is: <meta
name="Microsoft Border" content="tlb"> Now, logically, I would expect to
see
the verbiage for this command in the _borders folders. The bottom border
info
is in the folder, because it is not derived from a webot. The t/l border
files include this statement: [Add this page to the Navigation view to
display hyperlinks here] The code views for the left is: <!--webbot
bot="Navigation" s-type="children" s-orientation="vertical"
s-rendering="graphics" b-include-home="FALSE" b-include-up="FALSE" -->
</p>
and for the top is: <!--webbot bot="Navigation" s-type="siblings"
s-orientation="horizontal" s-rendering="text" b-include-home="TRUE"
b-include-up="TRUE" --></small></td>

I don't know how to "add this page to the navigation view" I've tried
dragging and dropping and setting up link bars, etc, until I'm blue in the
face. I must be resisting the most simple advice. If someone could walk me
through that I would be ever grateful.

There is no need to add the border pages to the navigation. The code you
quoted is what I would expect to be there. When the borders are added to
the pages using them, the webbot code is expanded into the Navigation Bar.
Changing anything in the Nav bars will not help (and you can't change them
through HTML anyway).

Secondly, when I open the remote site through FP, click on navigation
view,
I see that there are in fact two top pages shown, each named
Cancer_Survivors_On_Line one in yellow which is linked with lines to the
entire site but for which the 'properties' option is greyed out so I can't
tell it's name; and one greyed out named default.htm which is off to the
left of the other, and linked to nothing. That logically seems to be the
problem. And is what you probably explained too me in your last post but
I'm
just not getting it.

It's not quite what I attempted to explain, but it does explain a lot!

The greyed out object is the default.htm and has been excluded from the link
bars.
Right-click on the grey box, and click "Included in Link Bars". This should
turn it yellow, and your Home page links should come to life on the pages.
Then drag all the links from the mystery yellow box over to the default.htm.
Finally, Tools-> Recalculate Hyperlinks.

It seems that the navigation has become corrupt (the mystery box that has
taken over the home page: I guess that this is a "phantom" page named
Default.htm), so this exercise may cure it, or fail.

You indicated in your advice to make my changes in the locay copy of my
web.
In the local copy, I do not have a page named Default.htm or Default.html.
It's default.htm And, in the navigation view there is only one top page
and
it is correctly linked.

Ignore my advise, for the time being.

Dare I make the changes you suggested on the remote?

See above regarding grey boxes and mysteries.

And, again, on neither
the local nor the remote is there a folder in the folder view or folder
pane
called Default.

There is no need for such a folder.

Gosh, I'm so sorry to be taking up all this time and bandwidth. I feel so
foolish and pestering you all, I apologize for not being more clever. Once
I
get this, I promise I'll never forget!

Knowledge is the key, and one way to gain knowledge is by asking questions.

Your home page is named default.htm (note the lower case "d" in
default)
All the links to the home page that I looked at point to Default.htm
(note
the UPPER case "D")

Unix is a case sensitive operating system - default.htm and Default.htm
are
two different files as far as Unix is concerned, but the same file on
Windows.

In the local copy of your web you will have to rename Default.htm to
default.htm

This needs two steps:
In FrontPage with the web open,
1st - rename Default.htm to default.html
2nd - rename default.html to default.htm

The two steps are needed because Windows sees Default.htm and default.htm
as
the same file, and will not allow the rename to take place.

You should also remove all spaces from file and folder names - some
browsers
can't handle them.

Two FrontPage add-ins that might help with the renaming and spaces, both
obtainable from http://www.jimcoaddins.com/addins.aspx are the Space
Replacer and Case Changer, but using these may mean republishing the
entire web.

--
Ron

Reply only to group - emails will be deleted unread.


OK, . Site first created some years ago with FP98. Has worked fine for
years.
New computer using WXP HE, FP2003. Published remote site to local on
new
machine.
Looks good on local and all links work as well. Server has all latest
FP
extensions, however, it is a new Apache server.

I've been struggling with this for a while, you'll remember, I'm sure.

Online, the site: www.cancersurvivors.org shows the navigation links
in
the top and left shared borders, however, instead of [home] and [up] it
only
shows [up] and clicking it displays a "can't find msg".

I've tried everything you've suggested and in reading through all the
other
Q&A in this GP I found this response to the same question posed by
someone
else.

"Is it possible the site is on an Apache/UNIX server and that they just
got
around to upgrading extensions which makes 98 unusable on an
Apache/UNIX??"

Is there something intrinsically incompatible between Apache server
w/the
latest FP extensions and a site originally generated on FP98. Even
though
the site was generated on FP98, the "home" page when viewed in source
indicates it was generated in FP6,[which I think is FP2003] and the
other
pages read as generated in FP3, [which I think is FP98]. Boy, they
sure
don't make it easy for us non-computer guys, eh?

Does any of this provide enough information to solve my problem?

Sorry to be such a pest, but it's important to me that the information
is
accessible. Most of the people I work with are newly diagnosed with
cancer
and are in a panic mode anyway and I really don't want to add to their
frustration. I truly appreciate all the help you've given me to get
this
far.
TIA

 

[Ronx]

If the pages are working properly I am tempted to use the old adage "If it
ain't broke, don't fix it".

However, it might cause trouble later on, at the next update perhaps. You
could try to delete it (just delete from navigation view, not the page
itself)- if it goes, that's good - or wait for the next update that changes
the navigation, which might kill it off.

--
Ron

Reply only to group - emails will be deleted unread.

Oh, BTW, what should I do with that mystery box or phantom page now that
it's
unlinked...should I delete it? Will it cause any trouble just to leave it
hanging there. [I'm kinda timid about deleting things now that it's
working
well again LOL]

Comments inline below

--
Ron

Reply only to group - emails will be deleted unread.

Ron, your response makes perfect sense to me, but as always there's a
twist.
When I have the site open, not through FP, I see exactly the wording
that
needs to be changed on each page. Default to default. However, when I
open
the remote web through FP, or look at it on my local, those specific
words
aren't there.

They are implied through a webot. The webot language is: <meta
name="Microsoft Border" content="tlb"> Now, logically, I would expect
to
see
the verbiage for this command in the _borders folders. The bottom
border
info
is in the folder, because it is not derived from a webot. The t/l
border
files include this statement: [Add this page to the Navigation view to
display hyperlinks here] The code views for the left is: <!--webbot
bot="Navigation" s-type="children" s-orientation="vertical"
s-rendering="graphics" b-include-home="FALSE" b-include-up="FALSE" -->
</p>
and for the top is: <!--webbot bot="Navigation" s-type="siblings"
s-orientation="horizontal" s-rendering="text" b-include-home="TRUE"
b-include-up="TRUE" --></small></td>

I don't know how to "add this page to the navigation view" I've tried
dragging and dropping and setting up link bars, etc, until I'm blue in
the
face. I must be resisting the most simple advice. If someone could walk
me
through that I would be ever grateful.

There is no need to add the border pages to the navigation. The code you
quoted is what I would expect to be there. When the borders are added to
the pages using them, the webbot code is expanded into the Navigation
Bar.
Changing anything in the Nav bars will not help (and you can't change
them
through HTML anyway).

Secondly, when I open the remote site through FP, click on navigation
view,
I see that there are in fact two top pages shown, each named
Cancer_Survivors_On_Line one in yellow which is linked with lines to
the
entire site but for which the 'properties' option is greyed out so I
can't
tell it's name; and one greyed out named default.htm which is off to
the
left of the other, and linked to nothing. That logically seems to be
the
problem. And is what you probably explained too me in your last post
but
I'm
just not getting it.

It's not quite what I attempted to explain, but it does explain a lot!

The greyed out object is the default.htm and has been excluded from the
link
bars.
Right-click on the grey box, and click "Included in Link Bars". This
should
turn it yellow, and your Home page links should come to life on the
pages.
Then drag all the links from the mystery yellow box over to the
default.htm.
Finally, Tools-> Recalculate Hyperlinks.

It seems that the navigation has become corrupt (the mystery box that has
taken over the home page: I guess that this is a "phantom" page named
Default.htm), so this exercise may cure it, or fail.

You indicated in your advice to make my changes in the locay copy of my
web.
In the local copy, I do not have a page named Default.htm or
Default.html.
It's default.htm And, in the navigation view there is only one top
page
and
it is correctly linked.

Ignore my advise, for the time being.

Dare I make the changes you suggested on the remote?

See above regarding grey boxes and mysteries.

And, again, on neither
the local nor the remote is there a folder in the folder view or folder
pane
called Default.

There is no need for such a folder.

Gosh, I'm so sorry to be taking up all this time and bandwidth. I feel
so
foolish and pestering you all, I apologize for not being more clever.
Once
I
get this, I promise I'll never forget!

Knowledge is the key, and one way to gain knowledge is by asking
questions.

:

Your home page is named default.htm (note the lower case "d" in
default)
All the links to the home page that I looked at point to Default.htm
(note
the UPPER case "D")

Unix is a case sensitive operating system - default.htm and
Default.htm
are
two different files as far as Unix is concerned, but the same file on
Windows.

In the local copy of your web you will have to rename Default.htm to
default.htm

This needs two steps:
In FrontPage with the web open,
1st - rename Default.htm to default.html
2nd - rename default.html to default.htm

The two steps are needed because Windows sees Default.htm and
default.htm
as
the same file, and will not allow the rename to take place.

You should also remove all spaces from file and folder names - some
browsers
can't handle them.

Two FrontPage add-ins that might help with the renaming and spaces,
both
obtainable from http://www.jimcoaddins.com/addins.aspx are the Space
Replacer and Case Changer, but using these may mean republishing
the
entire web.

--
Ron

Reply only to group - emails will be deleted unread.


OK, . Site first created some years ago with FP98. Has worked fine
for
years.
New computer using WXP HE, FP2003. Published remote site to local
on
new
machine.
Looks good on local and all links work as well. Server has all
latest
FP
extensions, however, it is a new Apache server.

I've been struggling with this for a while, you'll remember, I'm
sure.

Online, the site: www.cancersurvivors.org shows the navigation
links
in
the top and left shared borders, however, instead of [home] and [up]
it
only
shows [up] and clicking it displays a "can't find msg".

I've tried everything you've suggested and in reading through all
the
other
Q&A in this GP I found this response to the same question posed by
someone
else.

"Is it possible the site is on an Apache/UNIX server and that they
just
got
around to upgrading extensions which makes 98 unusable on an
Apache/UNIX??"

Is there something intrinsically incompatible between Apache server
w/the
latest FP extensions and a site originally generated on FP98. Even
though
the site was generated on FP98, the "home" page when viewed in
source
indicates it was generated in FP6,[which I think is FP2003] and the
other
pages read as generated in FP3, [which I think is FP98]. Boy, they
sure
don't make it easy for us non-computer guys, eh?

Does any of this provide enough information to solve my problem?

Sorry to be such a pest, but it's important to me that the
information
is
accessible. Most of the people I work with are newly diagnosed with
cancer
and are in a panic mode anyway and I really don't want to add to
their
frustration. I truly appreciate all the help you've given me to get
this
far.
TIA

 

[judithbear]

Good advice, as always. Thank you so much.

If the pages are working properly I am tempted to use the old adage "If it
ain't broke, don't fix it".

However, it might cause trouble later on, at the next update perhaps. You
could try to delete it (just delete from navigation view, not the page
itself)- if it goes, that's good - or wait for the next update that changes
the navigation, which might kill it off.

--
Ron

Reply only to group - emails will be deleted unread.

Oh, BTW, what should I do with that mystery box or phantom page now that
it's
unlinked...should I delete it? Will it cause any trouble just to leave it
hanging there. [I'm kinda timid about deleting things now that it's
working
well again LOL]

Comments inline below

--
Ron

Reply only to group - emails will be deleted unread.


Ron, your response makes perfect sense to me, but as always there's a
twist.
When I have the site open, not through FP, I see exactly the wording
that
needs to be changed on each page. Default to default. However, when I
open
the remote web through FP, or look at it on my local, those specific
words
aren't there.

They are implied through a webot. The webot language is: <meta
name="Microsoft Border" content="tlb"> Now, logically, I would expect
to
see
the verbiage for this command in the _borders folders. The bottom
border
info
is in the folder, because it is not derived from a webot. The t/l
border
files include this statement: [Add this page to the Navigation view to
display hyperlinks here] The code views for the left is: <!--webbot
bot="Navigation" s-type="children" s-orientation="vertical"
s-rendering="graphics" b-include-home="FALSE" b-include-up="FALSE" -->
</p>
and for the top is: <!--webbot bot="Navigation" s-type="siblings"
s-orientation="horizontal" s-rendering="text" b-include-home="TRUE"
b-include-up="TRUE" --></small></td>

I don't know how to "add this page to the navigation view" I've tried
dragging and dropping and setting up link bars, etc, until I'm blue in
the
face. I must be resisting the most simple advice. If someone could walk
me
through that I would be ever grateful.

There is no need to add the border pages to the navigation. The code you
quoted is what I would expect to be there. When the borders are added to
the pages using them, the webbot code is expanded into the Navigation
Bar.
Changing anything in the Nav bars will not help (and you can't change
them
through HTML anyway).


Secondly, when I open the remote site through FP, click on navigation
view,
I see that there are in fact two top pages shown, each named
Cancer_Survivors_On_Line one in yellow which is linked with lines to
the
entire site but for which the 'properties' option is greyed out so I
can't
tell it's name; and one greyed out named default.htm which is off to
the
left of the other, and linked to nothing. That logically seems to be
the
problem. And is what you probably explained too me in your last post
but
I'm
just not getting it.

It's not quite what I attempted to explain, but it does explain a lot!

The greyed out object is the default.htm and has been excluded from the
link
bars.
Right-click on the grey box, and click "Included in Link Bars". This
should
turn it yellow, and your Home page links should come to life on the
pages.
Then drag all the links from the mystery yellow box over to the
default.htm.
Finally, Tools-> Recalculate Hyperlinks.

It seems that the navigation has become corrupt (the mystery box that has
taken over the home page: I guess that this is a "phantom" page named
Default.htm), so this exercise may cure it, or fail.


You indicated in your advice to make my changes in the locay copy of my
web.
In the local copy, I do not have a page named Default.htm or
Default.html.
It's default.htm And, in the navigation view there is only one top
page
and
it is correctly linked.

Ignore my advise, for the time being.


Dare I make the changes you suggested on the remote?

See above regarding grey boxes and mysteries.

And, again, on neither
the local nor the remote is there a folder in the folder view or folder
pane
called Default.

There is no need for such a folder.


Gosh, I'm so sorry to be taking up all this time and bandwidth. I feel
so
foolish and pestering you all, I apologize for not being more clever.
Once
I
get this, I promise I'll never forget!



Knowledge is the key, and one way to gain knowledge is by asking
questions.




:

Your home page is named default.htm (note the lower case "d" in
default)
All the links to the home page that I looked at point to Default.htm
(note
the UPPER case "D")

Unix is a case sensitive operating system - default.htm and
Default.htm
are
two different files as far as Unix is concerned, but the same file on
Windows.

In the local copy of your web you will have to rename Default.htm to
default.htm

This needs two steps:
In FrontPage with the web open,
1st - rename Default.htm to default.html
2nd - rename default.html to default.htm

The two steps are needed because Windows sees Default.htm and
default.htm
as
the same file, and will not allow the rename to take place.

You should also remove all spaces from file and folder names - some
browsers
can't handle them.

Two FrontPage add-ins that might help with the renaming and spaces,
both
obtainable from http://www.jimcoaddins.com/addins.aspx are the Space
Replacer and Case Changer, but using these may mean republishing
the
entire web.

--
Ron

Reply only to group - emails will be deleted unread.


OK, . Site first created some years ago with FP98. Has worked fine
for
years.
New computer using WXP HE, FP2003. Published remote site to local
on
new
machine.
Looks good on local and all links work as well. Server has all
latest
FP
extensions, however, it is a new Apache server.

I've been struggling with this for a while, you'll remember, I'm
sure.

Online, the site: www.cancersurvivors.org shows the navigation
links
in
the top and left shared borders, however, instead of [home] and [up]
it
only
shows [up] and clicking it displays a "can't find msg".

I've tried everything you've suggested and in reading through all
the
other
Q&A in this GP I found this response to the same question posed by
someone
else.

"Is it possible the site is on an Apache/UNIX server and that they
just
got
around to upgrading extensions which makes 98 unusable on an
Apache/UNIX??"

Is there something intrinsically incompatible between Apache server
w/the
latest FP extensions and a site originally generated on FP98. Even
though
the site was generated on FP98, the "home" page when viewed in
source
indicates it was generated in FP6,[which I think is FP2003] and the
other
pages read as generated in FP3, [which I think is FP98]. Boy, they
sure
don't make it easy for us non-computer guys, eh?

Does any of this provide enough information to solve my problem?

Sorry to be such a pest, but it's important to me that the
information
is
accessible. Most of the people I work with are newly diagnosed with
cancer
and are in a panic mode anyway and I really don't want to add to
their
frustration. I truly appreciate all the help you've given me to get
this
far.
TIA