Server Side Include (SSI) - Basic - html

I, for the life of me, cannot figure out how to get these to work.
I currently have a file that is named "included.html" that I would like to be posted on another page, "a.html". The "included.html" contains both HTML and CSS. So within "a.html", I pasted the following code:
<!--#include file="included.html" -->
That did not work.
I contacted my hosting service to make sure they supported SSI and they said they did, just in the .shtml format.
So, I changed the file name to "included.shtml" and changed my code within "a.html" to the following:
<!--#include file="included.shtml" -->
Still does not work. I've even messed around with changing #include file to #include virtual. Doesn't work.
Any and all help is appreciated. Thanks.


Your server host is supporting SSI in pages that have the .shtml extension. Therefore, your include must be in a file with a .shtml extension, and the pages being included don't necessarily need the same extensions.

Related

HTML SSI's don't work in browser

I'm trying to use server side includes for both my header and navigation, as they will be constant across every page, and I'd like the ability to make frequent changes in one place and have them populate across all pages. I have tried a "file" and "virtual" include, and have tired placing the include files in the same directory. The include files have no duplicate code (doctype indicator, html tag, etc). I've also tried both .html and .shtml file extensions. I use the file explorer in DW to select the files, so I'm assuming the path is correct.
The SSI's preview fine in Dreamweaver, but will not populate in the browser. Any suggestions would be greatly appreciated.
<!--#include virtual="/lpapp/includes/influencer_header.shtml" -->
<!--#include virtual="/lpapp/includes/influencer_sidebar.shtml" -->

Dreamweaver probably support SSI. If you run your html from a random folder on your local PC, SSI won't work. As soon as you upload the project to a Apache webserver or a virtual server like Wamp/Mamp. It is possible to get SSI working using the right SSI syntax and .htaccess.

How do I use Server-Side Includes in Webstorm?

I have a few .html files in a project I am working on for a class. All with the same header and footer. We are required to use SSI with Apache, but I am having trouble looking for a way to have my includes code acknowledged by WebStorm. To be honest, I'd be content with just a way to include the same code header by using just one line of code, but I'd rather not have to replace the code with SSI code in every page before I hand it in.

SSI not working in html

I've been through all the topics on here and have tried everything but my SSI code is not pulling the html page like it should...
What i have already tried:
confirmed with godaddy that SSI is enabled
tried both <!--#include virtual="\menus\menu.html" --> & <!--#include file="\menus\menu.html" -->
tried changing "menu.html" to "menu.shtml"
i'm stuck...what's going on?
here is my html:
<body>
<!--#include virtual="http://unifiedforunifat.com/menus/menu.html" -->
<div id="include">
</div>
</body>

Your problem is you are including the external web address of your script. Not only does that violate the point of having scripts on the server side, but random people can view the script if it's accessible that way.
Try
<!--#include virtual="/menus/menu.html" -->
It seems your slashes are the wrong way around. The \ character is the Windows filesystem slash, not the standard / slash for most technologies and Linux/Mac OS filesystems.
If virtual doesn't work, you should be able to use:
<!--#include file="/menus/menu.html" -->
According to http://nginx.org/en/docs/http/ngx_http_ssi_module.html, virtual specifies an included request, whereas file specifies an included file.

Or you can edit the .htaccess file to allow for them to be in separate folders (and inherently more tidy).
Add the following command to the first line of your .htaccess file in the root:
AddType text/x-server-parsed-html .html .htm

Server side include no longer seems to be working - "[an error occurred while processing this directive]"

We have a page that has been using a server side include for many years. Recently it stopped working. No changes have been made to the page
<!--#include virtual="..\..\includes\nav.include" -->
Near the bottom of a page called contact.html
The 'nav.include' page simply contains html for a navigation bar. No javascript. No server side scripting. Just html.
Is there some setting somewhere that needs to be set to make SSIs work in the way it is implemented here (including a file with an uncommon extension inside a html file)?

