how to access PEAR In my hosting environment

[NotGiven]

My hosting company has pre-intalled PEAR in a directory out of the web
directory (and not in php-includes).

I've tried including the absolute /to/path/ in the requre statement but it
does not work.

How would I access the PEAR packages?

Many thanks.

[Janwillem Borleffs]

NotGiven wrote:

My hosting company has pre-intalled PEAR in a directory out of the web
directory (and not in php-includes).

I've tried including the absolute /to/path/ in the requre statement
but it does not work.

How would I access the PEAR packages?

Check the open_basedir directive in the php.ini file. Chances are that it
doesn't include the path to the PEAR installation.

When this is the case and you are unable to edit the php.ini file yourself,
all you can do is asking your hosting provider to include this path.
JW

[Tim Van Wassenhove]

In article <41***********************@news.euronet.nl>, Janwillem Borleffs wrote:

NotGiven wrote:

My hosting company has pre-intalled PEAR in a directory out of the web
directory (and not in php-includes).

I've tried including the absolute /to/path/ in the requre statement
but it does not work.

How would I access the PEAR packages?

Check the open_basedir directive in the php.ini file. Chances are that it
doesn't include the path to the PEAR installation.

When this is the case and you are unable to edit the php.ini file yourself,
all you can do is asking your hosting provider to include this path.

or use http://www.php.net/ini_set

--
Tim Van Wassenhove <http://home.mysth.be/~timvw>

[Michael Vilain]

In article <2p************@uni-berlin.de>,
Tim Van Wassenhove <eu**@pi.be> wrote:

In article <41***********************@news.euronet.nl>, Janwillem Borleffs
wrote:

NotGiven wrote:

My hosting company has pre-intalled PEAR in a directory out of the web
directory (and not in php-includes).

I've tried including the absolute /to/path/ in the requre statement
but it does not work.

How would I access the PEAR packages?

Check the open_basedir directive in the php.ini file. Chances are that it
doesn't include the path to the PEAR installation.

When this is the case and you are unable to edit the php.ini file yourself,
all you can do is asking your hosting provider to include this path.

or use http://www.php.net/ini_set

I followed the instructions in PROGRAMMING IN PHP to access the PEAR DB
class, but my web hosting ISP's php configuration didn't allow it. Just
using the

require_once("DB.php");

would fail, even though the php variable include_path was set correctly
in the php.ini file. For some reason, the require will _work_ if I
include the following _before_ the require:

ini_set('include_path', ini_get('include_path')); # lets PEAR work

Why is this required? This is php 4.3. Is there some internal bug that
doesn't correctly access the include_path until it's "set" by ini_set?
I didn't see anything in the docs on http://www.php.net

--
DeeDee, don't press that button! DeeDee! NO! Dee...

[Tim Van Wassenhove]

In article <vi**************************@comcast.dca.giganews .com>, "Michael Vilain <vi****@spamcop.net>" wrote:

would fail, even though the php variable include_path was set correctly
in the php.ini file. For some reason, the require will _work_ if I
include the following _before_ the require:

ini_set('include_path', ini_get('include_path')); # lets PEAR work

Why is this required? This is php 4.3. Is there some internal bug that
doesn't correctly access the include_path until it's "set" by ini_set?
I didn't see anything in the docs on http://www.php.net

It's always handy to have a look at http://bugs.php.net in that case.
And it also handy to know that on a windows platform you have to
separate values with ; and on a unix platform with :

As in: include_path=.;c:/libs/pear VS include_path=.:/usr/lib/pear
--
Tim Van Wassenhove <http://home.mysth.be/~timvw>

[Michael Vilain]

In article <2p************@uni-berlin.de>,
Tim Van Wassenhove <eu**@pi.be> wrote:

In article <vi**************************@comcast.dca.giganews .com>, "Michael
Vilain <vi****@spamcop.net>" wrote:

would fail, even though the php variable include_path was set correctly
in the php.ini file. For some reason, the require will _work_ if I
include the following _before_ the require:

ini_set('include_path', ini_get('include_path')); # lets PEAR work

Why is this required? This is php 4.3. Is there some internal bug that
doesn't correctly access the include_path until it's "set" by ini_set?
I didn't see anything in the docs on http://www.php.net

It's always handy to have a look at http://bugs.php.net in that case.
And it also handy to know that on a windows platform you have to
separate values with ; and on a unix platform with :

As in: include_path=.;c:/libs/pear VS include_path=.:/usr/lib/pear

Not relevant really. The ISP runs Debian Linux. My MacOS X system is
10.3.5. Both php implementations have this problem. The bugs section
didn't give anything. The php.ini file on the ISP has

include_path=.:/usr/lib/pear

which is correct. But it only works if you use the ini_set function in
a script. Should this be logged as a bug on 4.x?

--
DeeDee, don't press that button! DeeDee! NO! Dee...

[Janwillem Borleffs]

Tim Van Wassenhove wrote:

or use http://www.php.net/ini_set

open_basedir can only be set in the php.ini file...
JW