Description:
------------
Hi Devs
I'm referring to bug #3293.
Yes, allowing multiple auto_prepend_file/auto_append/file does make sense. Picture this:
You have your global configs in a file that's auto prepended. And you want to use a package using auto_prepend_file as well (like my db_auth, see https://www.bitcetera.com/en/project/pear/). You can't include() dbauth to your global config as you don't want to protect all pages. And you don't want to include() your global config in dbauth as this means you have to alter the code of dbauth and trouble arises when new dbauth versions are released.
I suggest allowing the following:
auto_prepend_file /path/to/inc1.php:/path/to/inc2.php
Allowing several auto_prepend_file directires is not a good idea as things would get very messy when using it with .htaccess.
Love PHP! -sven

Patches

Pull Requests

History

AllCommentsChangesGit/SVN commitsRelated reports

[2005-09-11 19:45 UTC] csaba at alum dot mit dot edu

I would also find this quite useful as I have some files that I would like to selectively include depending on which virtual host is being accessed.
However, I would suggest a semicolon separated list of entries as with the ini setting: include_path
Allowing this directive multiple times is not desirable because then it is not overrideable. For example, if your php.ini has a standard set of libraries (.php files) that you use locally, it might make sense to override these in the web server's configuration files (e.g. httpd.conf)
Csaba Gabor from Vienna