[freeside] Installation doc "www.sisd.com/freeside/docs/"veryvague to many at this point.

[Kent Andersen]

Been there done that..
Never got any version of mysql to work EVER with freeside. This is the
primary reason that people cant get freeside to work correctly.  They
attempt to use MySQL as their flavor of database. There is something to be
said in the documentation where it recommends postgresql. It is my opinion
that MySql should be removed from the docs entirely.
----- Original Message ----- 
From: "The Salisburys" <rojee at bigpond.net.au>
To: <ivan-freeside at sisd.com>
Sent: Wednesday, June 09, 2004 9:28 AM
Subject: Re: [freeside] Installation doc
"www.sisd.com/freeside/docs/"veryvague to many at this point.


> > what version of apache and mod_perl? I had this issue with apache 2.0.x
> > and mod_perl 2. Ultimately I succeeded using apache 1.3.x.
>
> Apache 2.0.40
> mod_perl-1.99_07-5
>
> I am running mysql which is to old.
> In the proccess of upgrading to 4.1.2
> & hoping ....
>
>
> ----- Original Message ----- 
> From: "Sven Willenberger" <sven at dmv.com>
> To: <ivan-freeside at sisd.com>
> Sent: Thursday, June 10, 2004 1:04 AM
> Subject: Re: [freeside] Installation doc
> "www.sisd.com/freeside/docs/"veryvague to many at this point.
>
>
> > On Thu, 2004-06-10 at 00:07 +1000, The Salisburys wrote:
> > > Thanks Sven
> > >
> > > > "Configure Apache" == "Edit the httpd.conf file". Cut 'n' paste the
> > > > noted code into httpd.conf and apachectl restart (or however you
> restart
> > > > your apache server)
> > > >
> > > Done but command
> > >
> > > "httpd -t"
> > >
> > >  responds with
> > >
> > > "Syntax OK"
> > >
> > > ONLY if I comment out these 3 lines:
> > >
> > > #<Perl>
> > > #$MLDBM::RemoveTaint = 1;
> > > # </Perl>
> > >
> > > ELSE it responds with :
> > >
> > > "Syntax error on line 1047 0f /etc/httpd/conf/httpd.conf
> > > <Perl not allowed here"
> > >
> > > So something still needs attention.
> > >
> > > Any ideas anyone?
> > >
> > > thanks
> > > Roger
> > >
> > >
> > what version of apache and mod_perl? I had this issue with apache 2.0.x
> > and mod_perl 2. Ultimately I succeeded using apache 1.3.x.
> >
>
>