Hi there!

I tried to install Silverstripe on my kilu.de account. I followed the installation steps described on your site, but when I accessed the first time the folder where I copied (by FTP client) the locally unpacked files I got:

Warning: file_exists() [function.file-exists]: open_basedir restriction in effect. File(/data/multiserv/users/237215/projects/279827/www/.htaccess/_config.php) is not within the allowed path(s): (/data/multiserv/users/237215/projects/279827:/var/tmp/multiserv/users/237215/projects/279827:/data/apache/users/kilu.de/jburger) in /data/multiserv/users/237215/projects/279827/www/sapphire/core/i18n.php on line 1739

I tried to call the install.php directly and it opened the installation site. I put in the necessary data and the checks were all green, except the one advising me to give PHP more memory.. but it wasn't an error, just a warning.

So, I started the installation. I got again the above mentioned error message.

Accessing my site (http://jburger.kilu.de/), you can see that part of installation was successful, but something went wrong(?) as you can see.

Any ideas?
Thanks!

At a quick glance, this is probably a bug in PHP or Silverstripe (or both, depending on your viewpoint), but not a fatal one. Your installation should be okay.

I don't know the specific internals of Silverstripe, but as it seems it tries every directory-entry of the installation's root, whether it contains a file named "_config.php". Some of this directory entries are actually files and not directories, like ".htaccess" or "UPGRADING", so they cannot really have children. Since all the mentioned files in the warning messages on your website, which are declared not to be in open_basedir, are actually in open_basedir, this might be a faulty and misleading warning message on behalf of PHP and lazy (but not necessarily wrong) procedure on behalf of Silverstripe.

Anyway, you can help yourself by deactivating the PHP warning messages. This might help you:

php.net Documentation: php.ini display-errors

Try this method first:
http://www.php.net/manual/en/configuration.changes.php
If it fails, try this method at the beginning of "sapphire/main.php":
http://www.php.net/manual/en/function.ini-set.php

If you can confirm what I am saying, you might want to enter a bug report into the Silverstripe trac system (and at php.net).

About the .htaccess: Your provider might not allow this.

Concerning your main.php, you did right by putting it right at the beginning. But you can try this:

You should see something like that, if everything is good:

status ini_set(): 1
state display_errors: 0

If so, just leave:

You can try similar for the 'error_reporting' variable instead of 'display_errors'.

Anyway, it is not common to run PHP in a productive environment with warnings on -- this is for development or testing. So you may be able to convince your provider to change that or help you in your particular case.

I think this is a good read in your situation: turn off error reporting on your production site.

It's good to know, that at least the directives work. Maybe what you see is not considered a warning by PHP. Which would be weird, but nonetheless, try this error_get_last(). Something like:

Almost forgot: Put it at the end of main.php. This should give you your last error message, hopefully the warning ... and what ever you find under type, should be the bit you have to mask.