You are probably right, considering you wrote XML::LibXML. I was
basing my info off an old O'Reilly article written in 2001. I finally
gave up and modified the program I was working on to use XML::LibXML,
making the CPAN module, Blog::Simple now compatible with mod_perl 2.0.
You can see a sa
On Wed, Jun 16, 2004 at 05:19:57PM -0700, Steven Scotten wrote:
> Hello, and thanks in advance for your patience as I ask how to do
> something rudimentary, but I seem to be rather dense and a week up to
> my eyeballs in documentation has left me no closer than when I began.
No apology necessary
Hi all,
I ran in to a problem using NameWithVirtualHost because I used
Rewrite rules based on the host name inside a single virtual host and
so ended up with, in my case:
http://www.interarchy.com/main/index.pl
and
http://www.stairways.com/main/index.pl
going to different files in the file syste
Steve,
If you were not using mod_perl 1.x in your old cgi programs, you probably don't need
to be using any of the request stuff. ModPerl::Registry does all the voodoo for you
for ordinary cgi programs.
The stuff below is full of extra stuff and may not be 100 percent, but it works. This
is w
Hello, and thanks in advance for your patience as I ask how to do
something rudimentary, but I seem to be rather dense and a week up to
my eyeballs in documentation has left me no closer than when I began.
My problem is that I'm trying to pick up mod_perl2 without ever having
used mod_perl befo
Willy,
mod_perl 2 uses a different default directory from mod_perl 1.3.
May also be different from plain cgi also.
mp1
used E:\Apache2\bin
mp2
uses E:\Apache2
This
gave me fits when I migrated from 1.3 to 2.
I
think the error I was getting was file not found.
This
works for writ
Hi
All,
Recently I are
migrating cgi to mod_perl but it is running out of the problem for
IO::File.
Here are my original
codes:
my
$template_file = new
IO::File("templates/quickquote.templ"); $template_file->input_record_separator(undef); my
$template =
<$template_file>; $template_f
Hi all,
I
upgraded Perl from 5.8.0 to 5.8.4 and read on the
list that mod_perl had to be re-built. So I gave the foll commands in the source dir of mod_perl
Perl Makefile.PL USE_APXS=1 WITH_APXS=/usr/local/apache/bin/apxs EVERYTHING=1
Also tried adding tag NO_HTTPD=1
No errors
On 16 Jun 2004, at 12:42, Jesse Stay wrote:
Partially because XML::XSLT is more widely used
Actually I don't think that's true (based on traffic on the perl-xml
list).
Matt.
--
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquett
http://httpd.apache.org/apreq/
Install using one of the following methods:
(easiest way)
perl Makefile.PL --with-apache2-apxs=/path/to/apache2/bin/apxs
(or, same thing, different method)
./configure --with-apache2-apxs=/path/to/apache2/bin/apxs
--enable-perl-glue --with-perl=/path/to/perl/binar
On Tue, 15 Jun 2004 23:01:40 -0500 (CDT)
Dave Rolsky <[EMAIL PROTECTED]> wrote:
> On Tue, 15 Jun 2004, Frank Wiles wrote:
>
> > mod_perl Advocacy and PR
> > Thursday 8-9pm Columbia Room
>
> Doh, same time as the Mason BOF. I hope this doesn't conflict for too
> many folks. Oh well, too man
Title: Exit problem using mod_perl 1.99 apache 2.049
This error typically happens when you don't return headers
(beyond 200 OK)... such as content-type and content-legth. Check your
scripts and make sure you're explicily returning headers before you print the
page.
From: Cadman, Andrew (
In message <[EMAIL PROTECTED]>, Stas Bekman writes:
>The core dump shows that neither mod_perl nor Perl are involved. I suppose
My 2c guess is that mod_perl is not properly copying the username into
the relevant Apache data structure or Apache expects the username to
be stored with undocumented m
Me too.
ken.
On 16 Jun 2004 at 14:34, Elizabeth Mattijsen wrote:
>
> I have XML::LibXSLT with mp2 in production for a client. No mp2
> related problems whatsoever.
>
> Liz
>
> --
> Report problems: http://perl.apache.org/bugs/
> Mail list info: http://perl.apache.org/maillist/modperl.html
>
On Wed, Jun 16, 2004 at 02:03:25PM +0200, Cadman, Andrew (Contractor) wrote:
> Generally, as the scripts were well written few errors were reported and
> these have been dealt with. None of the logs files: - the virtual host log,
> apache general error log or /tmp.db.out (using the Apache::DB in st
Andrew, please read the following guidelines for bug reporting and try again.
Thanks.
http://perl.apache.org/bugs/
(1.99_xx == 2.0)
--
__
Stas BekmanJAm_pH --> Just Another mod_perl Hacker
http://stason.org/ mod_p
At 14:22 +0200 6/16/04, Tom Schindl wrote:
Frankly I haven't tried XML::LibXSLT on Apache2 but I don't see any
reason why it should not work beside maybe threading issues. For a
instruction on getting started with libxml/libxslt on RH9 take a
look at
http://axkit.org/wiki/view/AxKit/AxKitRedHat9
Hi,
Frankly I haven't tried XML::LibXSLT on Apache2 but I don't see any
reason why it should not work beside maybe threading issues. For a
instruction on getting started with libxml/libxslt on RH9 take a look at
http://axkit.org/wiki/view/AxKit/AxKitRedHat9# and
http://axkit.org/wiki/view/AxKit/
Title: Exit problem using mod_perl 1.99 apache 2.049
Hi
I am a mod_perl newbie so apologies if I am missing something obvious here.
I am converted some perl scripts and packages into mod-perl using apache 2.049 and mod_perl 1.99 running on Linux RedHat 9.
Generally, as the scripts were we
Partially because XML::XSLT is more widely used and partially because
XML::LibXSLT seems to have problems with RH 9.0 on the system I'm
running it on. Can you verify that XML::LibXSLT will work in a mod_perl
2.0 environment? If it has been verified I will probably push a little
more towards getti
Hi,
I admit I've never used XML::XSLT but why are you not using XML::LibXSLT?
Tom
Jesse Stay wrote:
I admit I have not tried this in mod_perl 1.x but I am really trying to
move towards developing and helping out the mod_perl 2.0 movement.
Hopefully someone has some pointers. Here's my problem:
Hi,
I was just reminded of this happening and thought it might be useful to people here
since lots of people like me use Storable for persistence with mod_perl.
FreeBSD 4.10 changed the way Perl is compiled in the ports collection. They added the
use64bitint flag which was not there before. Th
Hi,
Very glad I could be of some help, even though most of this was copy and paste and
googling. I was in fact testing this on a FreeBSD server with 5.8.0, the production
server is 5.8.4.
Eric
At 03:39 PM 6/15/2004, Jim Albert wrote:
>Great! It's always nice to have multiple solutions to a p
Jim,
Thank you! This was a big help to me in that I ran into this problem from two
directions recently, with a perl daemon and with Apache::SIG.. I did find some info
about fixing this for real rather than using unsafe signals. They mostly seemed to
point to using the POSIX sigaction methods ra
24 matches
Mail list logo