A solution that I discovered yesterday:
I duplicated and renamed all my pages to .php (retained the original html files just in case!)
I have replaced all the {<#include virtual="folder_name/file_name.ext" -->} with
<?php include "folder_name/file_name.ext" ; ?>
with the appropriate number of dots and slashes depending upon where the pages are in my folder hierarchy. ( The {} above is to mark out the code only)
Finally, I renamed the original index.html to some other name so that the index.php is picked up instead of the index.html
This seems to be working out - I am still testing out all the pages and links - a very tedious and time consuming exercise!
INCLUDES SYNTAX:
In a php file use
<?php include "..//folder_name/file_name.ext" ; ?>
In an html file use
<!--#include virtual="../folder_name/file_name.ext" -->
EXPERIMENT WITH NUMBER OF "..." AND NUMBER OF "///" IN THE ABOVE SYNTAX TO GET THE CORRECT COMBINATION!!!!
For me, all my includes are small html files in a folder ABC which is directly under the webroot.
For pages which are under sibling folders of ABC i.e. in other folders directly under webroot, "..//" is the number of dots and slashes that work.
For pages which are directly in the webroot (i.e. not in any folder inside webroot), folder_name/file_name.ext without any dots or slashes has worked.
I haven't had the time to check out the number of dots and dashes required for any other level in the hierarchy!
I hope this helps!

Are you using GoDaddy? They did the same to my site, and I found on their forums someone that said to use include file instead of include virtual.

Just switched over to Godaddy servers and my SSI stopped working. I made a .txt file with the following:
AddHandler server-parsed .html
I uploaded it to the public html folder, then renamed it .htaccess, and everything started working.

I had too many files to convert all the extensions to PHP, so I had to find another answer, if at all possible.
For me, for a little while, exchanging include virtual to include file seemed to help, but then it broke again after a few days. I guess GoDaddy was not finishing monkeying around with the SSI configuration. o_O
The solution, as of tonight, was to convert all relative paths to absolute specification in regards to the site root. For example, I had to convert:
<!--#include virtual="..\..\includes\nav.html" -->
To:
<!--#include virtual="\includes\nav.html" -->
Using this approach, I was able to include HTML files inside other HTML files.
I discovered this on one of my pages that mixed absolute and relative path specification.
HTH

I've been seeing this problem frequently on my GoDaddy hosted site. I have to go into the Server configuration page, disable SSI, save the settings, then re-enable SSI and check "Use SSI on .HTM and .HTML files) and it starts working again.
The problem is on GoDaddy's side. For some reason, it's forgetting that it needs to parse SSI in files, until you turn off and turn on that option. Their Tier-2 support only suggested using Virtual instead of File on the Include command... which is preposterous, since not only does that not change a thing, the SSI includes work just fine most of the time... until it doesn't.

I'm also updating old .html pages to .php and replacing some of the with php include statements on all pages when some of the pages displayed [an error occurred while processing this directive].
The pages displaying the error also referenced an old .ssi file that wasn't even in the directory it pointed to. I deleted the old includes code to the non-existent .ssi file in those pages, and that fixed the error.

This error occurs when you have in your code html documentation like this
<!--#My awesome documentatacion-->
to fix it remove the #, like this
<!-- My awesome documentatacion-->

Why don't SSI's work for me?

I'm trying to include one html file into another. I'm coding on the MAMP stack. I assume SSI's are automatically permitted. I type
<!--#include virtual="header.html" -->
in the body of one html file, the other file is called header.html, and they are both in the same folder. I even tried calling the file header.shtml instead. None of this works. It's frustrating.
The code isn't included. I'm including a form and a navigation bar, but they don't appear.

I assume SSI's are automatically permitted
That's a very big assumption. SSIs will only work if you've got mod_include loaded. You also need to enable the filter for the relevant files, e.g.
AddOutputFilter INCLUDES .shtml
...and of course ensure that Includes are not overridden elsewhere in the config.
Did you read this?