Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

PHP question



On Fri, 30 Mar 2007 13:34:43 -0400
Mark Richards <mark.richards at massmicro.com> wrote:

> Jerry Feldman wrote:
> > On Fri, 30 Mar 2007 11:58:54 -0400
> > "John Abreau" <abreauj at gmail.com> wrote:
> > 
> >> The old behavior is dangerous, and would leave the website
> >> vulnerable to compromise in the presence of sloppy PHP code.
> >> So enabling the old behavior is not an option.
> > I agree. At the time I wrote the script I used what had been acceptable
> > behavior. What I need to do is to find the specific cases that cause
> > the script to fail and correct it in the PHP 5 context. It's more of a
> > case that I don't do much PHP coding. 
> > 
> Log files can also help a lot.
> 
> error_reporting(E_ALL);
> ini_set('display_errors', 1);
> ini_set('display_startup_errors ',1);
> 
> at the very top of the script.
Thanks,
This was the type of advice I was looking for. 

-- 
Jerry Feldman <gaf at blu.org>
Boston Linux and Unix user group
http://www.blu.org PGP key id:C5061EA9
PGP Key fingerprint:053C 73EC 3AC1 5C44 3E14 9245 FB00 3ED5 C506 1EA9



BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org