Keeps putting in target="main"

J

Jo

I'm really hoping someone can help me with this. I'm at wit's end! I'm
running FP2003 on Win-XP-Pro, and my site does *not* use frames as such. (A
few pages use the Include iFrame that FP offers, but not on many pages that
this problem occurs in.)

On some hyperlinks (<a href=...>), as well as some anchor code (<a
name=...>), FP insists on inserting target="main." I have never put this in
on my own, nor have I ever used a target or even an anchor name called
"main," so I have no idea where this is coming from. Besides being annoying,
the bigger problem is that when you click on a link that has this, it creates
a new window, which I don't want it to do. These are (so far) links to other
pages within my site, not external links.

If I delete this from the code directly, it keeps coming back. ??!! If I
substitute something like target="_self" or "_top" it seems to stay put. But
I don't relish going through some 180 web pages to change this, even using
find-and-replace (which I've found to be buggy anyway). And I don't
understand why it would put this into anchor code anyway, except maybe that
it uses the same <a> code but for a different purpose.

I have checked to see if a target default has been set in Page Properties or
in the header code of the page -- nope. I even tried *setting* the default
target frame in Properties to "_top" and it STILL came back to "main." This
is like a bad horror movie! It comes back when I save it, unload the page,
and then reload the page in FP. And of course, when I test it in a browser
that's when I see that it produces a new window.

And even if I was to go through all those pages and change the target
specification, I'm not sure if I should be using "_self" or "_top" to link
using the same window, since they seem to be more or less the same in a
non-framed page.

So two questions:

1. Why is FP doing this and how can I get it to stop??

2. What's the difference between "_self" and "_top" and which should I be
using if I have to replace the code?

Thanks VERY much in advance for any help about this. I'm about to start
pulling my hair out by the roots!

Jo
 
J

Jo

I'm bumping this up because I really want to get an answer to this problem.
This is either a bug in Frontpage 2003 or some weird glitch that I have no
idea how to fix. I don't want to (and shuoldn't have to) pay $35US for email
support to get an answer, so this newsgroup is my best resource. Would
someone please reply and help me solve this problem? Thank you.

Jo
 
T

Tom Pepper Willett

When and if someone has an answer, I'm sure they'll provide it. Be patient.
This is simply a peer-to-peer newsgroup.
--
===
Tom "Pepper" Willett
Microsoft MVP - FrontPage
---
About FrontPage 2003:
http://office.microsoft.com/home/office.aspx?assetid=FX01085802
===
| I'm bumping this up because I really want to get an answer to this
problem.
| This is either a bug in Frontpage 2003 or some weird glitch that I have no
| idea how to fix. I don't want to (and shuoldn't have to) pay $35US for
email
| support to get an answer, so this newsgroup is my best resource. Would
| someone please reply and help me solve this problem? Thank you.
|
| Jo
|
|
| "Jo" wrote:
|
| > I'm really hoping someone can help me with this. I'm at wit's end! I'm
| > running FP2003 on Win-XP-Pro, and my site does *not* use frames as such.
(A
| > few pages use the Include iFrame that FP offers, but not on many pages
that
| > this problem occurs in.)
| >
| > On some hyperlinks (<a href=...>), as well as some anchor code (<a
| > name=...>), FP insists on inserting target="main." I have never put this
in
| > on my own, nor have I ever used a target or even an anchor name called
| > "main," so I have no idea where this is coming from. Besides being
annoying,
| > the bigger problem is that when you click on a link that has this, it
creates
| > a new window, which I don't want it to do. These are (so far) links to
other
| > pages within my site, not external links.
| >
| > If I delete this from the code directly, it keeps coming back. ??!! If I
| > substitute something like target="_self" or "_top" it seems to stay put.
But
| > I don't relish going through some 180 web pages to change this, even
using
| > find-and-replace (which I've found to be buggy anyway). And I don't
| > understand why it would put this into anchor code anyway, except maybe
that
| > it uses the same <a> code but for a different purpose.
| >
| > I have checked to see if a target default has been set in Page
Properties or
| > in the header code of the page -- nope. I even tried *setting* the
default
| > target frame in Properties to "_top" and it STILL came back to "main."
This
| > is like a bad horror movie! It comes back when I save it, unload the
page,
| > and then reload the page in FP. And of course, when I test it in a
browser
| > that's when I see that it produces a new window.
| >
| > And even if I was to go through all those pages and change the target
| > specification, I'm not sure if I should be using "_self" or "_top" to
link
| > using the same window, since they seem to be more or less the same in a
| > non-framed page.
| >
| > So two questions:
| >
| > 1. Why is FP doing this and how can I get it to stop??
| >
| > 2. What's the difference between "_self" and "_top" and which should I
be
| > using if I have to replace the code?
| >
| > Thanks VERY much in advance for any help about this. I'm about to start
| > pulling my hair out by the roots!
| >
| > Jo
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top