That printing problem happens to me too. Pain in the......
But i've got another question. My servers are located in a data centre. And
if I turn on debugging for my IP address it turns on for the whole
organisation and people start calling me saying they are getting "weird SQL
errors" below the page.
So i was thinking of doing a OnRequestEnd.cfm page and putting it in the
same folder as every Application.cfm on each of my servers.
I'd love to use just one OnRequestEnd but from the docs....
"The OnRequestEnd.cfm page must be in the same directory as the
Application.cfm page ColdFusion uses for the current page. ColdFusion does
not search beyond that directory, so it does not run an OnRequestEnd.cfm
page that resides in another directory."
In this file i could have something like:
<cfif cgi.REMOTE_ADDR eq "my IP address" AND isdefined("url.debug") AND
url.debug>
<cfdump var=#form#>
<cfdump var=#request#>
<cfdump var=#application#>
etc
So my questions are:
1. Is there a better way?
2. Can i just output the debugging info using <cfsetting
showDebugOutput="yes"> so it would show all the SQL etc?
Thanks
Gav
----- Original Message -----
From: <[EMAIL PROTECTED]>
To: "CFAussie Mailing List" <[EMAIL PROTECTED]>
Sent: Friday, April 23, 2004 10:02 AM
Subject: [cfaussie] CF Debugging printing oddness
I have an odd thing that's been happening to me for a while, and I'm really
getting sick of it.
If I'm looking at a ColdFusion generated page and I have debugging turned on
the CF Server, I get the usual screens and screens of useful debugging
information below my page. So far so good.
If I print this page, I get the non-debugging info portion of the page just
fine, but then I get at least 5 pages of the HTML code that makes up the
debugging information. Its exactly what you would see if you did a 'view
source', but only for the debugging portion of the page and only when it
gets printed.
If you've ever viewed the source of the standard CF debugging html code, you
will know that it starts with a long string of HTML closing tags, like this:
</td></td></td></th></th></th></tr></tr></tr></table></table></table></a></a
bbrev></acronym></address></applet></au></b></banner></big></blink></blockqu
ote></bq></caption></center></cite></code></comment></del></dfn></dir></div>
</div></dl></em></fig></fn></font></form></frame></frameset></h1></h2></h3><
/h4></h5></h6></head></i></ins></kbd></listing></map></marquee></menu></mult
icol></nobr></noframes></noscript></note></ol></p></param></person></plainte
xt></pre></q></s></samp></script></select></small></strike></strong></sub></
sup></table></td></textarea></th></title></tr></tt></u></ul></var></wbr></xm
p>
<style type="text/css">
.cfdebug
The oddest thing is that the printed HTML code only starts at </PLAINTEXT>,
and then goes on from there. No debugging HTML code before the </PLAINTEXT>
tag is ever visible on any page's printout.
Is there some magic in the </person> tag just before the plaintext one?
It happens on every PC here that I tried it on, and it does it to every CF
app I tested, even though they have very different coding styles and
origins.
We run CFMX6.1
Has anyone ever seen this before.
Has anyone got a clue what might be causing it, or how I might stop it from
happening?
---
You are currently subscribed to cfaussie as:
[EMAIL PROTECTED]
To unsubscribe send a blank email to
[EMAIL PROTECTED]
MXDU2004 + Macromedia DevCon AsiaPac + Sydney, Australia
http://www.mxdu.com/ + 24-25 February, 2004
---
You are currently subscribed to cfaussie as: [EMAIL PROTECTED]
To unsubscribe send a blank email to [EMAIL PROTECTED]
MXDU2004 + Macromedia DevCon AsiaPac + Sydney, Australia
http://www.mxdu.com/ + 24-25 February, 2004
