if you had pages call themselves you would be stuck in a loop.
it would be possible to drop the content of a page using output and CFFILE,
but I would suggest using CFHTTP to call and save the pageslike so,
http://www.some.com/myFile.cfm"; method="GET"
name="fileName.html" path="C:\Inetpub\w
Have a different page loop through all pages on the site, call the page
using and save that as the static .htm file.
>>> Ben Whalley <[EMAIL PROTECTED]> 10/03/01 11:33AM >>>
Ok,
I have been trying to think of ways to create a static copy of a site for
Verity to index properly. At the moment it
Rather than a CFLocation, I'd create your static file names such that
you know what parameters are going in -
Something like cart.cfm?catid=5&productid=39 would become
cart_cfm_catid_5_productid_39.htm
In your Verity search results, rather than sending this user to this
htm, catch the file name
There is a much easier way
use cffile to list all of the .cfm files in the desired directory(s),
then loop through them using cfhttp to read in the text of the page.
I have an html style comment in the pages that I don't want indexed that
just says .. so I see if that text is in the
t: Re: creating a static copy of a site
There is a much easier way
use cffile to list all of the .cfm files in the desired
directory(s),
then loop through them using cfhttp to read in the text of the page. I
have an html style comment in the pages that I don't want indexed that
just sa
5 matches
Mail list logo