Scott,
If all you are interested in is a header and footer that will be on all pages, there is no reason to put them in each individual template file. For example, in the default Links, each template file has:
Code:
<p><small class="menu">|
<a class="menulink" href="<%build_root_url%>">Home</a> |
<a class="menulink" href="<%db_cgi_url%>/add.cgi">Add a Site</a> |
<a class="menulink" href="<%db_cgi_url%>/modify.cgi">Modify a Site</a> |
<a class="menulink" href="<%build_root_url%>/New">What's New</a> |
<a class="menulink" href="<%build_root_url%>/Cool">What's Cool</a> |
<a class="menulink" href="<%build_root_url%>/Ratings">Top Rated</a> |
<a class="menulink" href="<%db_cgi_url%>/jump.cgi?ID=random">Random Link</a> |
<a class="menulink" href="<%db_cgi_url%>/search.cgi">Search</a> |
</small></p>
That really is not necessary. Instead, in the Globals section of site_html_templates.pl (at the top), you could put something like:
Code:
$site_menu = qq~<p><small class="menu">|
<a class="menulink" href="$build_root_url">Home</a> |
<a class="menulink" href="$db_cgi_url/add.cgi">Add a Site</a> |
<a class="menulink" href="$db_cgi_url/modify.cgi">Modify a Site</a> |
<a class="menulink" href="$build_root_url/New">What's New</a> |
<a class="menulink" href="$build_root_url/Cool">What's Cool</a> |
<a class="menulink" href="$build_root_url/Ratings">Top Rated</a> |
<a class="menulink" href="$db_cgi_url/jump.cgi?ID=random">Random Link</a> |
<a class="menulink" href="$db_cgi_url/search.cgi">Search</a> |
</small></p>~;
Then include
site_menu => $site_menu, in the %globals variable list and then use <%site_menu%> inside the template file where you want the menu to appear instead of the menu that is there now. That way, to change the menu, you only need to do it in one place. It doesn't require SSI at all nor .shtml files. You can do the same thing for a header and footer.
I hope this helps.
[This message has been edited by Bobsie (edited May 02, 1999).]