I have been looking into solutions for quicker reaction times when changes are needed on our company website. Because of the fact the page-number keeps growing, more and more do I need quick solutions.
I planned on using SSI for including headers, footers and menus into my pages. The skeleton of the webpages would be set up in a format, and applied to all pages (to avoid overusing SSIs, and losing overview).
SSI seemed like the perfect solution, and it even seemed to be supported by the company server (a check mark behind an option called "SSI support" in the configuration menu seems pretty straight-forward). Sadly, when testing (both with an .html and an .shtm file) the opposite was true. After having directly contacted the help desk of our server, I was given this response:
"Despite the fact we have this option in the Control Panel, we sadly do not provide support for this function. This because our domains and websites are based on an IP-shared address, and therefore this option is sadly not possible."
1) I do not really understand how these two depend on one another (SSI and IP-shared addresses), so this would be my first question.
2) After some internet research, I came across this option: FakeSSI is a Perl program supposed to emulate the SSI function, and according to my server's configuration, I should be able to upload it to the cgi-bin and run it from there. I haven't got a clue as to how that would work, but nothing can't be solved by some research, so that's not really the problem. Where to start looking... THAT's the problem. Plus, I don't even know if this would be a good idea.
3) I already use several iFrames on the website, which always do their job. Could I not just use iframes instead of SSI? I do not want to use PHP-include, as it would require changing all .html files to .php files, and I don't want to lose all the outside links we currently may have out there.
Any help in the above questions would be greatly appreciated... Thank you very much in advance!!!
You could do worse I suppose.
