Anyway, I did not interprete "accidentally append debug output when serving XML documents via CF" as that one needs to turn off debugging when doing XML stuff for turn on debugging for development is pretty standard, I can't seem to align "standard" and "accidentally" together.
If I were MM, I would set a check before executing any XML family tag to turn off debugging if not. Wouldn't it be better this way by design? Overhead? Totally necessary.
>>Dave,
>>
>>Please elaborate on "it's common to accidentally append debug output when
>>serving XML documents via CF.". Thanks.
>>
>
>Different Dave, but I believe he means that if you're serving this XML
>document via CF and you have debugging turned on (i.e., in development),
>then MX will add a bunch of debugging code to the bottom of the document
>(just do a View Source on a CF page with debugging and you'll see). You'll
>need to explicitly use
>
><cfsetting showDebugOutput="No">
>
>to suppress and attempt by CF to output debugging code. This extra code will
>of course make this XML document invalid.
>
>Regards,
>Dave.
>
>
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
