SSI: to use or not to use?

siyab · #1 (**permalink**) 07-15-2007, 01:44 AM

Hi every body!
I could not find a category for my question so im posting it here.
The question is, should we use Server Side Includes or not? We all know that the page would be displayed badly if some include doesn't work. But many hosts support it. And, do search engines have a problem with .shtml files???

ncaditya · #2 (**permalink**) 07-15-2007, 08:15 AM

It is good to use SSI for many reasons:

1) To change the menu on all pages at the same time. If the menu needs to be updated, a single change made can be visible on all the pages.

2) Adding adsense ads. I usually create separate pages like adsense_1.html and add the code to it. Then I php include these where ever needed. If I have to try new ad formats or color combinations, I can edit a single file and check how it performs.

I would recommend php including files as most web hosts support php and have no problems with it.

lisa · #3 (**permalink**) 07-15-2007, 11:56 AM

I second ncaditya. My site has over 150 pages and it is a wonderful thing to be able to update my left, top, right nav and footer simply by editing one file rather than going in and updating all 150 pages.

webdev · #4 (**permalink**) 07-15-2007, 03:31 PM

I have done the same for my php site. My site layout is split in 5 components. The header, left menu panel, container or the main content panel, the right panel and the footer. Each component is a single php file that controls its look and feel. i even have ad helper script which i wrote last night that control the ad formats and types. For example i can tell it to display a specific google text or referral ads of any specific ad format. So everything is done through a central place.

Bingo · #5 (**permalink**) 07-15-2007, 03:37 PM

I also use them for every site I have. They make life a lot easier when having to update sidebars etc.

To answer your question if the Search Engines have a problem with it, they dont. The SSI is server as one file when requested from the server.

Give them a shot and see if SSI is for you. My bet is that you wont look back.

siyab · #6 (**permalink**) 07-15-2007, 08:42 PM

thank you all for your recommendations. I'll try it out

siyab · #7 (**permalink**) 07-16-2007, 07:50 AM

if you do use SSI, which one would be better?? php or .shtml??

ncaditya · #8 (**permalink**) 07-16-2007, 09:19 AM

I think php include would be better. Here is the code to use:

Code:

<?php include('filename.html'); ?>

Bingo · #9 (**permalink**) 07-26-2007, 07:00 PM

I personally use .shtml but dont know if there is any benefits over using .php

siyab · #10 (**permalink**) 07-29-2007, 05:51 AM

but i do not see any .shtml or .php extension on your websites. Is it possible to retain the .html extension?

Bingo · #11 (**permalink**) 07-29-2007, 01:02 PM

Quote:

Originally Posted by siyab

but i do not see any .shtml or .php extension

You wont actually see the SSI's when viewing a web page.

You'll have a HTML page and within its code the SSI will reside. Once a visitor requests the HTML page the server brings all the SSI's together to bring you one page, which you have seen.

For example:

HTML Code:

<html>
<body>
 <!--#include virtual="/ssi/header.shtml" -->
 <!--#include virtual="/ssi/navbar.shtml" -->
<p>Your main on-page content</p>
 <!--#include virtual="/ssi/footer.shtml" -->
</body>
</html>

The above page is made up of 4 different files. The header, navbar, footer and the main html page. Once these 4 files are uploaded onto the server and someone requests the html page the server will show all 4 files as one.

Hope that helps.

siyab · #12 (**permalink**) 07-29-2007, 08:39 PM

thanks Gavin!

WB Sponsors