Anyway, we discovered that H-Sphere’s PHP5 support, as installed; has a bug in the php.ini files that it creates.   Since H-Sphere can support both PHP4 and PHP5 in parallel, as well as Apache 1.x and 2.x, there’s quite a bit of configuration file juggling going on.

The php.ini file for PHP5 that was in use was referring to the PHP loadable module path for Apache 1.x, and not 2.x.   For other administrators of H-Sphere, you might want to double check that this line is appropriate in your own php.ini.

For instance, our /hsphere/local/config/httpd2/php5/php.ini file had this entry:

;include_path = “.”
include_path = “.:/hsphere/shared/apache/libexec/php5ext/php/”
doc_root =
user_dir =
extension_dir = “/hsphere/shared/apache/libexec/php5ext/”
cgi.fix_pathinfo = 1

When it really should have been:

;include_path = “.”
include_path = “.:/hsphere/shared/apache2/libexec/php5ext/php/”
doc_root =
user_dir =
extension_dir = “/hsphere/shared/apache2/libexec/php5ext/”
cgi.fix_pathinfo = 1

This must have occured when we did the PHP5 upgrade, and didn’t take effect until Apache actually restarted again some time later.

Thanks for being patient during the issue!