I need to block the execution of coldfusion debug ...
# cfml-general
n
I need to block the execution of coldfusion debug in my project, any advice? Possibly without Coldfusion Admin
a
I think cfsetting should do it:
setting showdebugoutput=false;
/
<cfsetting showDebugOutput="false">
n
showdebugoutput=false is used to hide the result of the execution, for my project i need that coldfusion debug doing nothing if i add in my url _cf_nodebug=true coldfusion debug is “set off”, but I don’t want to write this tag in all url about my project
a
Oh so you are talking about the AJAX calls?
n
all calls, not only AJAX for example “/area-personale/i-tuoi-prodotti?userId=96” this is one of my url (not AJAX)
a
Not sure then. I don't think you can stop it collecting debug info (even if it doesn't display it) without Admin / API access.
a
I know you said "without the use of CFAdmin", but the entire approach here is treating the symptom, not the problem. Switch debug off. Don't have it on and then suppress it. Just... don't have it on
💯 2
r
@Marco Liverani This has been answered in multiple threads. You need to run the one site you want to disable debugging for in a separate instance of ColdFusion. Either using the multiple instance support built-in to Adobe ColdFusion Enterprise, docker containers, or Commandbox.
d
If you don't mind me asking, why does it matter what CF does under the hood if it's not displaying anything? If this is about optimizing performance, I doubt this the one final thing that's the problem. What else could it be that makes you care so much about this?
m
It’s not what we see, but what happens behind the scene. If I keep the CF debug on, Wirebox objects creation costs up to 40/50 ms for every instance (depending on the object complexity), while is almost negligible with the execution time tracking disabled. Assuming that I’m not able to disable debug, I don’t know what else I have to consider.