Hello afinlr,
when I was getting to grips with links I had a few different build folders before i went live. It is, I thought, quite nifty that you can go to setup and tell it to build with whatever extension you want so changing to *.shtml isn't too difficult, you just tell it to use a different extension, rebuild and there it is.
Overall, from previous posts, I think your knowledge is far greater than mine for code etc so I really don't think SSI would cause you a problem, it's pretty much the same as all the globals tags in Links but you need to have *.shtml on the end.
The other thing that can trip you up is remembering that ssi only works in parent>child i.e you cannot <!include> a file from another website etc.
I would suggest having a play with another page in your directory to see how it works for you, editing the httpd.conf file is a whole new ball game and not something I have been involved in. I could be wrong but I don't think editing it will help, I honestly do not know though.
Cheers
KevM
when I was getting to grips with links I had a few different build folders before i went live. It is, I thought, quite nifty that you can go to setup and tell it to build with whatever extension you want so changing to *.shtml isn't too difficult, you just tell it to use a different extension, rebuild and there it is.
Overall, from previous posts, I think your knowledge is far greater than mine for code etc so I really don't think SSI would cause you a problem, it's pretty much the same as all the globals tags in Links but you need to have *.shtml on the end.
The other thing that can trip you up is remembering that ssi only works in parent>child i.e you cannot <!include> a file from another website etc.
I would suggest having a play with another page in your directory to see how it works for you, editing the httpd.conf file is a whole new ball game and not something I have been involved in. I could be wrong but I don't think editing it will help, I honestly do not know though.
Cheers
KevM