On Sun 10 Feb 2008, James Breat wrote:
to resolve handler `ModPerl::Registry': Can't locate
ModPerl/Registry.pm in @INC (@INC contains:
/usr/lib/perl5/5.8.8/i486-linux-thread-multi /usr/lib/perl5/5.8.8
/usr/lib/perl5/site_perl/5.8.8/i486-linux-thread-multi
/usr/lib/perl5/site_perl/5.8.8
Hi guys,
thank you very much for all the interest in the issue, but
could one of you summarise and tell me what I should do ? Should I
- go back to ActivePerl 8.8.820 (instead of 8.8.22 currently) ?
- do something else (like what Jan Dubois said below ? (or is that just
for the people creating
I uploaded a .02 release last night which i think will make something
like this even easier to accomplish. This version adds a function
called uri_to_function, which takes a RequestRec (or derived) object,
and an array of uri_bits and returns a function name that should be
used to to
I am taking the Apache2::Request method, and will integrate the DB solution
as Chandra mentioned.
#!/usr/bin/perl -w
use strict;
use CGI;
use Apache2::Request;
use Data::Dumper;
print Content-type: text/html\n\n;
my Apache2::Request $r = shift;
my $docroot =
On Feb 10, 2008 12:14 PM, Mag Gam [EMAIL PROTECTED] wrote:
my Apache2::Request $r = shift;
Tells the Perl compiler to expect an object in the CApache2::Request
class to be assigned to C$r. A patch has already been submitted to
use this information so method calls can be resolved at compile
On Feb 10, 2008 12:24 PM, Mag Gam [EMAIL PROTECTED] wrote:
my $docroot = $r-document_root('/var/www/html/perl');
Why are you trying to change the DocumentRoot?
- Perrin
Thanks for the quick response Perrin.
I am trying to change DocumentRoot because, currently I am using open() to
load templates for my website. I have header, menu, footer in 3 seperate
files, and I generate content like that. It works fine now, just not too
dynamic when I want to move the stuff
I've spent at least a couple of hours trying to figure this out and
reading manuals, to no avail, hence asking here. I hope it's not too
obvious :-).
I'm running a mod_perl (2.0.2) script from the root of my domain. My
Apache (2.2.3) configuration is as follows.
VirtualHost *
. . .
There are a couple of ways you can tackle this sort of thing.
1) You can modify TestSite to return DECLINED for any request that you
want to be handled by the filesystem rather than your handler. ie
if $r-uri =~ m|\css$| {
return Apache2::Const::DECLINED;
}
2) If you've got all your CSS
On Sun, 10 Feb 2008, Foo JH wrote:
William A. Rowe, Jr. wrote:
Foo JH wrote:
Andre,
I've recently set up a test based very closely on your platform:
AP2.2.8
AP5.8.8 Build 822
MP2.0.3
You mention a VC 2005 build of httpd, which build of MP? 2005?
Not sure which uwinnipeg is built against,
I do keep my templates in other directories also.
1. If your directories are relative to the document root, and you can
take advantage of this fact by rendering a variable to remember the
template path.
2. If your template directories have nothing in common with the document
root, then you
Randy,
I think characterizing the ASF binaries as unreliable with
mod_perl is misleading - there were some recent problems
with restarts, etc. on Win32 that have been looked into
and addressed for the 2.2.8 release.
The intent of my earlier response was not to undermine the quality of
the ASF
12 matches
Mail list logo
