[thelist] <cferror> and NT/Unix differences

[scott.brady at homeqonline.com]

No, this Unix box is running 4.5.1 with no service packs, while our NT boxes are
running 4.5.1 SP2.  The only other Unix box we have is running 4.0, so it's not
something we can test on.

I'll look up Charles and see if there's anything there to help.

Thanks for the help!  I'll keep looking.

Scott





"Benekli" <benekli at benekli.net> on 04/05/2001 02:22:41 PM

Please respond to thelist at lists.evolt.org

To:   thelist at lists.evolt.org
cc:    (bcc: Scott Brady/TMS)

Subject:  RE: [thelist] <cferror> and NT/Unix differences


The logic is fine except that the Unix box is running 4.0 right? I don't exactly
remember how 4.0 behaved but I do know that the error mechanism has changed a
bit
since then. For one there's site wide error checking in 4.5 enabled via the
admin
panel. You can also now execute cftags from the error templates where as
previously
the cfServer would stop processing and abort cftags. Look up Charles Arehart on
the
cfdj site, if I remember correctly he had a three part article dedicated to
error
handling. One last note is that I do believe the type="exception" did NOT exists
in
4.0 along with type="monitor".

Benekli17:21P05IV2001

<->However, when the cferror file wasn't found during development, we'd get an
<->error any time any page was loaded saying that the template file could not be
<->found.  So, I would expect it to do the same thing on Unix (no matter if the
<->page has an error or not, app_globals.cfm would choke on <cferror>).  Is that
<->not a good expectation?

---------------------------------------
For unsubscribe and other options, including
the Tip Harvester and archive of TheList go to:
http://lists.evolt.org Workers of the Web, evolt !