Non existent user

[Steve Jones]

Hi,

I have been using FP 2000 for years without any major problems but
have now come across something that has me puzzled.

I manage a site for my workplace that has grown over the years and I
have started using sub webs to make things easier. Creating a link
back from the sub web to the main website is simple enough but last
week I lost all the navigational structures and had to republish. This
is where my troubles began.

First, no matter what I call my main page, be it index, home,
default.asp (a name FP sometimes insists calling home.htm) the link
back from the sub web fails after I upload to the ISP's server. It
exists and works on my local machine without problems but returns an
error 404 otherwise.

Second, when trying to republish FP will warn me that such a page has
been changed by SARTRE on <date> at <time>. This sometimes refers to
a page I know *hasn't* been altered in months if not years. FP may
also indicate that a page has been changed when no one can possible be
in the building ie at weekend.

I can overcome this by overwritng files but the entire site can take
over 1 hour to transfer all files using a DSL connection. Even then I
wil not be sure if all navigation bars have been reinstated.

Any ideas on a course of action gratefully received.

 

[Jim Buyens]

-----Original Message-----

Hi,
Howdy.

I have been using FP 2000 for years without any major
problems but have now come across something that has me
puzzled.

I manage a site for my workplace that has grown over
the years and I have started using sub webs to make
things easier. Creating a link back from the sub web to
the main website is simple enough but last week I lost
all the navigational structures and had to republish. This
is where my troubles began.

First, no matter what I call my main page, be it index,
home, default.asp (a name FP sometimes insists calling
home.htm) the link back from the sub web fails after I
upload to the ISP's server. It exists and works on my
local machine without problems but returns an error 404
otherwise.

Is FrontPage renaming your home page as it publishes?

This can happen if, for example, the home page in a local
disk-based Web is index.htm, but the default document name
on the remote Web server is default.htm. In that case,
FrontPage will rename the home page as it publishes.

However, FrontPage will *not* correct any links within
subwebs, and this can create broken links.

The solution is usually to build your links with the
filenames that will exist on the server, and ignore any
broken links of that type that you encounter locally.

Another solution is to use a local Web sever for
development, and set its default document name to match
that on the remote (live) server.

Second, when trying to republish FP will warn me that
such a page has been changed by SARTRE on <date> at
<time>. This sometimes refers to a page I know *hasn't*
been altered in months if not years. FP may also
indicate that a page has been changed when no one can
possible be in the building ie at weekend.

I can overcome this by overwriting files but the entire
site can take over 1 hour to transfer all files using a
DSL connection. Even then I will not be sure if all
navigation bars have been reinstated.

Any ideas on a course of action gratefully received.

First, if your site takes over an hour to publish via DSL,
you need more and smaller subwebs.

As to SARTRE, I'd certainly open a few of those pages
directly on the server and look for signs of tampering,
especially if the date in the message is recent.

You might also want to try the advice at:

FrontPage Publish Command Fails
http://www.interlacken.com/winnt/tips/tipshow.aspx?tip=24

Jim Buyens
Microsoft FrontPage MVP
http://www.interlacken.com
Author of:
*----------------------------------------------------
|\---------------------------------------------------
|| Microsoft Office FrontPage 2003 Inside Out
||---------------------------------------------------
|| Web Database Development Step by Step .NET Edition
|| Microsoft FrontPage Version 2002 Inside Out
|| Faster Smarter Beginning Programming
|| (All from Microsoft Press)
|/---------------------------------------------------
*----------------------------------------------------

 

[Steve Jones]

Is FrontPage renaming your home page as it publishes?

Yes it is. If I name the home page home.htm then FP will publish as
default.htm. What I have done is republish but the link from the
subweb back to the home page presents no page at all or the home page
sans navigation bars. I added a relative link locally and this has
worked before now.

This can happen if, for example, the home page in a local
disk-based Web is index.htm, but the default document name
on the remote Web server is default.htm. In that case,
FrontPage will rename the home page as it publishes.

However, FrontPage will *not* correct any links within
subwebs, and this can create broken links.

The solution is usually to build your links with the
filenames that will exist on the server, and ignore any
broken links of that type that you encounter locally.

