Does compatible hosting really mean compatible?

I've just switched to HostForWeb and did a dolphin install.  To start off with, a long list of permissions had to be changed to continue.  2 former hosts never had that problem, only ffmpeg had to be changed on the others.  The next page of the install gives me about 15 error messages like this.

Warning: file_exists() [function.file-exists]: open_basedir restriction in effect. File(/usr/local/bin/php) is not within the allowed path(s): (/home/xxx/:/usr/lib/php:/usr/local/lib/php:/tmp) in /home/xxx/public_html/xxx.net/install/index.php(1294) : runtime-created function on line 2

I have a 2nd level ticket active on it, and was told that open_base is a security-related issue and I had to identify myself.  Okay, fine, but if i'm buying a Dolphin hosting package, why is this not off already?  One would think I should just be able to install and go!

I'm on my 3rd host right now, and 2 of them are "Dolphin Ready".  I have the feeling there will be more problems and i'll be looking for a 4th...

I'm just venting and frustrated. 

Quote · 16 Jan 2010
 
 
Below is the legacy version of the Boonex site, maintained for Dolphin.Pro 7.x support.
The new Dolphin solution is powered by UNA Community Management System.