This is something I've been meaning to do for awhile. I want to dynamically generate my detail pages on some sites, where the build takes 10 minutes for pages that no one ever looks at.

Premise: I want to use a standard detailed.html file, and auto-generate it (like Search or Add) with none of the paths turned into dynamic stuff.

So, I cut page.cgi apart, and got the following script.

Cut the following script, call it detailed.cgi, and you call it by:

detailed.cgi?ID=nnn

instead of using a hard-link or jump.cgi to call the detailed page (if you were using my modified jump.cgi) use detailed.cgi?ID=<%ID%> instead. It even works with page.cgi sites... though why you'd want to do that, I don't have a clue <G>

There may be other more efficient ways of copying large blocks of code from this forum (w3t formats the copied text as being all one line), but this works for anyone struggling with it: View the source code and copy the appropriate section, then do a find and replace, replacing tags with a hard enter. Not all editors allow multi-line replacements (needed for the hard enter to serve its purpose), but the Arachnophilia HTML editor is one that does so quite nicely.

Try this (if you have it) it works fine. Save the page to your hard drive, load it up in MS Word (stays as HTML) and then save it in ascii.txt format with line breaks. Takes a couple of minutes and works like a charm!

ALSO, on page.cgi - I use .shtml as I use SSI extensively. It appears as though page.cgi will not work with the SSI extension. It leads me around the garden path when I try to use it.

Any suggestions?

BTW - will detailed.cgi work with LinksSQL NG? I am impressed with it!

Clint...as far as getting the SSI's you want to use working, you could extend the SSI script(s) to update to a seperate storage file whenever additions/modifications are made by that SSI, then use <%include /path/2/ssi_file.txt%> it's the only way I could figure it, but I couldn't find ways to extend all the SSI's to do it (Banners, etc...). It Would be nice if there was a perl module (cgi.pm style) that could parse included SSI routines into a cgi script [&ssi_into_cgi($ssi_script)]. But until then this is probably the only way to get them working together; besides because of the output and the handling method differences between CGI and SSI I don't see it as being possible.

Gossamer Threads is a Vancouver-based company with over 24
years experience in web technology. From development to hosting, we
partner with leading organizations around the globe and help to build
their web presences, strategies and infrastructures.