I have a weird situation that I have never come across before.  I am
writing a search output page that I would like to display a custom message
to the user based on what page name they are currently viewing.  I use
_javascript_ to determine this message bases on the url string.  (This page
is getting generated on the server several times with different .html  page
names for search engines, so I have to use _javascript_.)

The question I have is that when I use a cfinclude inside document.write(),
the next time I view the page code on the generating page (a .cfm page),
the cfinclude is gone, and the code that I was including is in there
instead, with some other file references, etc.

For clarity, here is what I am doing:

list_result.cfm is the page that is generating these html search engine
pages.  Those pages get overwritten every day (to reflect the most current
snapshot of the DB) by using cfhttp and saving the file results to an html
file.  When I run the page generator, the code in list_result.cfm gets
altered.

Is there a way to stop this from happening?  Why would the code get changed
on a page that is just getting hit by cfhttp?

Thanks,

Ray

=============================================
Ray Champagne - Senior Application Developer
CrystalVision Web Site Design and Internet Services
603.433.9559
www.crystalvision.org
=============================================

The information contained in this transmission (including any attached
files) is CONFIDENTIAL and is intended only for the person(s) named
above. If you received this transmission in error, please delete it
from your system and notify us immediately. If you are not an intended
recipient, please note that any use or dissemination of the information
contained in this transmission (including any attached files) and the
copying, printing, or retransmission of that information is strictly
prohibited. You can notify us by return email or by phone at 603.433.9559.
Thank you.
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]

Reply via email to