Greetings... I've encountered a problem that I've not been able to find a cure for, regardless of several pointers found in the archives. Basically, if I place php.ini into my Windows folder, it's parsed properly, or so I am assuming since the sendmail_from and SMTP values, as well as the path to the ini file, are correctly displayed using phpinfo. The problem is, once the ini file is parsed, PHP basically stops working. A bit of background. I'm running 98SE (I know, bad choice, but unavoidable at present) with php 4.1.1, and using OmniHTTPd as my webserver. Ironic that the docs mention Omni as the easiest of all setups for PHP. PHP was installed by Omni on a prior release, being version 4.04pl1, or some such. I've left it as is, outside of making the needed settings to Omni to show it the exe location, and setting the mime types. No problems. Recently, I had occasion to look into the mail() functions, as a user informed me that he was having problems. That's when I hit the roadblock, head on. I have a single instance of php.ini on my system at any given time; I've even gone so far as to rename those in the pear folders. If I place this file into my Windows folder, phpinfo reveals my desired settings, which are simply the suggested settings, with my SMTP and sendmail_from entries, however, visiting any of the user sites (subdomains, with user folders, etc.) that uses PHP returns pages of error texts, and cease working. Removing the file from the Windows folder restores things to as is. As is consists of an upgrades install in the /php folder underneath the Omni installation. There is no php.ini file in this folder, yet, under Omni, PHP runs without it, on a set of seeming defaults. I've also encountered similar problems with Apache. It parses the file, as long as it's told where to look for the ini file, with no problems. Phpinfo under it returns the desired settings, but, alas, the functions are missing, and again the errors appear. From what I've gathered, there aren't supposed to be any copies of php.ini outside of the one contained in the Windows folder. In my case, placing the file there results in the desired settings being parsed (or indication thereof in showing desired as opposed to "default" when calling phpinfo) If the file is present, it no longer works, outside of seeing my settings. If the file isn't present, with Omni at least, PHP functions seem to work within whatever default settings it come out of the box. Omni is set to look for the executable in it's path, and mime types have been added for php* extensions. For whatever reason, once the ini file is parsed, it stops working. Which makes me think... There is no doubt some glaringly obvious setting in the ini file that I have overlooked, or have set incorrectly, but I'm dipped if I can find it. If this has any bearing, I'd be interested in knowing where to look further into it. My OS resides on the C drive, while the servers and associated go-withs reside on the E drive. Any insights would be most gratefully accepted.
[EMAIL PROTECTED] --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.338 / Virus Database: 189 - Release Date: 3/14/02 -- PHP Windows Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
