> - Right now this also effects things like opening php.ini. It'll now
always
> check in the current working directory for php.ini. I think this
doesn't
> screw up todays behavior.
Isn't this a huge security risk? When there is something wrong so that
php.ini can't get read where it should, it will maybe read the user's
one?
I assume it will at least first check for php.ini where it should be?
By the way, when doing something like include("../init.php"), your
script will get broken when a init.php is added somewhere...
it doesn't make it very transparently.
Jeroen
--
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
