FP 2002 messes with code...sometimes?

[darrel]

I'm trying to accomodate one of our web folks and let them use FP to edit
files that we normally edit in DW. We use includes to keep the page content
relatively 'clean' and then just open these up in DW to edit them.

With Frontpage, however, we've found a weird inconsistency. Two of us each
have installed FP 2002. When I open an include file, FP leaves it as-is,
minus any changes and saves it just fine. In the other person's copy of FP,
when it opens the include file, it sees that there are no HTML or BODY tags
and inserts them...thereby breaking the include.

The obvious issue here is that we're both using the exact same copy of FP,
so we're a bit leery as to how the other people's copies of FP are going to
act.

I've sort of asked this before, but thought I'd do it one more time...is
there some odd setting somewhere in FP that may be causing this
inconsistency?

Next week, we're probably going to set up the server to handle some unique
extentions (like ASPFP) that, in theory, will allow FP to open the file with
out adding it's own 'corrections' to it. However, I can't test this, as my
copy of FP doesn't have the problem with the plain extensions either.

-Darrel

 

[darrel]

Next week, we're probably going to set up the server to handle some unique

extentions (like ASPFP) that, in theory, will allow FP to open the file with
out adding it's own 'corrections' to it.

Actually, we just tried this. FP doesn't know what to do with it until you
assign FrontPage as the editor for this type of file. Once you do, FP sticks
the 'missing' HTML/BODY tags back in.

So, perhaps to simplify (and repeat) the question:

Is there a way to have FP open a file containing HTML, edit it, and save it,
without taking it upon itself to replace tags it assumes are missing (and
thereby breaking our includes)?

-Darrel

 

[Andrew Murray]

I'm trying to accomodate one of our web folks and let them use FP to edit
files that we normally edit in DW. We use includes to keep the page content
relatively 'clean' and then just open these up in DW to edit them.

With Frontpage, however, we've found a weird inconsistency. Two of us each
have installed FP 2002. When I open an include file, FP leaves it as-is,
minus any changes and saves it just fine. In the other person's copy of FP,
when it opens the include file, it sees that there are no HTML or BODY tags
and inserts them...thereby breaking the include.

The obvious issue here is that we're both using the exact same copy of FP,
so we're a bit leery as to how the other people's copies of FP are going to
act.

I've sort of asked this before, but thought I'd do it one more time...is
there some odd setting somewhere in FP that may be causing this
inconsistency?

Next week, we're probably going to set up the server to handle some unique
extentions (like ASPFP) that, in theory, will allow FP to open the file with
out adding it's own 'corrections' to it. However, I can't test this, as my
copy of FP doesn't have the problem with the plain extensions either.

-Darrel
aren't the include files supposed to be HTML files(include page component won't

allow selection of other file types....), so therefore they'd have body and html
tags in any case?

 

[Thomas A. Rowe]

Make sure the both copies of FP have the same page options set.


--

==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)

FrontPage Resources, Forums, WebCircle,
MS KB Quick Links, etc.
==============================================

 

[Stefan B Rusynko]

The "includes" should not be .htm files and not associated w/ FP as an editor
Some users make them .inc
If they are .htm, Right and select open w/ Notepad

--




| > Next week, we're probably going to set up the server to handle some unique
| > extentions (like ASPFP) that, in theory, will allow FP to open the file
| with
| > out adding it's own 'corrections' to it.
|
| Actually, we just tried this. FP doesn't know what to do with it until you
| assign FrontPage as the editor for this type of file. Once you do, FP sticks
| the 'missing' HTML/BODY tags back in.
|
| So, perhaps to simplify (and repeat) the question:
|
| Is there a way to have FP open a file containing HTML, edit it, and save it,
| without taking it upon itself to replace tags it assumes are missing (and
| thereby breaking our includes)?
|
| -Darrel
|
|