Okay, problem solved.

I missed the file in my first search attempts because I searched my entire wwwroot, and I had a bunch of ajaxcfc code examples in there and other bits and pieces that did include a <cfsetting showdebugoutput="false">. This time around I narrowed it down to just the application in question and the include directory where we keep some common files and most of our cfcs.

Just recently, I've written a few things using ajaxcfc and it turns out that the ajax.cfc file includes a <cfsetting showdebugoutput="false">. Well, I have a base component that I call "base" (strangely enough), and I had it extend ajax.cfc. All my other components were extending base. duh.

Well, I was just about to ask how I should best fix it. My first thought was to put the <cfsetting showdebugoutput="true"> in the application.cfm, but then Ken Ferguson jumped in with the answer before I could even ask the question! :)

I put the code at the end of our OnRequestEnd.cfm and it works like a champ!

Thanks guys. I really appreciate the help. :)

Chris

Dave Shuck wrote:
Maybe search for just "showdebugoutput".   They could have other parameters in there as well.

~Dave

On 8/11/06, Gistech Gistech < [EMAIL PROTECTED]> wrote:
As Dave is saying: you've checked other CFMs, right?

>>> [EMAIL PROTECTED] 8/11/2006 8:38 am >>>
Is it possible that another developer dropped in a <cfsetting
showdebugoutput="false" /> somewhere in the code?

~Dave

On 8/11/06, Christopher Jordan <[EMAIL PROTECTED]> wrote:
>
>  Hi everyone,
>
> I've got a problem that I'm wondering if someone on the list has
grappled
> with before. For some reason yesterday, my CF development server
just
> stopped displaying any debugging information.
>
> I have done the following to try and correct the problem:
>
> 1. checked in the CF administrator to be sure that debugging was
indeed
> enabled. It is.
> 2. checked to see that my IP is in the list of IPs able to receive
> debugging. It is.
> 3. checked my machine to see that my IP hadn't somehow changed. It
hasn't.
> 4. started completely new browser sessions.
> 5. tried different browsers (FireFox).
> 6. removed all IPs from the debugging IP list so that *everyone*
would get
> debugging output.
> 7. restarted all CF services. (twice)
> 8. soft boot of the server.
> 9. hard boot of the server.
>
> Can anyone else think of anything that I haven't tried that might
help us
> to get our debugging information back?
>
> Thanks,
> Chris
>
> _______________________________________________
> Reply to DFWCFUG:
>  [email protected]
> Subscribe/Unsubscribe:
>  http://lists1.safesecureweb.com/mailman/listinfo/list
> List Archives:
>     http://www.mail-archive.com/list%40list.dfwcfug.org/
>  http://www.mail-archive.com/list%40dfwcfug.org/
> DFWCFUG Sponsors:
>   www.HostMySite.com
>  www.teksystems.com/
>
>
>


--
~Dave Shuck
[EMAIL PROTECTED]
www.daveshuck.com
www.worldwildweb.biz

_______________________________________________
Reply to DFWCFUG:
  [email protected]
Subscribe/Unsubscribe:
  http://lists1.safesecureweb.com/mailman/listinfo/list
List Archives:
     http://www.mail-archive.com/list%40list.dfwcfug.org/
  http://www.mail-archive.com/list%40dfwcfug.org/
DFWCFUG Sponsors:
   www.HostMySite.com
  www.teksystems.com/



--
~Dave Shuck
[EMAIL PROTECTED]
www.daveshuck.com
www.worldwildweb.biz

_______________________________________________ Reply to DFWCFUG: [email protected] Subscribe/Unsubscribe: http://lists1.safesecureweb.com/mailman/listinfo/list List Archives: http://www.mail-archive.com/list%40list.dfwcfug.org/ http://www.mail-archive.com/list%40dfwcfug.org/ DFWCFUG Sponsors: www.HostMySite.com www.teksystems.com/


_______________________________________________
Reply to DFWCFUG: 
  [email protected]
Subscribe/Unsubscribe: 
  http://lists1.safesecureweb.com/mailman/listinfo/list
List Archives: 
    http://www.mail-archive.com/list%40list.dfwcfug.org/             
  http://www.mail-archive.com/list%40dfwcfug.org/
DFWCFUG Sponsors: 
  www.HostMySite.com 
  www.teksystems.com/

Reply via email to