Yes, I used the debugger, sometimes.
I'm absolutely sure I can have a working setup for the debugger, but
sometimes it is not easy. Also in our team we had a lot of problems, getting
the debugger to work. In some cases it might be easier to use the
administrator settings and an occasional javascript alert, which is
dynamically generatied.
But if you want the full power of the debugger, read on...because it really
can work fine.
Some of the problems are:
It doesn't work well with IE 5. It worked fine with IE 4 and I have
demonstrated this several times in some courses how handy this debugger
thing can be. But with IE 5 things changed, since it doesn't seem to work
well with FORM variables, which are quite essential for debugging. There is
a workaround, according to Allaire, but although I posted this several times
in beta forums, they never gave me an answer which workaround this might be.
I discovered one myself:
Change the enctype in a Form tag from
<form action="" enctype="application/x-www-form-urlencoded "> to
<form action="" enctype="multipart/form-data">
and FORM variables are visible. It is not very elegant that you have to
change your code to enable debugging, but well, it works....
Other problems you might encounter:
If you run several websites on ports other than 80, a very common setup for
a test environment, the debugger fails. You can prevent this by not working
with port numbers but with named hosts in the headers. This works fine.
You have to be very picky about the developmappings in CF studio. Problem is
this dialog box is not very intuitive, but again, this can be done.
Next point is when you start the debugging session, it's often pointing by
default to the wrong server, wrong development mapping etcetera. When you
start your session check your RDS server AND start URL.
One more point. If you are debugging you want to spent some time stepping
through your code. If you have low timeout settings in your server, e.g 15
seconds, which is quite reasonable for normal use, your debug session will
also timeout. So change your timeout settings or append the session timeout
on your start URL, this might also work.
Last problem: if you made a mistake with some of the above points, CF studio
will crash sometimes, especially on Win 98. Sometimes the CF RDS service
needs a restart after some of these mistakes.
O yes, one more. If you are trying to debug a custom tag, it doesn't always
recognize the right attributes, or can't even find the custom tag code,
especially if this code is not in your template directory.
Yes, it is a bit buggy, but if you are a bit careful, you can use it.
But again, sometimes it might be easier to roll your own custom tag for
debugging purposes.
-----
Wil de Bruin
------------------------------------------------------------------------------
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
