Question
CFDEBUG not working on CF8 Server
My company is currently running CF8 Standard Edition, version
8,0,0,176276 on Windows 2003. I am currently working on building an
editable CFGRID data grid. I was unable to get the data grid to
ever return data, so I put some sample code available on Ben
Forta's blog on the system to test. Likewise, the CFGRID never
returned any data, and acts like it's infinitely waiting for data
from the CFC it's bound to. Copying the exact same files to a dev
server (same version of CF8, also running on Windows 2003), the
CFGRID works great. I tried to pull up the AJAX debugging window on
my production server by adding ?CFDEBUG=true to the end of the url
for the CFM file, but no AJAX debug div/window every pops up.
Meanwhile, the exact same thing does pop up the AJAX debug window
on the dev server. I've tripled checked and the Enable AJAX Debug
Log Window option is enabled on both the production and dev server.
At this point, I'm having to assume something is wrong with the installation on our production server. Unfortunately, I have absolutely no idea what could be the issue. Any help would be appreciated.
Some other little tidbits I'd like to add that may or may not have anything to do with this problem:
(1) Creating a simple HTML CFGRID where selectmode is not equal to "edit" does work, as far as returning data, but the CFDEBUG URL option still does nothing.
(2) Enabling debugging for my IP address in the CF Admin control panel has no positive effect, unless I set the debugging output format to "classic" instead of "dockable". If I run with "dockable", the application (not the AJAX) debug window is corrupted and has the following in the top part of the window:
(3) Just found this one out: if I set the debugging output format to classic, the cfdebug does work. but no errors show in the cfdebug ajax window.
Any ideas? Any help would greatly be appreciated.
At this point, I'm having to assume something is wrong with the installation on our production server. Unfortunately, I have absolutely no idea what could be the issue. Any help would be appreciated.
Some other little tidbits I'd like to add that may or may not have anything to do with this problem:
(1) Creating a simple HTML CFGRID where selectmode is not equal to "edit" does work, as far as returning data, but the CFDEBUG URL option still does nothing.
(2) Enabling debugging for my IP address in the CF Admin control panel has no positive effect, unless I set the debugging output format to "classic" instead of "dockable". If I run with "dockable", the application (not the AJAX) debug window is corrupted and has the following in the top part of the window:
quote:then it goes into the usual " ColdFusion MX Debugging" stuff, but none of the options are clickable. Is this normal?
'); } } function writeCloseBody() { if( debugMode ) { document.write(''); } } //============================== TREE STATE ============================== function setCookie( targetName, value ) { var cookieValue = targetName + "=" + escape(value); var exp = new Date(); var nowPlus30Days = exp.getTime() + (30 * 24 * 60 * 60 * 1000); exp.setTime( nowPlus30Days ); document.cookie = cookieValue + "; expires=" + exp.toGMTString() + ";"; } function getCookieValue( name ) { var thisCookie = document.cookie.split("; ") for( i=0; i
(3) Just found this one out: if I set the debugging output format to classic, the cfdebug does work. but no errors show in the cfdebug ajax window.
Any ideas? Any help would greatly be appreciated.
AdChoices