Please read the mailing list posting guidelines before posting. We
don't top-post on this list.
> > > I have just installed squirrelmail on a new server running FreeBSD 7.1
> > > Release p1 with Apache 2.2.11, UW-imap and PHP 5.2.25. Installs were all
> > > done via the latest FreeBSD "ports" col
Thanks for the reply Paul. I modified the php.ini to display errors but
nothing showed up. Then, while checking httpd-error log I noticed there
was a squirrelmail error log too (duh). it's telling me:
[Mon Jan 19 19:41:36 2009] [error] [client 192.168.98.57] PHP Fatal
error: Call to undefined
I checked my php extensions.ini and it pointed to a lib (session.so)
that got moved to a different directory. that's back where it should
be. I still get a blank screen but now the error log shows:
[Mon Jan 19 19:55:38 2009] [error] [client 192.168.98.57] PHP Fatal
error: Call to undefined fu
On Mon, Jan 19, 2009 at 11:18 AM, Joe in MPLS wrote:
> I have just installed squirrelmail on a new server running FreeBSD 7.1
> Release p1 with Apache 2.2.11, UW-imap and PHP 5.2.25. Installs were all
> done via the latest FreeBSD "ports" collection.
>
> Squirrelmail is on it's own apache virtual
I have just installed squirrelmail on a new server running FreeBSD 7.1
Release p1 with Apache 2.2.11, UW-imap and PHP 5.2.25. Installs were all
done via the latest FreeBSD "ports" collection.
Squirrelmail is on it's own apache virtual server with
/usr/local/www/squirrelmail as the document root
