FrontPage: Not Able to "Save As"

[Melanie]

In one of my FrontPage websites, I am no longer able to "save as" a page. All the other FrontPage websites' "save as" function works fine. I've searched the Microsoft database but can't find anything regarding this issue. I've tried starting fresh with a new web and importing the files but as soon as I add the FrontPage template to this website, the "save as" feature stops working.

Does anyone have any ideas how I can fix this?

Melanie

[bill]

Hey Melanie, welcome to WebmasterWorld.

What have you done to this template that is different from your other sites? If it's not too complex maybe you could rebuild the template from scratch and replacing the old one.

[Melanie]

It is a standard FrontPage template with shared borders. I have a subweb with the same template, and it works fine. I'll try copying the template from the subweb and see if that works. I'm just trying to avoid a total rebuilding of the site.

[NeedScripts]

If nothing works try this.

1) Copy the source code of that page into txt file
2) Delete that page
3) Create New page with whatever name you want and past the source code.

Hope this helps :)

[bill]

shared borders

I'm just guessing here as I don't know your site's setup, but shared borders are a component that you might want to steer clear of. The shared borders depend on FrontPage server extensions which can easily be corrupted if you don't know what you're doing (or even if you do). Your shared borders depend on what you set up in the Navigation of your web, so importing them may not work the way you think. You may have to play around with the Navigation and then Recalculate Hyperlinks your web. Also I'd make sure you have the latest version of the FrontPage server extensions on your development machine and the server.

As an aside, this won't solve your current problem, you might want to consider using the FP Include Page instead of the Shared Borders. Include Page does not require server extensions and will ultimately give you more control over the page.

[mack]

I dont think shared borders require front page extensions. although I belive they should be avoided. FP is ok is you stay clear of all the complicated stuff and try and keep it basic.

[bill]

I dont think shared borders require front page extensions.

oops, you may be right...I take that back. However, they are affected by the Navigation, and they do create horribly incomprehensible HTML.

[mack]

totaly with Bill on that one, avoid it if possible. Is is very convenient to be able to use common header and footers using shared borders but the cons far out weigh the pro's. As bill said code becomes cluttered and error ridden.

[pageoneresults]

Melanie, I'll agree with the sentiments raised above. I've been working with FP since 1996 and can pretty much debug most of the problems.

Can you tell me exactly what is happening when you do a save as? Is the save as grayed out or do you find that you cannot browse to the directory you want to save the file in? I've noticed a bug in FP2002 when you do a save as and it won't let you save to another location. What I've done is save it wherever it lets me, and then close all pages in my editor view, click on the new file and drag it to the location you want it. FP will automatically update all the url references when you do this.

[Melanie]

I want to thank everyone for the help. I copied the code from my subweb for the shared left border into the main web and now the "save as" feature works fine. :)