> Yeah, I was thinking about that route, but just as I was reading your > response, I thought up a new 'problem' for myself. Even if I set it in > the httpd.conf, a .htaccess, or in a file that I auto_prepend, if the > end user on one of the vhosts uses the ini_set(), it will be > overwritten. I could turn off the ability for users to set a local > include path, but I'd like to give them as much *freedom* as possible. > It's not an issue at the moment, since I'm the only one who does any php > code on the box (I have a 'designer' who helps me out from time to time, > but he doesn't mess with any PHP), but sooner or later, I'm probably > going to pick up a customer who wants to handle his/her own code. I > guess if I'm feeling really brave, I could brush up on my C code, and > modify the source so that ini_set() will append, and not overwrite the > include path. I wouldn't do that. If somebody is silly enough to not use ini_get() and append their own directories, it's on their heads. More importantly, they might NEED to set the path differently to get legacy code, versions, whatever, of the files you are providing. -- Like Music? http://l-i-e.com/artists.htm -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
