|
| |
|
|
tgorski
Posts: 75
From: Middleton
Status: offline
 |
target frame default set to contents - 10/24/2003 15:49:46
Hey Folks -
Great job, as always.
Here's a weird one that's driving me nuts.
Somewhere along the line, the line ' target="contents"' is being added to our links. (My assumption is at my ISP's server extensions.) Further, this line causes weird behavior. If no other browser windows are open, the link is opened in a new window. If more than one browser is open, clicking on the link appears to do nothing, although it opens the link in some other window. The problem, however, is that the window in which it opens does not "present itself" (i.e., I have to look through all open windows to find out which one it opened in.)
Here's related scenarios:
1. When I remove the "target=contents" locally in FrontPage, I can view the page locally just fine. But when I publish to the host's web server, "target=contents" is back in the code.
2. When I open the page from FrontPage AFTER opening the site on the web server, I can remove the "target=contents" attribute (either using FrontPage or in html view), but when I close and save, the line is re-inserted.
3. The only way I can fix the problem is to fix the problem in a text editor and FTP the file.
It's been suggested that the problem is with my client software, because one of the techs there can open the web in FrontPage, correct the link, and it STAYS corrected. However, I can duplicate the problem on 3 separate clients, one of which has a newly installed version of FrontPage. Additionally, I have a 4th client that publishes to a different web server WITHOUT the problem occurring. In fact, I can publish to the same server without producing the problem.
Any help in resolving this would be appreciated.
tgorski
|
|
|
|
DarlingBri
Posts: 3123
From: Left of Centre, Cork, Ireland
Status: offline
|
RE: target frame default set to contents - 11/4/2003 22:38:18
Can we see the site? A URL would be helpful.
_____________________________
--Bri
Bartlet for President 2008
Get a taste of religion. Lick a witch.
| |
|
|
|
tgorski
Posts: 75
From: Middleton
Status: offline
|
RE: target frame default set to contents - 11/5/2003 16:51:49
Thanks for the follow up. I finally got it solved through a Microsoft board, but here's what the problem was:
apparently I was on a framed page, and when setting the target frame for a link, I clicked on the "page default" box, thinking it would make it the default for other links on the page.
OOPS! That made it the default for ALL pages! And rather than putting in familiar target references, like "Target=_blank, it used "Target=contents" AND it automatically inserted a "Base target=_blank" line in all pages published to the server after that point, so even if I removed the "Target=contents" reference, the server extensions (or whatever) would add it back in for all links on the page!
To correct the situation I had to remove all "Base Target=" references, then go back and remove all "Target=contents" references which turned out to be over 33,000!!!
Thank you Microsoft for your clear cut prompts and benevolence in interpreting and propagating what you THINK I wanted to do!
Clearly the down-side of using an editor!
Thanks again for your reply.
| |
|
 New Messages |
 No New Messages |
 Hot Topic w/ New Messages |
 Hot Topic w/o New Messages |
 Locked w/ New Messages |
 Locked w/o New Messages |
|
Post New Thread
Reply to Message
Post New Poll
Submit Vote
Delete My Own Post
Delete My Own Thread
Rate Posts
|
|
|
Printable Version 
