Ilia,
>
> There's a good thing about Template Toolkit which Embperl seems to be
missing and that is: OUTPUT_PATH. This is similar to EMBPERL_PATH aka 'path'
key for Execute param, but for the case when outputfile is used.
>
> Please add EMBPERL_OUTPUT_PATH. This is where Embperl will produce
outp
>
> Problem:
> Using [* *] delimiters, when I dynamically generate any select, or text
boxes or whatever that Embperl should be replacing with formdata inputted
values, if I first go to the page, it looks normal, but when I refresh the
screen, the print OUT statements appear. Even if you don't pa
>
> If not a call to get the path to an EmbperlObject located object, how
> about a flag on Execute to tell it to process *nothing*? I have a
> problem now that I'm processing files uploaded to the web site, and I
> definitely do *not* want them to have Perl code in them. I'm working
> around it
On Wed, Mar 21, 2001 at 01:24:34AM +0200, Aivo Kalu wrote:
> Should I try to rebuild everything using dynamic linking ? Does anyone has
> experience doing this with AIX ? I found some letter from comp.os.aix that
> there some problems with using AIX native loader with modules such as
> mod_perl a
Hello,
I'm trying to get running Apache, mod_perl and embperl, but no success. This
night I got segmentation faults, and I thought that maybe the mailing list
could help me. I'm sorry for the long message, I hope that there are some
simple errors, you could point me to, therefore the long descri
Dear Gerald, et al;
There's a good thing about Template Toolkit which Embperl seems to be missing and that
is: OUTPUT_PATH. This is similar to EMBPERL_PATH aka 'path' key for Execute param, but
for the case when outputfile is used.
Please add EMBPERL_OUTPUT_PATH. This is where Embperl will pro
> But the below mentioned steps do not work.
> I tried in apache, httpd.conf & embpcgi.pl but It still uses
> /tmp/embperl.log as log file.
>
> tried SetEnv & PerlSetEnv ---
> tried EMPPERL_LOGFILE & EMBPERL_LOGFILE ---
> (Assuming a typo error)
> tried EMPPERL_LOG but to no vail.
>
It's a dou
BTW, I also tried
EMBPERL_OPTIONS 8392208
To disable the scanning of Select,Table,Input.
Bill
On Tue, 20 Mar 2001, goEbusiness.com Mail Lists wrote:
> Solaris 7 Sparc
> Apache 1.3.14, Mod Perl 1.24
> Embperl 1.3.1
>
> Problem:
> Using [* *] delimiters, when I dynamically generate any
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
At 10:05 AM +0100 3/22/00, Gerald Richter wrote:
> >
>> The problem is that I'm processing auto-generated HTML files. I can
>> modify them and escape all the [[ blocks, but it occurred to me that
>> I really didn't want any processing at all, so
Solaris 7 Sparc
Apache 1.3.14, Mod Perl 1.24
Embperl 1.3.1
Problem:
Using [* *] delimiters, when I dynamically generate any select, or text boxes
or whatever that Embperl should be replacing with formdata inputted values, if I first
go to the page, it looks normal, but when I refresh th
>
> Gerald, yes it did help, thanks very much. The install was not without
> pain and suffering (I had to manually find various files like mod_env.so
> and libperl.so, and the 'make test' failed for mod_perl), but it does
> seem to be working finally when I test the server. This is very useful
> t
Gerald Richter wrote:
>
> Neil,
>
> Embperl needs only to have read access the Apache header files and must be
> able to start the Apache binary, to check with whichs options it is
> compiled.
>
> The header files are normaly installed by mod_perl somewhere under the Perl
> directory (do a find
Neil,
Embperl needs only to have read access the Apache header files and must be
able to start the Apache binary, to check with whichs options it is
compiled.
The header files are normaly installed by mod_perl somewhere under the Perl
directory (do a find -name httpd.conf). Take this directory a
Hi Gerald, quick question: I am installing Embperl on the server of a
small company for whom I am doing some consulting. The server is running
FreeBSD, and the setup is a virtual server environment which has many
restrictions on what my user account can see. Currently I am having
problems with the
>
> Well, my goal was to keep the changes to the server config to a
> minimum. And to have different library paths for different sites.
>
Since @INC is global for the whole server, I prefer to keep it at one place,
but that's a matter of taste. At least you avoid the problem as you
described bel
15 matches
Mail list logo
