Inline below even though I'm not normally a bottom poster.
Orest Kinasevych said:
We're not any closer to a solution to our original correspondent's
problem.
His insistence on keeping the file naming scheme that he has instituted
on his web site is perfectly understandable and reasonable.
Why, because he made his site that way.??
Rename the home page to index.html and FrontPage will rename
every link to it in the time it takes to click OK.
What earthly difference does it make, what the file name of the home page
is.
It's invisible to everyone but the web author when he's viewing the site in
folder view anyway.
Whether or not his decision generates 404 errors is not the issue.
Besides missing the point, your insistence that a 404 error *would*
occur is wrong. It *might* occur if "index.htm" isn't listed in the
Apache DirectoryIndex directive. (See
http://httpd.apache.org/docs/mod/mod_dir.html#directoryindex for an
explanation.)
Would occur, might occur whatever. Using the "default" required by
the server eliminates the error. Also the only index that needs to be
index.html
is the one in the root.
However, by the information already conveyed in this thread, it sounds
like "index.htm" might well be listed in the DirectoryIndex directive.
In an earlier post, Thomas A. Rowe suggested that "index.htm" ought to
be moved to the top of the default document list. However, changing the
order of DirectoryIndex file names in an operational -- and very likely
shared -- web hosting environment can potentially break many, many web
sites already on the server.
Your assumption that the host has changed the default document list is also
in error.
All of my sites are hosted on Apache, and they all have index.html as the
default.
Always have. It's just one of those things I was aware of, and had the
poster read the
FAQ's at his hosting service he would have probably known that.
The issue is we have someone ( like many ) that created a web site, then
looked for hosting, or changed hosts without realizing that different
servers require
different "default page names."
So your site is hosted on Apache/UNIX with FP extensions and PHP, and your
home page can be index.php. He unfortunately doesn't have that option.
And once again it is a hosting issue, not a FrontPage or a Microsoft or an
MVP issue.
The issue is that there is some mechanism, somewhere, that is renaming
his files. Whatever mechanism it is, it is making the blatantly
incorrect assumption that our correspondent would appreciate having his
files renamed. This renaming feature is the root of the stated problem
and is the issue that one would hope that the MVP FrontPage "experts"
would be informed enough to answer directly, if they can answer it at all.
It's not a blatantly incorrect assumption. It's a Programmed result of
FrontPage
determining the requirements of the server and publishing the web in a
manner that ensures functionality.
The other issue is that the Extensions for Apache/UNIX aren't created or
maintained
by MSFT nor are the MVP's privy to how they are constructed.
The are authored by RTR software. However there is a news group dedicated
to UNIX servers: microsoft.public.frontpage.extensions.unix
--
Steve Easton
Microsoft MVP FrontPage
95isalive
This site is best viewed............
........................with a computer
