Php.ini Problem??

[planejane]

Hiyas..
I've just about torn all my hair out looking for a solution all over the 'Phpweb community' regarding an explanation to editing the php.ini: include_path.
From the forums of phpgeek, phpauction, phpetc etc the list goes on...and still I cannot find the answer.

I run: Win98,Phptriadapache,php,mysql with running scripts like 'Phpauction, Phpnuke, Phorums etc etc...and all werk extremely well except a few errors I have such as:

Warning: Failed opening 'footer.php' for inclusion (include_path='.;c:\apache\includes; c:\apache\htdocs\nuke\includes;') in c:\apache\htdocs\nuke\admin\case\case.filemanager.php on line 29

obviuosly the Nuke application
And I've noticed a few other phpscripts I have I get a similar error

Friends from phpGeek tell me it may be a php.ini error with incorrect include_paths

I have the php.ini file at c:\apache\php and I've noticed through the posts here at phpbuilder that many have extracted this file to windows dir...shall I leave this where it is?
I've tried hundreds upon hundreds of times editing correct paths to include_paths...and I guess I've failed in this area.
Before I go crazy, can somebody please suggest a include path to get this error out of my head?

As said before I have win98/phptriad etc etc

I truly appreciate anything considered

[Anon]

Yes you need to move your php.ini file over to the WINDOWS directory. that is where the ini file should be

[mithril]

Jane,

If calling phpinfo() shows you the values correct values for include_path, the problem doesn't lie in the location of php.ini. The reason php.ini is told to live in c:\windows is that directory is always in the Win32 %PATH% variable, therefore the file can be located. However, any directory in %PATH% is a suitable home. In addition, if you're running PHP as a CGI process the php.exe always looks in it's own path first for a copy of php.ini (not the case with PHP as an Apache module or ISAPI filter).

Regarding your problem, from my own experince with Phorum, phpMyAdmin, etc. this problem is usually caused by a call like:

include("footer.php");

Changing the above to:

include("./footer.php");

often solves it. Thus, you can either manually change all similar calls (tedious!!!), or try adding "./" to your include_path. This sometimes solves the problem. HTH.

Cheers,

Geoff A. Virgo

[planejane]

Oh poo,Oh well..hasnt changed a thing Geoff..I appreciate your help...
Php.ini file is in the right place, everything is installed, scripts such as Phpinfo.php, Phpmyadmin, Phorums, Phpauction, phpnuke run fine..including mail confirmation etc etc...Although I still get warning errors for any of the admin scripts.

One in particular with Phpauction admin.php I get:
Warning: Failed opening '../C:\apache\htdocs\phpauction\includes\passwd.inc.php' for inclusion (include_path='.; .\; ./; c:\apache\includes; c:\apache\htdocs\; c:\apache\php; c:\apache\phpauction\admin; c:\apache\phpauction\includes') in c:\apache\htdocs\phpauction\includes\config.inc.php on line 185

Warning: Cannot add header information - headers already sent by (output started at c:\apache\htdocs\phpauction\includes\config.inc.php:185) in c:\apache\htdocs\phpauction\includes\sessions.inc.php on line 217

Warning: Cannot add header information - headers already sent by (output started at c:\apache\htdocs\phpauction\includes\config.inc.php:185) in c:\apache\htdocs\phpauction\admin\admin.php on line 26

and underneath these errors is the actual 'Site Administration Program" table..with the various admin sections e.g news managment etc etc.
Isnt there suppose to be a Login/Admin page before I enter this section.

What ever the case guys I'm gettin pretty darn Pooey with Php...Oh I wish I had of stuck with my guns and stay with ASP..this is tirelesly useless.

I'm quite certain it 'HAS' to be the php.ini configuration. Would Uploading a copy of the info I get with phpinfo.php for any of you to double check, help in any way?

Jane : [e-mail]

[Anon]

I'm late but google linked this thread 🙂
Well on my linux box this would be a problem with filepermissions. Make sure your webserver is allowed to read your scripts.