one says me that
---------
for me, my php.ini has to be in winnt\ directory, not winnt\system32.

can you successfully run a "<?php phpinfo() ?>" file?  in the results, it
will tell you were it is expecting your php.ini file.
---------

I actually copy php.ini to winnt, winnt/system and winnt/system32 always.
it seems winnt in phpinfo

but problem still exists.

but the interesting thing is that the inclue_path problem exists in only one
work in my server. I mean there are several web appz. at my server but only
of them gives the error. although most of them uses the include(""); none of
them generates error besides one.

--

martina.
"Martinahingis" <[EMAIL PROTECTED]> wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> I tried to change my php.ini
> with
> include_path="."
>
> copy php.ini to winnt\system32 and restart apache
>
> but no change i still gett the error message that include path is
php4/pear
> and the included file doesn't exits
>
> can anyone help?
>
>
> --
>
> martina.
> "Ryan Grove" <[EMAIL PROTECTED]> wrote in message
> Pine.WNT.4.44.0204011318230.1668-100000@nooch">news:Pine.WNT.4.44.0204011318230.1668-100000@nooch...
> > On Mon, 1 Apr 2002, Aleem wrote:
> >
> > > I am getting the wierdest PHP error. I couldn't find anything on the
web
> > > regarding this error. The exact error is as follows:
> > >
> > > [01-Apr-2002 02:45:41] PHP Warning:  Failed opening
> > > '/apache/htdocs/php.php' for inclusion (include_path='c:\php4\pear')
in
> > > Unknown on line 0
> > *snip*
> >
> > I had the same problem when I upgraded to 4.1.2. You just need to change
> > the setting of "include_path" to search the current directory first. So,
> > for example:
> >
> > include_path="."
> >
> > Or, if you need to use the PEAR repository:
> >
> > include_path=".;c:\php\pear"
> >
> > (replace c:\php with your PHP path)
> >
> > --
> > Ryan Grove
> > [EMAIL PROTECTED]
> > http://wonko.com/
> >
>
>



-- 
PHP Windows Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Reply via email to