Just try it. If you had-wrote the page to exploit SSI, what
would you place in the hypertext file that triggers the include?
Put that in the footer of the page templates and away you go.
If the SSI is processed by the HTTP server when an HTTP GET is
received, then all you have to do is have the appropriate
meta-HTML markings in the right place in the pages. MHonArc does
not nitpick the HTML you put in your explicit code blocks. You
want SSI's expanded when the page is served, not installed.
MHonarc should not cause you any trouble, so try it.
to follow up on what Peter Losher said:
From owner-mhonarc(_at_)ncsa(_dot_)uiuc(_dot_)edu Wed Nov 4 11:04:24 1998
X-Authentication-Warning: ex1.ncsa.uiuc.edu: majordom set sender to
owner-mhonarc(_at_)ncsa(_dot_)uiuc(_dot_)edu using -f
Date: Wed, 4 Nov 1998 07:45:42 -0800 (PST)
From: Peter Losher <plosher(_at_)globe(_dot_)arc(_dot_)nasa(_dot_)gov>
Subject: Anyway to use include files (for nav bars) in a RCfile?
We have been using MHonArc for over a year now (switching from
Hypermail), and have used it in it's "vanilla" form straight out of the
box during that time. We now are trying to configure an RCfile to format
our multiple MHonArc archives into the standard "look and feel" that the
rest of our web site maintains.
Using the RCfile given in the MHonArc documentation, I have
customized it to meet most of our needs. But there is one nagging problem
that I see. In our "web design", we have a nav bar across the bottom of
the web page. Reading the documentation, it seems that the only way to
have the nav bar show on the main, themes & message pages is to explicitly
call out the HTML code in the <LISTEND>, <TFOOT>, and <MSGFOOT> resources
respectively. This would cause a problem in the future if modifications
are made to the nav bar (ex. having to edit three sections of a RCfile
times the number of MHonArc archives we maintain...whew!).
I would rather have it call to a file to include like a server
side include. I did look at the <INCLUDE> resource, but it only works for
the main index (and isn't supported).
Has anyone come across this problem, and how did they deal with it?
Thanks in advance,
Peter Losher The GLOBE Program \ Raytheon ITSS
E-mail: plosher(_at_)globe(_dot_)arc(_dot_)nasa(_dot_)gov GLOBE Program
NASA Ames Research Center, Mailstop 204-14, Moffett Field, Calif. 94035-1000