Server Side Includes (SSI) in a LiveSite Page

sgarimella

Hi,

I have a requirement to include SSI in a .page. These are the steps I performed:

I made sure test.shtml with SSI works on the Teamsite.

The iwwebd.conf is updated with SSI required configuration

Restarted the Teamsite and webserver after changes

Created a component that includes a basic SSI directive - <xsl:comment>#echo var="DATE_LOCAL"</xsl:comment>

Added the component to a page and previewed it.

I see no response.

We are using TS 7.4.1

Requirement:

The main drive to have SSI is to enable the include of a HTML form browsed in the component and display that browsed HTML as-is on a page. And most importantly, the HTML form browsed should be part of the Page View source.

Find more posts tagged with

Comments

nipper

I always have a problem wih requirements like this. The business should define requirements that do not specify a solution. The requirement would be to have a page display information that is shared with many other pages, have the ability to change the included data and see the changes.

No where should it say SSI should be supported. You can do that with components and DCRs easily.

That being said, SSIs work. You do not list what version of Apache you are using or how you configured it to work with TS/LS

The only bug that I know of with SSI that could cause this is if you use a different docroot (with preview, say /webdocs) SSIs are not picked up correctly with that config in APache 2.2

There are instructions in the admin maual. along with multuple logs you can peruse to see why they are not working.

sgarimella

We are using Apache 2.2 version.

Yes you are right.. There are below advantages using SSI.

1. The load on app server is reduced because SSIs are processed by the web server.

2. SEO (Search Engine Optimization) recommends having the HTML included as part of the view source of the Page where it is browsed. - thoiugh this could be achieved easily, the primary reason is the first point.

I tried the below part for including SSI

<Directory "/iwmnt">
   Options Indexes FollowSymLinks ExecCGI Includes
    Order allow,deny
   Allow from all
</Directory>

AddType text/html .page .shtml .html
AddOutputFilter INCLUDES .page .shtml .html

Directory iwmnt is the mounted content store in our teamsite.

nipper

Did you use apxs to build mod_a2_iw_ts_vpath.so ? Build the ssi,conf per the manual ? There is logging in the config, You can uncomment:

#RewriteLog logs/rewrite.log
#RewriteLogLevel 9

As to your points, #1 is wrong, the app server is reading a DCR from a local disk, that is very easy. Easier than a page load and then an Apache include as well.

For SEO, it is part of the page already so there are no SEO issue.

sgarimella

I will try the logging part and get back in a day.

The following is the way I can think of using a DCR,

1. Have a rich text editor in a DCR, ask the user to fit in his HTML and the component renders.

But our client already has ready made HTMLs which he has been using for some other app, so he does not want to rewrite the DCRs.

Can you think of any other way to reuse existing HTMLs?

sgarimella

In the manual also steps are detailed out to enable SSI for .shtmls.

Is there something different we need to do for pages?

@Nipper: When we use SSI in a page, dont we run into a problem where we see 2 HTML tags, 2 Body tags in View source of the page (1 Tag introduced by Livesite for the page and the other by the HTML file). How do people handle such problems?