🚀 go-pugleaf

      What is the easiest way to do a server side include in Golive CS. I'm
      new to this and what i have done has been hand coded in front page.




Download the golive SSI extension. It will add a palette item that you drag and drop onto a page, then from the inspector, link to a file with an HTML snippet (no head, body or title tags need to be there).

Then it will show up in the page in layout and preview mode. Change the include file, save and do a refresh of the page by going to preview then back to layout and the change appears.

 <http://share.studio.adobe.com/axBrowseSubmit.asp?c=14>

It is about the 12th item from the top. You can also open the file of the extension, named Main.html (don't edit-it's got programming) and read over some of the details.

Actually, after you have installed the extension, any time you hand type in the SSI call, it will automatically show it.

I don't use SSI very much anymore, but I have a bunch of legacy sites where I did, and it makes things very pleasant since I have a visual indicator, heck, the real thing, in my page.

Thanks Jim,

I have got the extension installed, but it will not let me preview the page. When i goto preview it just shows the page smushed (since it doesn't see anything in those table cells. It does work, but right now i just have to upload my pages to the server to check them. Anymore advice would be great.

Thanks for the reply,

@Nathan Ziglar - smushed and won't preview!

Are you doing this in a site? What do you have in your include file - just HTML, right? You are not trying to do ExecCCI or doing any sort of programming with SSI are you? The SSI extension will only display HTML from an include, and it needs to be a snippet of HTML rather than a whole page.

If doing SSI programming, it has to go through processing of the server.

For SSI, what I do is create New>Text File, then when it bops up as untitled.txt, I wipe it out and name it with an .inc ending ->

filename.inc

For some reason I can still edit the file as HTML, but woe unto you if you try to rewrite the source code!

ok jim i have a better handle of what is going on.

I'm using ASP to do the ssi...i'm using a simple <--! #include file="file.html"--> command. Today i did a with the extension .html, and the include previewed in golive, but when i do this my include is not used once the page is up loaded on the server.

Example with .asp
 <http://www.baptistcollege.edu/home.asp>

Example with .html
 <http://www.baptistcollege.edu/home.html>

The html page will not display the footer that is in the include. So have to revert back to nameing it with the .asp extension which caused golive to quit displaying it.

I don't understand fully what is going on. Thanks so much for the help.

Ah, I do understand - I've worked with extensions. It's simple really.

The Translate SSI extension has a set of params that tell what file extensions it will work with: html, htm, shm, shtml. asp isn't included, so you just get a little comment icon.

Go to where you have the Translate SSI extension installed, which is:

C:\Program Files\Adobe\Adobe GoLive CS\Modules\Extend Scripts\Translate SSI

Find the file named Main.html.

Open it up in GoLive CS.

Scroll down the page until you see the Translate SSI icon, and right below that is a blue thing that says jsxtranslator with a right pointing arrow.

Click the arrow to open it up.

You will see five params. With the Inspection where you can see it, click on them one by one.

It will show a list of Attribute Value pairs.

name - extension
value - html

Click on one of the params that has the name attribute set to extension and the paste it next to the others. In the inspector, change the value from html, htm, shtml,shtm to asp.

You can also just click on a param and drop to source view if that is easier (actually, it's easier to see)

After you have finished, you should have another param with the name attribute set to extension and value set to asp.

param name="extension" value="shtml"

      param name="extension" value="asp"




param name="expression" value="#include"

Close and save the file, close and restart Golive.

Now files with the ASP file extension will work when using the Translate SSI extension.

enjoy!

Thanks once again Jim,

Ok, here is my next and probably final question on this topic. I'm asking this so i'll have a better understanding of how this extension works.

When I was unable to preview the SSI in the page, the inspector let me choose the type (relative, virtual, php, etc), but now that i can preview the include it will only write code for virtual. I can hand change the code to (relative) and it will continue to function. I would love for the inspector to let me choose or force all new includes to be relative.

Thanks for all your help!