On 29 Jun at 21:47 Jonathan Vanasco <[EMAIL PROTECTED]> wrote in message
<[EMAIL PROTECTED]>
>
> On Jun 29, 2007, at 4:09 PM, Tony van der Hoff wrote:
> > Well, thank you for that advice.
> >
> > Um, Why?
> >
> > How does that help solve my problems?
>
>
> Apache::Reload checks perl modules and
Hello everyone,
I'm wondering whether the following is intended behavior. Calling die
inside the mod_perl handler doesn't clear the part of the response
generated to that point. In other words, the HTML error document is
simply appended to anything that has been sent to $r->print()
previously and
On Jun 29, 2007, at 4:09 PM, Tony van der Hoff wrote:
Well, thank you for that advice.
Um, Why?
How does that help solve my problems?
Apache::Reload checks perl modules and *reloads* them on every hit if
they've changed. It's essentially saying "hi, i'm running under a
persistant envir
On 29 Jun at 20:08 Jonathan Vanasco <[EMAIL PROTECTED]> wrote in message
<[EMAIL PROTECTED]>
>
> On Jun 29, 2007, at 1:24 PM, Tony van der Hoff wrote:
> > So, sorry to have rambled on a bit, but does anyone have any suggestions
> > as to how I can properly fix these problems, or tell me what I'm
On Jun 29, 2007, at 1:24 PM, Tony van der Hoff wrote:
So, sorry to have rambled on a bit, but does anyone have any
suggestions as
to how I can properly fix these problems, or tell me what I'm doing
wrong.
Any advice will be very welcome.
I don't have time to analyze your config, but
you s
I'm a bit of a newbie with respect to mod_perl, but with some perseverence,
I seem to have googled and hacked my way 'round most of it.
A couple of problems continue to dog me, though:
Because of constraints by my service provider, I'm running apache/1.3.37
with mod_perl/1.30 under linux on both
Hello,
Just to confrm that I have the same symptom as yours when I was developing
on Win32: when a module couldn't load, the only thing I could get was a bare
"Can't load module", without any explanation.
Then, th eonly thing I could do was trying to isolate the problem,
progressively strippin
John ORourke schrieb:
Jens Helweg wrote:
I thought perl -c mymodule.pm is no option when developing modperl
handler modules because these will only run/build in the apache
modperl environment and not on command line ?
Not sure about your windows environment but a command-line perl -c works
jus
Michael Peters schrieb:
Jens Helweg wrote:
How do the modperl pros find an error in modperl modules when all apache
tells is that it can't load the module instead of priting the complete
error that the perl compiler/parser has with the code.
I'm not sure why the error message is getting burie
William A. Rowe, Jr. schrieb:
Alvar Freude wrote:
Hi,
-- Jens Helweg <[EMAIL PROTECTED]> wrote:
Is there a way to get the compilers output from perl, so I can get
details on what is wrong in the code ?
usually you get the errors in the apache's error log. I don't know where
it is stored on W
10 matches
Mail list logo
