From: Brian G. P. <br...@br...> - 2006-07-25 13:24:33
|
On Tuesday 25 July 2006 07:42, Phil Driscoll wrote: > On Tuesday 25 July 2006 12:50, Brian G. Peterson wrote: > > On Tuesday 25 July 2006 06:33, Phil Driscoll wrote: > > > On Tuesday 25 July 2006 12:29, Brian G. Peterson wrote: > > > > On Tuesday 25 July 2006 04:54, Phil Driscoll wrote: > > > > > Can someone please have a look to see what's broken, or > > > > > alternatively, give me some guidance as to what further tests I > > > > > can perform to pin down the problem. > > > > > > > > set > > > > error_reporting=E_ALL > > > > in php.ini, and restart apache. > > > > > > It is already set to E_ALL - but no errors are output anywhere I > > > can find. > > > > Well, errors should either be displaying on the screen or in your > > apache error log. Check the php and apache settings to figure out > > where the errors should be logging to, and look there. > > If I add a line at the start of login.php > die($poo); > I get a warning message about $poo not being defined, so I am sure that > my E_ALL setting is ok. Then refer to my earlier post: Install a PHP debugger and step through the code. It is PHP's responsibility to tell you why it is stopping execution of a script. If PHP isn't reporting a fatal error, then the fault lies with PHP, or your PHP configuration. Stepping through the code may help you figure out specifically where the problem lies. PHP 5.2.0 has been widely reported to have problems with backwards compatibility. No one in their right mind who's been around PHP for a while would run a 5.2.0 release on a production machine for an enterprise application like Squirrelmail. *I* wouldn't even bother on a testing machine until PHP 5.2.1 was released, and one could assume that most of the worst bugs had been worked out. But that's just me, so I'm willing to play along in *your* troubleshooting. Regards, - Brian |