CF "Enable Request Debugging Output" can break Dynamic XML

I have XML flash slideshows for a client's site that builds a dynamic XML which then is used in a .swf file

This morning, all I see are malformed XML Flash errors on my dev server's xml calls. across the board. everywhere. ARRGGH!

Flipping on Firebug, I see that the end of my XML files contains some CF debugging statements that should not be there. Turns out, the issue arose yesterday when I turned on CF Administrator's 'Enable Request Debugging Output' feature to get some feedback on some dynamic SQL statements being created.

With this feature turned on, the CF debug statements at the bottom of the page get sucked into the XML as part of the file generated. Very interesting indeed.

(disclaimer - of course you should _never_ have Request Debugging Output enabled on a production server :) )

Comments (Comment Moderation is enabled. Your comment will not appear until approved.)
Raymond Camden's Gravatar Don't forget you can turn off CF debug info on a per request basis using cfsetting. This allows you to turn on debugging and not have it break stuff like this.
# Posted By Raymond Camden | 10/12/11 6:56 AM
Brian Swartzfager's Gravatar Yep, any sort of debugging output (whether from the CF server itself or from an application framework like Model-Glue that provides it's own type of debug output) will mess with files meant to return pure XML.

Fortunately, if you're in a test environment where you can't turn off the global debugging output setting, you can use the cfsetting tag's showDebugOutput attribute to toggle the output on and off.
# Posted By Brian Swartzfager | 10/12/11 12:07 PM
BlogCFC was created by Raymond Camden. This blog is running version 5.9.1.002. Contact HHWD