Glad you asked Paul!
here's the thing (I know because I'm just about done wrapping up about 1,000
hours worth of work on a php app specifically for FrontPage);
(the desktop program you're using) really doesn't like anything to do with
php. you can set php as a file FrontPage will edit and fp 2002 and up won't
/ shouldn't mess with the code much but you can forget about things like
themes (most parts of them), nav bars (FrontPage driven), and virtually any
other FrontPage save time component.
The reason I wanted to write my script in php is because of people using
FrontPage to author against a UNIX server.
so, given that FrontPage doesn't play nice with php and I really needed php
for the cross platform capability of my script I decided to really dig in
and get something worked out:
the verdict; FrontPage will work fantastically with php and include it's
shared borders, nav bars, and everything else, you just can't tell FrontPage
that the pages are php. look at this:
http://demo.contentseed.com/sample
although these pages have the .htm extension I've had the server admin
process the .htm and .html pages past the php engine. it may sound
complicated but it's really not. there's no problem with overburdening the
server because the pages would have had to be php anyway.
so in short, my suggestion to you would be to have your server admin make
the mod to process the .htm pages past the php engine, don't rename it to
php and in fact, don't use the <? and ?> instead use <script
language="php"></script> to enclose your php include statement.
HTH
--
Chris Leeds,
Microsoft MVP FrontPage
The email address on this posting is a "black hole". I got tired of all the
spam.
Please feel free to contact me here:
http://nedp.net/contact/