> > > [Sat Aug 5 16:10:00 2000] [notice] Apache/1.3.9 (Unix) (Red
Hat/Linux)
> > > mod_perl/1.21 configured -- resuming normal operations
>
> But that fixed, I geta segmentfault now. I tried embpexec on the same
> file, came out right.
>
Looks like you are using mod_perl 1.21 from RedHat. This
- Original Message -
From: "Jon Brisbin" <[EMAIL PROTECTED]>
To: "Embeded PERL ML" <[EMAIL PROTECTED]>
Sent: Tuesday, August 08, 2000 5:50 PM
Subject: Re: custom error handling in CGI mode
> > No, something like:
> >
> > my $rc = HTML::Embperl::Execute({inputfile => $ENV{PATH_TRANSLATED
Hi,
> I have an EmbperlObject base document with the obvious stuff like
> HTML headers in it. I want to set several
> variables there, too, but they are obviously not in the same
> scope as the page included with Execute ("*"). Is there a way to pass
> variable values to that page?
>
Use Embperl
> No, something like:
>
> my $rc = HTML::Embperl::Execute({inputfile => $ENV{PATH_TRANSLATED},
> options =>
> HTML::Embperl::optReturnError,
> errors =>
\@errors});
>
Now I've tried this:
will this still send an email of the error, as it does now??
jb
- Original Message -
From: Gerald Richter <[EMAIL PROTECTED]>
To: Jon Brisbin <[EMAIL PROTECTED]>; Embeded PERL ML <[EMAIL PROTECTED]>
Sent: Tuesday, August 08, 2000 8:32 AM
Subject: Re: custom error handling in CGI mode
>
Hi,
I have an EmbperlObject base document with the obvious stuff like
HTML headers in it. I want to set several
variables there, too, but they are obviously not in the same
scope as the page included with Execute ("*"). Is there a way to pass
variable values to that page?
Andre
---
Hello All,
> I am having the problem with saving data to the file. Script looks like
> this:
> [* $myfile="/path/to/my/file";
>open (OUT, ">$myfile) || die "Could not write to $myfile";
>print OUT $fdat{mydata};
>close (OUT);
> *]
> What happens is I have the empty file (0 bytes), and
Hello All,
I am having the problem with saving data to the file. Script looks like
this:
[* $myfile="/path/to/my/file";
open (OUT, ">$myfile) || die "Could not write to $myfile";
print OUT $fdat{mydata};
close (OUT);
*]
What happens is I have the empty file (0 bytes), and the Internal Se
>
>
> So the later option would be something like:
>
> my @errors = HTML::Embperl::Execute($ENV{PATH_TRANSLATED});
> ...handle errors...
>
No, something like:
my $rc = HTML::Embperl::Execute({inputfile => $ENV{PATH_TRANSLATED},
options =>
HTML
> Take a look at embpcgi.pl. If you set optReturnError in EMBPERL_OPTIONS
then
> the return value in $rc will contain zero for succes and an error code for
> all other cases. embpcgi.pl already outputs a small error document and you
> may replace it by your own. Unfortunately you don't have access
> > You can let Embperl return the error value to embpcgi.pl
(optReturnError).
> > Then you can call your custom error page at the end of embpcgi.pl. I
> didn't
> > tried it, but it should work.
>
> by doing an "Execute or die &errorhandler" ??? or how should i trap that
> error??
>
Take a look a
> You can let Embperl return the error value to embpcgi.pl (optReturnError).
> Then you can call your custom error page at the end of embpcgi.pl. I
didn't
> tried it, but it should work.
by doing an "Execute or die &errorhandler" ??? or how should i trap that
error??
Thanks!
Jon Brisbin
---
12 matches
Mail list logo
