Thanks for the replay Andrew,(its Saturday night, don't you guys ever
take a break?
)
We are the host actually. I work for the city and the servers and
equipment are stored on the Police side of the building. I can't get
access for security reasons. Department of justice rules.
Whatever a "DMZ" server is, I don't know - I assume this is your hosting or
internet provider ???
I wasn't sure either. I'm a graphics guy, not a network guy. I was
hoping someone would fill me in on that one. The whole site was move
there as part of a new security protocol. thats when the trouble
started. I now have to fix something that (imo) wasn't broken in the
first place. Job security I guess.
1) Shared borders do sometimes cause headaches, as you've discovered - I'd
avoid using them, and use the include page or dynamic web templates (DWT's
are a new feature of FP2003). They provide a similar function as shared
borders in that they display common content on all pages eg
navigation/menus, but they are much easier to handle and don't necessarily
require the FPSE to function.
I've been using this set-up from the start (over 8 years). This is our
first burp. I'll look into the included page deal. (I make comment why
I'd rather not next)
2) The printing issue, is probably just do do with the page margin settings,
the model of printer and the fact that web pages are not primarily designed
for print. There are ways to make pages look correct when printed using CSS
and so on, but for an easier work around, consider putting the content you
want to print, in a different format such as PDF files.
What I see happening recently is that in printing, the content from the
body of the page get pushed into the left shared border. In the past, it
would "respect" the 'boundaries" and keep alignment (like a table). I'll
look closer at ccs. I'm avoiding any major redesign at this point. I
have little time for this lately. I'm 90% engineering department tech
10% web guy.
Its not a printer issue I don't think. I've tried printing on several
models with the same result. As I mentioned, all this work for years
until the last 2 weeks.
3) Regarding the forms, you would have to check with your host that they
have enabled the mail transport functions of the server extensions; have
them do a health check/reinstall if necessary as well. I don't know what you
mean "only stored to pages". Which forms in particular are not functioning?
The standard "contact" form that sends an email, or the discussion web, or
the guestbook or database wizards or search component??
The way I use the forms, I have the data emailed to me to dump into
various applications outside of FP. I also have the data store to html
pages (FP option in the forms wizard). Most parts of all the 4 you
mention have been effected. The IT guys are working on the problems, so
even as we speak, some are starting to work (better).
4) Editing directly on the server is OK, but if the server crashes you risk
losing the entire site, and you have no back up to restore the site from.
So, editing the site locally and publishing the changes is the better
solution. If the server ext are installed you need to publish via
Frontpage's HTTP mode.
I'm told the server is backed up nightly, and stored on separate drives.
We've had a few crashes, with no lost data (knock on wood). I was
concerned with publishing. Not having edited that way in the past, I was
thinking that if others edit (2 other people edit a few pages) I didn't
want to publish over something they had made changes to. I'll study up
on that more.
I think I already edit via http mode
All in all, it sounds like the server doesn't have the Frontpage Server
Extensions enabled; get your IT to do this, although it might be a bit late
for that, since Microsoft have already withdrawn support and the download
file(s) for the server ext from their website. However I believe the FPSE
are available on either the XP Pro Install CD or the Server 2003 Install CD
along with the IIS install.
That was the first thing I asked them to do. I'll have them double
check. sounds like I'm going to have to make a move to something else,
like it or not.
*but you didn't mention whether this is a Windows or Linux server*.
again, not having access, I'm not 100% sure, but I'm pretty sure its a
Windows (2000?) server. Unless that changes too with the security stuff.
), is there any advice I can