ID: 29085
Comment by: php dot netsm at majorsite dot com
Reported By: christian at wenz dot org
Status: Assigned
Bug Type: Feature/Change Request
Operating System: Windows
PHP Version: 5.0.0RC3
Assigned To: pajoye
New Comment:
So, what does this mean to those of us NOT yet on W2K3?
php.net says support for W2K Server, but 5.3 requires newer software.
I'm STILL unable to get the .ini working and I have a lot of pages
simply not loading (now I'm very glad I didn't do a full xfer to .php
pages this last few months as I wanted - I would be totally out of
business!)
I have some php pages working - the 'simple' ones that are
self-contained, but all those that use mysql are DEAD as php says Fatal
error: Call to undefined function mysql_connect() in [FILENAMEREMOVED]
on line XXX
I was able to get my MDaemon WorldClient working by doing a re-route
and using its built-in server, but mysql is out.
Just not sure where to go/what to try anymore..... if .ini would
simply read, I'm sure all would be fine, but WHAT TO DO????
thanks for any help!
Previous Comments:
------------------------------------------------------------------------
[2009-09-09 06:18:28] christian at wenz dot org
great to see that this bug/change request gets some lovin' after over
five years ;-) This should do the trick in win32/build/config.w32:
---SNIP---
107c107
< PHP_PREFIX = "C:\\php" + PHP_VERSION;
---
> PHP_PREFIX = "C:\\php";
---SNIP---
Not sure if this should go into 5.x -- of course I'd love to see it,
but we would probably change the current behavior, and some people might
actually have installed PHP into C:\php5 and expect the include_path to
contain that automatically.
------------------------------------------------------------------------
[2009-09-08 23:50:05] paj...@php.net
Agreed. Let change it in trunk at least, or maybe in 5.3.2 as well.
------------------------------------------------------------------------
[2009-09-07 23:43:37] php dot netsm at majorsite dot com
I, too, find this VERY confusing, and I can't seem to get around it.
Running Win2K Server (was to upgrade this year - market stopped
that...) and have had PHP running on 5.0.3 for awhile (in C:\Program
Files\PHP - the 'default' from the install).
Went to upgrade and found latest versions need Win2003 Server or
better, so I had to take 5.2.10, but I cannot get the .ini to read.
Install.txt file says to avoid \program files\ so I deleted that and
went for a 'clean' install to \php\
phpinfo() says I'm looking at loaded .ini from C:\PHP\php.ini I've
tried setting the php.ini include_path = ".;c:\php;c:\php\ext", yet
phpinfo() says include_path is .;C:\php5\pear
The comments on this page were from 2004 - and the 'fix' was that
"people want to run php4 and php5, though, how long has php4 been gone,
and this issue is still relevant 5 years on..... this IS (IMHO) a BAD
thing and very confusing.
I look forward to some reply as I now have php running again, but none
of my databases run, none of my 'include' files work, etc.
And, please do not tell me to save my .ini file in some other location
- I've tried \winnt\system32, \winnt, c:\ and certainly c:\php - nothing
has worked. I am almost frustrated enough to try c:\php5 and even
c:\php5\pear, but I am trying to use the install instructions!
I think this php5 error is a bug and should be fixed - even in other
versions of php (for those of us that can't afford the upgrade).
------------------------------------------------------------------------
[2005-02-15 01:08:11] tony2...@php.net
This is not a bug, but change request.
Reclassifying.
------------------------------------------------------------------------
[2005-01-05 21:34:30] justin at telepop dot net
This setting just caused me some problems. Somehow my php.ini had a
bad path in its include_path setting. Rather than spit out an error, it
assumed that c:\php4\pear was my default include directory, and gave me
little information to figure out why. Once I fixed the path, my
declared settings took effect and everything worked fine, but it wasn't
a very intuitive leap to see why that include path was showing up.
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://bugs.php.net/29085
--
Edit this bug report at http://bugs.php.net/?id=29085&edit=1