Another solution is to use a local Web sever for
development, and set its default document name to match
that on the remote (live) server.



First, if your site takes over an hour to publish via DSL,
you need more and smaller subwebs.

I am think about this course of action when I come to re-design.

As to SARTRE, I'd certainly open a few of those pages
directly on the server and look for signs of tampering,
especially if the date in the message is recent.

SARTRE is the name of one of the ISP's servers. All machines are
named after philosephers. This one is Jean Paul. Support says that the
files are "modified" (or FP *thinks* they are modified) when a backup
occurs server side.

You might also want to try the advice at:

FrontPage Publish Command Fails
http://www.interlacken.com/winnt/tips/tipshow.aspx?tip=24

Jim Buyens
Microsoft FrontPage MVP
http://www.interlacken.com

Thanks for the help, Jim.

 

[Stefan B Rusynko]

Ask your host what home page file name is the default for the server, and rename it to the same name locally in FP

--




| On Mon, 28 Jun 2004 13:59:40 -0700, "Jim Buyens"
|
| >>-----Original Message-----
| >>Hi,
| >
| >Howdy.
| >
| >>I have been using FP 2000 for years without any major
| >>problems but have now come across something that has me
| >>puzzled.
| >>
| >>I manage a site for my workplace that has grown over
| >>the years and I have started using sub webs to make
| >>things easier. Creating a link back from the sub web to
| >>the main website is simple enough but last week I lost
| >>all the navigational structures and had to republish. This
| >>is where my troubles began.
| >>
| >>First, no matter what I call my main page, be it index,
| >>home, default.asp (a name FP sometimes insists calling
| >>home.htm) the link back from the sub web fails after I
| >>upload to the ISP's server. It exists and works on my
| >>local machine without problems but returns an error 404
| >>otherwise.
| >
| >Is FrontPage renaming your home page as it publishes?
|
| Yes it is. If I name the home page home.htm then FP will publish as
| default.htm. What I have done is republish but the link from the
| subweb back to the home page presents no page at all or the home page
| sans navigation bars. I added a relative link locally and this has
| worked before now.
| >
| >This can happen if, for example, the home page in a local
| >disk-based Web is index.htm, but the default document name
| >on the remote Web server is default.htm. In that case,
| >FrontPage will rename the home page as it publishes.
| >
| >However, FrontPage will *not* correct any links within
| >subwebs, and this can create broken links.
| >
| >The solution is usually to build your links with the
| >filenames that will exist on the server, and ignore any
| >broken links of that type that you encounter locally.
| >
| >Another solution is to use a local Web sever for
| >development, and set its default document name to match
| >that on the remote (live) server.
| >
| >>Second, when trying to republish FP will warn me that
| >>such a page has been changed by SARTRE on <date> at
| >><time>. This sometimes refers to a page I know *hasn't*
| >>been altered in months if not years. FP may also
| >>indicate that a page has been changed when no one can
| >>possible be in the building ie at weekend.
| >>
| >>I can overcome this by overwriting files but the entire
| >>site can take over 1 hour to transfer all files using a
| >>DSL connection. Even then I will not be sure if all
| >>navigation bars have been reinstated.
|
|
| >>Any ideas on a course of action gratefully received.
| >
| >First, if your site takes over an hour to publish via DSL,
| >you need more and smaller subwebs.
|
| I am think about this course of action when I come to re-design.
|
| >As to SARTRE, I'd certainly open a few of those pages
| >directly on the server and look for signs of tampering,
| >especially if the date in the message is recent.
|
| SARTRE is the name of one of the ISP's servers. All machines are
| named after philosephers. This one is Jean Paul. Support says that the
| files are "modified" (or FP *thinks* they are modified) when a backup
| occurs server side.
|
| >You might also want to try the advice at:
| >
| >FrontPage Publish Command Fails
| >http://www.interlacken.com/winnt/tips/tipshow.aspx?tip=24
| >
| >Jim Buyens
| >Microsoft FrontPage MVP
| >http://www.interlacken.com
|
|
| Thanks for the help, Jim.