Sounds like another job for CFHTTP.
You could:
1. Leave the help pages unchanged
2. move them to separate directory
3. rename the help's index.html, default.html, welcome.html page so it can't
be inadvertently be accessed
4. Write a CF template "command module" to replace the above and:
a. use CFHTTP to retrieve a requested help page
b. parse the help page repointing links, form actions, etc. with a link
back to the "command Module" (passing the original link address as
a link parameter)
c. Serve the "repointed" page to the user.
Each page that the user requests is dynamically repointed to return
to the command module.
This works really well... I have used this approach to harvest MY ISP
docs, which in turn linked to CFDOCS which, in turn linked to MS
docs, which in turn...
Some added benefits are:
you can control placement of the requested pages in a separate frame or
(popup) window
you can add navigation buttons, graphics etc. (within the displayed page or
in a separate frame.
you can remove unwanted information.
You can add context-sensitive customization
you could log page accesses to monitor the effectiveness of the help system.
HTH
Dick
At 6:19 AM -0400 6/16/2000, Rod Tosten wrote:
>To All-
>
>we have a help system that produces html pages and an associated index. to
>provide security for the pages we are embedding coldfusion tags into the
>help files. we then hacked the mod_coldfusion.c file to process .html
>pages as .cfm pages. our concern is that allaire will change this file
>under us in some future release. can anyone suggest a different method
>and/or knows if allaire will maintain the mod_coldfusion.c file in future
>releases.
>
>thanks,
>
>-rod
>
------------------------------------------------------------------------------
Archives: http://www.eGroups.com/list/cf-talk
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
