Posted by Jerry Stuckle on 10/27/07 14:15

AnrDaemon wrote:
> Greetings, Lars Willich.
> In reply to Your message dated Saturday, October 27, 2007, 13:18:44,
>
> LW> As far as I know I can override the php settings for a certain branch of the whole directory tree
> LW> by putting a additional, new php.ini in this directory.
>
> LW> Is this true ?
>
> AFAIK, it was removed some builds ago to avoid unpredictable results.
>
> LW> If I assign in this new php.ini only a new value to 1 (!) php variable are then all the
> LW> other php parameter values taken from the next php.ini when I go towards the root of
> LW> the directory tree? Or - otherwise - are default built-in values from PHP taken in this case ?
>
> Default, because PHP read only single INI file.
>
> LW> Do I have to do something else to activate this new php.ini (e.g. specify something in the
> LW> .htaccess file) ?
>
> Hm. Please tell me why You bothering with PHP.ini if You using PHP as web
> scripting engine?
> Install PHP as Apache module and use httpd.conf/.htaccess to control it's
> behaviour.
> Use php-apache2handler.ini or php-apache2filter.ini (depends on which SAPI You
> use) to create default environment.
>
>

I always use php.ini to set the basic commands. I'll use the httpd.conf
to modify specific directories for specific commands, but that's all.

It's stupid to load all of your configuration stuff in httpd.conf. And
even worse to put it in .htaccess!

--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex@attglobal.net
==================

[Back to original message]