On 2/18/2004 at 11:57, you wrote:
JM> I wasn't aware of the type="exception". Why would it preclude
JM> capturing user comments as might be entered into a form?
It doesn't prevent you from having a form to capture user comments,
but it removes the dependence on the user for getting error details
submitted. A dump of the error scope (and perhaps cgi and session) in
a CFMAIL gets you the information you need to troubleshoot most--if
not all--errors.
>> If your site is on a dedicated server, you can also configure a
>> server wide error handler in CF Administrator (which allows CF code
>> as well) that will catch all errors--no need for CFERROR.
JM> I'll look into that. So long as I can detect which web site and
JM> which template it came from (or at least which physical file the
JM> error occured in).
The error structure contains all the information you'll need to locate
the problem template. Customize the presentation of your server-wide
error handler by checking the cgi.server_name variable, if need be.
>> As for the form processor for your existing set up, Philip's
>> suggestion of a mapping is a good way to go.
JM> Are we talking about a CF-server level mapping?
Yes.
>> If you are unable to set up the mapping, simply place a form
>> processor 'shell' module in each sub-directory that does nothing
>> but CFINCLUDE your common processor code.
JM> Ugh.
Didn't say it was graceful :)
~ Ubqtous ~
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
