[freeside-users] failed to resolve handler HTML::Mason

[Cory Robson]

I have started to restart the install process from scratch and hope I have
all dependencies sorted. As mentioned previously I'm using a fresh install
of Fedora Core 6. (apache2 / Mod_Perl2)

If anybody has a better install document suited to fedora 6 with step by
step or rpm list of dependencies please let me know.

-----Original Message-----
From: freeside-users-bounces at sisd.com
[mailto:freeside-users-bounces at sisd.com] On Behalf Of Richard Siddall
Sent: Friday, 2 February 2007 2:10 PM
To: Freeside users mailing list
Subject: Re: [freeside-users] failed to resolve handler HTML::Mason

Cory Robson wrote:
> Ok I have asked before but nobody responded.
> 
> Apache2, mod_Perl2 Fedora 6 install
> I need to confirm the settings in apache for freeside to function.
> Currently I'm getting "failed to resolve handler HTML::Mason" in my logs
and
> no pages being served up.
> 
> My apache is running as user freeside and my config is as follows:
> 
> PerlModule HTML::Mason
> <Directory /var/www/html/freeside>
> AuthName Freeside
> AuthType Basic
> AuthUserFile /usr/local/etc/freeside/htpasswd
> require valid-user
> Options +Includes +ExecCGI
> AddHandler Perl-script .cgi .html
> PerlResponseHandler HTML::Mason
> require "/usr/local/etc/freeside/handler.pl"
> </Directory>
> 
> 
> Can anyone please tell me what I have missed ?

I just looked at my Apache config file from 
http://www.sisd.com/pipermail/freeside-devel/2005-September/000521.html 
and noted that the PerlResponseHandler directive is inside a <Files  ~ 
(\.cgi|\.html)> block.  I seem to remember that mod_perl2 is more picky 
about where you put directives.

BTW, I assume you're using straight double quotes throughout; you've got 
typographic quotes above.

Regards,

	Richard.
_______________________________________________
freeside-users mailing list
freeside-users at sisd.com
http://420.am/cgi-bin/mailman/listinfo/freeside-users

__________ NOD32 2029 (20070202) Information __________

This message was checked by NOD32 antivirus system.
http://www.eset.com