OK, the "registry per directory" allows *some* of the php.ini entries to be registered but does not work for all of them. Some that did not work for me are (not an exhaustive list):
safe_mode, user_dir, doc_root, open_basedir, expose_php, file_uploads, smtp what did work were: sendmail_from, error_log I presume all the choices are simply not being parsed when they are place in the registry location. A look through the php-win and php-dev archives doesn't show any further information about this issue. As soon as I made a change to the registry on the server it was immediately reflect in a refreshed phpinfo() but this system still requires that there is a single php.ini file with the "master" values for these settings. Does anyone know how to pass the "-c path/to/ini" parameter inside a script mapping for IIS5 ? This would solve the problem completely because all my php installs could be different versions/different options enabled and secure from other virtual servers both from the php point of view and the ntfs point of view in w2k. Regards Petar ----- Original Message ----- From: "Petar Nikolich" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Sunday, December 22, 2002 11:29 PM Subject: [PHP-WIN] iis5 php 4.2.3 multiple -c php.ini possible? > Hello Everyone! > > Ok, this config this is driving me crazy. Php works just fine until I try to > specify the path to the php.ini file in the IIS5 script mapping. > > It would be good to have each virtual server running its own php.ini, temp > area and php binaries (different versions) and all I need to work out is how > to make the '-c path/to/inifile' actually have an effect within IIS. > > I am aware of the -c command line option to specify an alternate location for > the php.ini file or alternatively the path+filename but have been unable to > make this work in IIS5. > > Has anyone managed to pass extra parameters in the executable line for the .php > mapping in IIS5? > > This is the normal line which uses the php.ini in c:\winnt\php.ini > > executable: -> c:\site1\php\php.exe > extension: -> .php > > Adding the extra parameter to the executable line *should* be all that is needed > to make individual .ini files workable like the following... > > exexcutable: -> c:\site1\php\php.exe -c c:\site1\php\php-site1.ini > extension: -> .php > > But no matter how I pass the line (quotes/no quotes) the additional parameter > is ignored and the c\winnt\php.ini is used. > > Actaully typing the line at a dos prompt does use the new .ini file so it > seems IIS is doing suomething to remove/ingore the extra paramter when it is > entered in IIS script mapping. > > c:\site1\php>php -c c:\site1\php\php-site1.ini -i > ...shows correct path to specified .ini file > > > Has anyone made this work? I would really like to know the 'magic trick' :-( > > ..Petar > > > > -- > PHP Windows Mailing List (http://www.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php > > -- PHP Windows Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
