I found this uncommitted change to a file on one of our shared dev servers today:
<CFIF IsDefined("request.traceactive")><CFELSE><CFSET request.traceactive = "false"/></CFIF> <CFSET request.traceactive = 'false'/>
I don't even know where to start…
By barneyb on January 30, 2009
I found this uncommitted change to a file on one of our shared dev servers today:
<CFIF IsDefined("request.traceactive")><CFELSE><CFSET request.traceactive = "false"/></CFIF> <CFSET request.traceactive = 'false'/>
I don't even know where to start…
Copyright © 2024 Barney Boisvert.
That is pretty awesome.
Doesn't that need a CFLOOP to work properly?
Kill it before it spawns!
boy, sure would look better with a CFSET request.traceactive = 'true' at the top. ; )
I was wondering where I left that! ;-)
I like that the first false has double quotes and the second one has single quotes :( Other than that, it's awesome :)
I am going to start, from now on, putting that at the top of every file I create
@Ben, yeah, it's like the first one is going
cfset request.traceactive equal to (air quotes)false(/air quotes)
Scary thing is, one of the developers in my group has core template files that he copies from that have junk like that.
I found something almost exactly like this on one of my acceptance servers one day a couple months ago — also uncommitted — but with the addition of a preceding that defaulted the variable to "false" (yes, with quotes)… I sat and scratched my head for a few minutes on that…