| 3:40 pm on Feb 20, 2004 (gmt 0)|
I would think to add absolute addresses instead of relative, would be a manual change unless you know how to edit the files, that assign relative/absolute linking for the website in question.
I don't think it is an FP only problem, DW has these restraints as well.
| 5:01 pm on Feb 20, 2004 (gmt 0)|
Well I do have a way of tricking it, I take the page I created in frontpage, save it to my hard drive but tell it not to save any of the files and to leave the paths as they exist. Then I ftp it from my hard drive back onto the website. Which does work but it is starting to be a pain when I have to go through that all the time. I'm surprised Dreamweaver would have the same constraints.
| 3:37 pm on Mar 3, 2004 (gmt 0)|
>Which does work but it is starting to be a pain when I have to go through that all the time.
Same here, I guess I will replace FP now after my sites have grown so much. It is a nice tool for beginners and sites that do not need too much updating and changing.
| 9:23 pm on Mar 3, 2004 (gmt 0)|
How are you creating your absolute links in FrontPage? I use absolute links all the time and FP has never messed with mine. I'm using FP2003 but FP2002 also never gave me any problems.
I assume you're doing something like the following:
1) Create initial relative link ("/images/pic.jpg")
2) In HTML view, change link to absolute ("/images/pic.jpg" to "h**p://www.example.com/images/pic.jpg")
3) Save and publish.
I may be missing something here, but I can't see how FP would be smart enough to change absolute links to relative links. Relative to absolute, sure, but not the other way around.
| 7:49 pm on Mar 24, 2004 (gmt 0)|
Or... just right click on the link, select Hyperlink Properties, and add the http part right there. FP2002 doesn't alter any changes I make that way.
It would be nice if there were an option to make this the default for internal links, though...