G
Graham Wideman \(Visio MVP\)
Folks:
I'd like to be able to use FrontPage (2002) to work on webs on the local
file system. FP works fine it all links within the web are relative.
But there's a problem with absolute links because FP retrieves those files
using the literal path in the URL, rather than relative to the root of the
web... and this is what I'd like to work around.
Example:
FP Web at D:\myweb, with some images in D:\myweb\images
If page D:\myweb\somepage.htm contains a link to /images/some.gif, then FP
will look for it at D:\images\some.gif, instead of at
D:\myweb\images\some.gif -- in a sense this is correct behavior if the
intent was to set up pages that IE can browse locally -- but it prevents
using local editing to simulate deployed web.
So, although the web will work fine when deployed, it doesn't work while
editing locally.
I attempted to work around this by creating a web at the root directory of
the drive (actually a subst drive), but FP refuses to set up web in a root
directory.
(When I try to start a blank web at "W:\", I get an error dialog: "There is
no web named /W".)
Any suggestions as to how to do what I'm trying to do?
(OK, one workaround is to set up IIS on local machine -- but I'd rather
avoid that effort and security hazard... this should be easy!)
Thanks,
Graham
I'd like to be able to use FrontPage (2002) to work on webs on the local
file system. FP works fine it all links within the web are relative.
But there's a problem with absolute links because FP retrieves those files
using the literal path in the URL, rather than relative to the root of the
web... and this is what I'd like to work around.
Example:
FP Web at D:\myweb, with some images in D:\myweb\images
If page D:\myweb\somepage.htm contains a link to /images/some.gif, then FP
will look for it at D:\images\some.gif, instead of at
D:\myweb\images\some.gif -- in a sense this is correct behavior if the
intent was to set up pages that IE can browse locally -- but it prevents
using local editing to simulate deployed web.
So, although the web will work fine when deployed, it doesn't work while
editing locally.
I attempted to work around this by creating a web at the root directory of
the drive (actually a subst drive), but FP refuses to set up web in a root
directory.
(When I try to start a blank web at "W:\", I get an error dialog: "There is
no web named /W".)
Any suggestions as to how to do what I'm trying to do?
(OK, one workaround is to set up IIS on local machine -- but I'd rather
avoid that effort and security hazard... this should be easy!)
Thanks,
Graham