Look for the line in the php.ini (it should already be in there on install, but may be comented out). It will say ‘include_path = .:/somepath:/anotherpath’. You need to append ‘:/home/yourusername/php’ and possibly ‘:/usr/lib/php’ to the end of this list. The php.ini for your bluehost should be in your webroot. The PEAR install should have created a folder ‘php’ or added to it, in the folder ‘/home(3?)/yourusername’. If you don’t have a php folder in ‘home(3?)/yourusername’ then you need to install PEAR through the CPanel, or find out where the thing installed it in your user folder/shared server space.

You can also set this manually on one php script page using ini_set(’include_path’, ‘.:/yoursdesiredpath:/yourdesiredpath2′);

It took me forever to use the include_path effectively. Note the syntax, the . means ‘look in the current directory first’ and then each other path is separated by a :. These are all the places php will look for included/required php files/classes. Essentially the php_include path is like your php mappings, telling php where to find files you will include in your scripts. With coldfusion it was a lot clearer with a gui server admin that had you add each server mapping. It took me a bit to translate ‘include_path’ to ‘php server mappings’ in my mind. To begin with, I had been used to using includes for templating purposes only.

Also note that the VTCalendar stuff may have screwy interfacing with your php include_path settings.