Hiding Debugging on Certain Apps

[Brimard]

Greetings,

Looking at implementing a CF-based CMS.  Right now, the staging server for static HTML pages is the development server for apps, and then a live server, and would like to do the same for the CMS.

Best of my limited CF knowledge, debugging is an all-or-none affair.  Debugging is turned on, all CF apps show the debugging, which interferes with the admin screen of the CMS, rendering some areas of the screen unusuable because debugging is turned on.

Is there anyway around this issue, ie turning off debugging at the directory level, or at least hiding it from the end user?

Being a cash-strapped non-profit, we are going the opensource route, so there's no money for a separate box, and any of our old desktops are of the Penium II variety, so we can't repurpose any other servers.

Best idea to find another debugger versus what comes standard?  ANything anybody can recommend to keep the CF Developers happy?

Thanks!

-B

[Guest]

Not sure which version of CF you're using but you can restrict debugging by IP address.  It is usually the link under turing debugging off or on.

[Charlie Arehart]

As ke4pym says, limiting by IP address would seem your best bet.

But beyond that, to your original question, yes it is also possible to set debugging on a per app (or per template) basis using the tag CFSETTING SHOWDEBUGOUTPUT="no", either in a single template or in the application.cfm/application.cfc controlling an app or a portion thereof.

To address your point: no, debugging in CF is not an all-or-nothing affair. It's really quite flexible.

/charlie

[Brimard]

CFSETTING SHOWDEBUGOUTPUT="no"

That still has debugging being processed though, correct?  Just not shown?

Looks like I have have a couple of different options, thanks folks!

[Charlie Arehart · Accepted solution]

Well, yes, but that is what you asked for (not showing it). You said, it " interferes with the admin screen of the CMS, rendering some areas of the screen unusuable because debugging is turned on."

Are you asking this follow-up just for edification? Or are you thinking that somehow the debugging still being processed but not shown would affect the appearance of your app? It would not.

There are indeed performance implications of debugging being on (whether it's shown or not, and whether by the tag or the IP address filter), but it didn't seem the focus of your question so I didn't address it. Just being clear now.

Have you tried either the tag or the IP address filtering? Have they solved your problem? If so, there's a mechanism in these forums to mark an answer as the answer to your question, and it's a great help to future readers of the thread.

/charlie

[Brimard]

Ayup, noticed the helpful and question answered radio buttons, used them on the first two replies.  Follow-up for clarification regarding terminology.