php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #24114 include_path option
Submitted: 2003-06-10 09:09 UTC Modified: 2003-06-10 11:38 UTC
Votes:1
Avg. Score:5.0 ± 0.0
Reproduced:1 of 1 (100.0%)
Same Version:1 (100.0%)
Same OS:1 (100.0%)
From: stefano dot cecconi at staff dot aruba dot it Assigned:
Status: Not a bug Package: PHP options/info functions
PHP Version: 4.3.2 OS: windows 2000
Private report: No CVE-ID: None
View Add Comment Developer Edit
Welcome! If you don't have a Git account, you can't do anything here.
You can add a comment by following this link or if you reported this bug, you can edit this bug over here.
(description)
Block user comment
Status: Assign to:
Package:
Bug Type:
Summary:
From: stefano dot cecconi at staff dot aruba dot it
New email:
PHP Version: OS:

 

 [2003-06-10 09:09 UTC] stefano dot cecconi at staff dot aruba dot it
This is my include_path option value :

include_path = ".;c:\php\includes"

Before 4.3.2 everything worked using this path in a script : 

include "/call_php/counter.php"

With 4.3.2 is mandatory to remove the first / so it works only with this path :

include "call_php/counter.php"

or 

include "./call_php/counter.php"

I can't understand this change and it's creating a lot of problems for our web hosting service, simply because there are thousands of scripts based on the old way to use relative paths.




Patches

Add a Patch

Pull Requests

Add a Pull Request

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2003-06-10 09:44 UTC] derick@php.net
Your version should never have worked... it's not a bug at all that you need to strip that / (it will make PHP to open c:/call_php/counter.php)...
 [2003-06-10 10:35 UTC] stefano dot cecconi at staff dot aruba dot it
Php 4.2.3 works in a different way.

Even with the / it works. 

A lot of free php scripts are written with this notation.

Now they don't work anymore.

Try to think to 200.000 domain in hosting (we are the web hosting company) where all people working with php and includes have to change their scripts.

It's not so easy, right?
 [2003-06-10 11:38 UTC] sniper@php.net
This was already 'broken' (actually it was another bug that was fixed) in PHP 4.3.0. Current behaviour is the correct and documented one.

There is no reason to break it again.


 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved.
Last updated: Sat Apr 27 08:01:29 2024 UTC