|
|
Posted by Rick Emery on 10/23/05 18:43
Jasper Bryant-Greene wrote:
>On Fri, 2005-10-21 at 15:43 -0500, Jay Blanchard wrote:
>
>
>>[snip]
>>I haven't used Windows for a while, but Start->Search->Files & folders
>>(or something like that) and enter php.ini. Delete all results except
>>the one that you've been editing, and then move the one you've been
>>editing around the following folder until you find the one in which it
>>works:
>>
>>c:\php
>>c:\windows
>>c:\windows\system32
>>c:\
>>
>>Horrible, isn't it?
>>[/snip]
>>
>>Horrible indeed. I got no joy from this. It didn't work.
>>
>>
>
>When you say didn't work... do you mean you didn't find any other
>php.ini files?
>
>There's one other thing I can think of. It's possible to set things like
>the location of the php.ini file and also php configuration directives
>through Apache's configuration.
>
>Now I know you're using IIS, but is there a similar thing available
>through IIS's configuration? (I wouldn't know, I don't practise the dark
>arts...)
>
>
>
You can tell Windows where to find the php.ini file by setting the PHPRC
evironment variable. But, if you've already placed *your* php.ini file
in the location indicated by phpinfo(), then I'm not sure why it
wouldn't be read, unless:
1. From the manual: "*Note: * If you're using NTFS on Windows NT, 2000,
XP or 2003, make sure that the user running the web server has read
permissions to your php.ini (e.g. make it readable by Everyone)."
2. IIS hadn't been restarted (to re-read the new php.ini).
Other than that, not sure. Sorry.
Rick
Navigation:
[Reply to this message]
|