Hi All,
A lot of programmers spend lots of time tracking down the values of their hidden
APPLICATION, CLIENT, SESSION and REQUEST variables to verify that the contents of the
variable contain the expected values. They typically do this by writing temporary
output code to display the variables, which then gets commented out. So, comment in,
comment out, comment in, comment out, ad nauseum.
It is also hard to know on a large project if some other programmer has an
application, session or client variable that you SHOULD be using, or that you should
NOT create a new one with the same name. For example, where can I get a neat listing
of all my application variables, so that I can use them immediately if I don't happen
to remember the exact spelling right away, or I want to make sure I am using it in the
correct context? Where can I get a neat listing of all my client variables, in case I
want to re-use one, or make sure I am not overwriting an existing variables?
You may have noticed that the standard CF debugging information does not display these
critical variables, while it does display CGI, FORM and URL variables, as well as
exploded paths and run times for the modules, and query results.
Don't you think something is missing from the basic CF debug display screen?
I have written a module that displays these missing variables, and it is activated
based on IP address, just like the standard CF debugger. In addition, it has a domain
level control, so you can let everyone in say "207.128.33" see the debug information,
which is likely to be all the developers in your company working on the application.
There is also code (commented out) that lets you turn on the debug info based on some
internal variable, say UserID. So, after you log-in as admin, you get to see the
debug code.
I am telling the list about this for 3 reasons:
1) I think it is extremely useful code that I want to share with you (aren't I nice ;-)
2) I would like you to try this code out and give me your feedback.
3) I am wondering if it would be appropriate to include it in a standard library of
FuseBox tags.
HOW TO USE THE MOD_DISPLAY_VARIABLES.CFM TAG
============================================
You will have to do some tweaking to get it to work with CF 4.01. Some of the scopes
only become structures in CF 4.5
1) Since this list does not do attachments, download from here:
http://www.teratech.com/download/mod_display_variables.txt
2) Rename the file to be mod_display_variables.cfm
3) on lines 43 and 44, modify the allowed domains and IP address.
4) On line 62, modify the scopes you want displayed, or if they are giving you errors.
Currents scopes displayed: APPLICATION,CLIENT,SESSION,FORM,URL,COOKIE,CGI and some
SERVER variables.
4) Put a reference to in your on OnRequestEnd.cfm, for example:
<CFMODULE template="CF_LIBRARY/MOD_DISPLAY_VARIABLES.CFM">
====================================================
Douglas M. Smith - Database Architect/Web Integration Specialist
====================================================
TERATECH, INC. - TOOLS FOR PROGRAMMERS(tm)
VisualBasic, Web (ColdFusion and ASP), Math and Statistics,
Access, SQL, programming tools & consulting
100 Park Ave, Suite 360, Rockville MD 20850 USA
Voice: 301-424-3903, Fax: 301-762-8185
http://www.teratech.com
====================================================
Email: [EMAIL PROTECTED]
Mobil/Cell Phone: (240) 601-5520
ICQ: 41044319
====================================================
Do you need a group calendar or scheduler?
How about a free ColdFusion Tag and Function Reference?
Go to http://www.teratech.com/freestuff.cfm
====================================================
------------------------------------------------------------------------------
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.