>
> I have an ErrorDocument 500 in httpd.conf, and optReturnError
> is enabled. Using Embperl::Object, if an error occurs in
> something Execute()'d from base.epl, nothing happens -
> Embperl just aborts the Execute and carries on. This is
> Embperl 2.0rc2.
>
> This behaviour has been noted b
I have an ErrorDocument 500 in httpd.conf, and optReturnError is
enabled. Using Embperl::Object, if an error occurs in something
Execute()'d from base.epl, nothing happens - Embperl just aborts the
Execute and carries on. This is Embperl 2.0rc2.
This behaviour has been noted before.
http://www2
> By "hide the error" I mean that if an ErrorDocument 500 is enabled in
> httpd.conf, EMBPERL_OPTIONS is set to return the error in the Apache
request,
> and I call a template in base.epl that causes an error then it seems to
> simply abort that current template and continue on, as opposed to sho
By "hide the error" I mean that if an ErrorDocument 500 is enabled in
httpd.conf, EMBPERL_OPTIONS is set to return the error in the Apache request,
and I call a template in base.epl that causes an error then it seems to
simply abort that current template and continue on, as opposed to showing me
>
> I do a couple Execute calls in my base.epl and essentially they hide the
error
> from the parent process.
>
What do you mean by "hide the error"? If a error happens anywhere, you
should get an error page, don't you?
Errors should propgate to the parent, unles you use the errors => parameter
(
At 10:33 AM -0200 11/24/02, Luiz Fernando B. Ribeiro wrote:
I use a [$ sub error $] in my base.epl that do do all the error handling
and in the end it exits with a normal exit;
In my other pages after any eval {}; or other error I call that sub with
$req->error('tittle', 'page', $error);
It work
Em Sat, 23 Nov 2002 00:08:09 -0500
Jordan Baker <[EMAIL PROTECTED]> escreveu:
> Aha, well I discovered something by testing tonite.
>
> I do a couple Execute calls in my base.epl and essentially they hide
> the error from the parent process.
>
> So I have to find a way to propogate errors.. perh
Have a per-request data store (such as the Apache request record) in
which you place your error messages. So, instead of 'my $errs', you
have something like '$r->errs'. (Please note that I don't actually use
the Apache request record for this; as such, I don't know if that was
the right syntax fo
Aha, well I discovered something by testing tonite.
I do a couple Execute calls in my base.epl and essentially they hide the error
from the parent process.
So I have to find a way to propogate errors.. perhaps there is an option to
Execute to propogate errors when you call another document but
