Re: factory broken

"Tomas V.V.Cox" wrote: > > "Stig S. Bakken" wrote: > > > > "Tomas V.V.Cox" wrote: > > > > > > mailling@bigfoot.com wrote: > > > > > > > > I already sent this message to this list, but I got no answers/comments, so > > > > I decided to send it again. > > > > Either I am wrong, or every factories are broken. So comments would be > > > > appreciated. > > > > > > > > > > Pear DB isn't affected by this, others should be revised. > > > > > > > It migth be good also to add a constant such as PEAR_DIRECTORY to include > > > > the file, because some ISP may not let you change the php.ini or work wirh > > > > .htaccess > > > > > > Yeah, this is more problematic. For those who doesn't have access to > > > php.ini, ini_set() or .htaccess, there is a big problem, not only with > > > Pear I mean also with other php packages. Perhaps a user-land > > > set_include_path() php function could help a lot. Other ideas about how > > > to fix this problem? > > > > ini_set("include_path", ...) in your script seems to work even for > > require. > > > > ini_set() is other function that normally is disabled by ISP admins. So for "ISP victims", using the full path is the only solution? That would be relatively easy to fix were it not for a (IMO) bug in how include_path treats ".". "." is always relative to the original script, not the file doing the include. If it had been the latter, we could have used relative paths when including files within PEAR. Then it would be enough for the "ini_set challenged" to use the full path in their scripts. - Stig