Ajas, is there by any chance code with the same file name in the CF wwwroot
as well as in your external web server docroot? (such as in [cf8/9]\wwwroot,
or [jrun]\servers\[instancename]\cfusion-ear\cfusion-war\, or
[cf10]\cfusion\wwwroot, or [cf10]\[instance]\wwwroot)? And beyond just the
root, how about in any subdirectory structure that might match that in the
external web server root?

I'm wondering if you are having a situation where someone is occasionally
creating a file of the same name and path in the internal wwwroot as in the
external, and CF is caching that, but then when it's removed, CF gets an
error. This is just a wild guess. I don't know that it would or should
happen.

But many don't realize that CF does indeed search in both the internal and
external web server roots for files, so that if you have files of the same
name in them, there can be confusion (you edit one and not the other, and
"never see" the change reflected when you browse the page, because you
didn't realize there was this "shadow" page that CF was finding.)

 

/charlie

 

From: [email protected] [mailto:[email protected]] On Behalf Of Ajas Mohammed
Sent: Friday, August 17, 2012 4:10 PM
To: [email protected]
Subject: Re: [ACFUG Discuss] CFC path - bind autosuggest issue

 

And the error happened again. My colleagues renamed the CFC to lets say
Employee1.cfc & refresh page and then renamed it back to Employee.cfc and
its working fine again. Earlier, I was adding a space or introducing an
error myself by adding single pound and then refreshing page and then
removing pound and refreshing page to make the error go away.

This is weird stuff.

<Ajas Mohammed /> 

 




-------------------------------------------------------------
To unsubscribe from this list, manage your profile @ 
http://www.acfug.org?fa=login.edituserform

For more info, see http://www.acfug.org/mailinglists
Archive @ http://www.mail-archive.com/discussion%40acfug.org/
List hosted by http://www.fusionlink.com
-------------------------------------------------------------

Reply via email to