I found while googling for similair experiences another person having issues.
He seems to have a similair issue with cfcatch, cftry.
My code can be tested on everyone machine, because it should simply trigger the
cfcatch part when the session call errors.
The corresponding post from Tony Weeg
Parse errors are not caught with cftry/cfcatch. Reason being, the page
couldn't compile, so it couldn't even try/catch anything.
-nathan strutz
http://www.dopefly.com/
Micha Schopman wrote:
There are no parse errors involved. An expired session variable, in this case
session.cultureid should
I have errors which slip through ctry tags. The provided cfcatch part is not
executed and the source shows the error in the cftry part. Did anyone
experience similair behavior? I provided the responsible code below where
session.cultureid has not been filled in;
cftry
cfoutput
Parse errors are not caught with cftry/cfcatch. Reason being, the page
couldn't compile, so it couldn't even try/catch anything.
-nathan strutz
http://www.dopefly.com/
Micha Schopman wrote:
I have errors which slip through ctry tags. The provided cfcatch part is not
executed and the source
4 matches
Mail list logo
