Frontpage suddenly srewing file:/// references ???

[+Bob+]

For unknown reasons, FrontPage 2003 has decided to replace all of my
relative URL's with file :// references in one particular web. In
addition, when I insert anything new it now uses an absolute file
reference.

This is a disk based web. I've been working on it for over a week with
no problems. I've been creating webs like this for many years without
a hitch. All my other webs still work just fine.

The pages are actually stored correctly if I look at the files from
outside FP. But, when I open them in FP, it changes all the references
on the fly to "absolutes" to the drive. I did a "recalculate
hyperlinks" and then I could open the pages without them being
translated incorrectly, but anything new still comes out with a
file:/// reference.

When I insert images (insert picture) from outside the web, it no
longer prompts me to save the images within the web when I save the
page, it just saves it with a local file URL. Any link I create to a
simple page is treated similarly.

Ideas?

 

[+Bob+]

For unknown reasons, FrontPage 2003 has decided to replace all of my
relative URL's with file :// references in one particular web. In
addition, when I insert anything new it now uses an absolute file
reference.
<snip - see previous post for details>

Following my own post... I've tried a half dozen things to try to fix
it, including manually copying then repairing the files from outside
FP, correcting all errant references from outside, removing all FP
hidden directories, then renaming the directory and placing it on
another drive.

When I open it in FP, it's still messing up the references.

 

[+Bob+]

When I open it in FP, it's still messing up the references.

It turns out that the is a bug with included "base href" tags when
working on a disk based web, when the tag is included with the include
bot.

e.g <base href="http://www.domain.com/" >

If I code the tag directly in a page, it causes the includes to "fail
to include in FP" (even though they are legit and the files also exist
on the server and are available. Annoying, but not fatal. Not really
my issue tonight.

To avoid that issue, I had included the base href tag in a file of
included META tags that are used throughout my site. But, while having
the tag in there fixes the include issue (they work properly), it
causes FP to change any relative references to absolute disk
references.