D
Dana Nelson
I have a FP2002 created website hosted on a Win2k server
with FP extentions. The site uses include pages for both
a top title section and a side link bar. The website has
no frames. All of the links in the included link bar are
set to the page default of "nothing", so they open in the
same browser window.
The other day I was messing around with some re-design
ideas including frames with included content. I abandoned
the test pages, but since publishing these pages, the
included links on my home page all open in a new window.
Also, all pages on my site that had HREF links with the
page default settings have a line added target="contents"
I manually removed every target="contents" line from
every single page in the site, and the links from the
home page were still kicking off in a new browser window.
I looked at the source again, and all of the target lines
were back just like magic! I went around this loop a few
more times with just the home page.removing the lines,
them watching them re-appear again after publishing the
changed page.
I published a copy of my home page default.asp that I had
from back in October - and behold.same problem still
occurs.
If you navigate the site from with-in the new page that
is kicked off, everything works fine.
It looks as if the FrontPage server is compiling/parsing
the code in default.asp the first time it is requested by
a browser and adding the line target="contents" to any
HREF that does not already have a target specified.
Having a target default specified for the page does not
seem to help this from happening either. The link bar on
the left is actually an include page, and does not
contain any target="contents" lines itself.
with FP extentions. The site uses include pages for both
a top title section and a side link bar. The website has
no frames. All of the links in the included link bar are
set to the page default of "nothing", so they open in the
same browser window.
The other day I was messing around with some re-design
ideas including frames with included content. I abandoned
the test pages, but since publishing these pages, the
included links on my home page all open in a new window.
Also, all pages on my site that had HREF links with the
page default settings have a line added target="contents"
I manually removed every target="contents" line from
every single page in the site, and the links from the
home page were still kicking off in a new browser window.
I looked at the source again, and all of the target lines
were back just like magic! I went around this loop a few
more times with just the home page.removing the lines,
them watching them re-appear again after publishing the
changed page.
I published a copy of my home page default.asp that I had
from back in October - and behold.same problem still
occurs.
If you navigate the site from with-in the new page that
is kicked off, everything works fine.
It looks as if the FrontPage server is compiling/parsing
the code in default.asp the first time it is requested by
a browser and adding the line target="contents" to any
HREF that does not already have a target specified.
Having a target default specified for the page does not
seem to help this from happening either. The link bar on
the left is actually an include page, and does not
contain any target="contents" lines itself.