Software Development:
Individual Programming

Symptom

You are trying to install the content management system (CMS) concrete5. When checking the installation prerequisites, the program complains that it cannot access the tmp path. The installation cannot continue. In some articles on the internet, you read that you need to ease the open_basedir restriction.

Cause

The tmp path is a "temporary" folder where programs cache data. concrete5 assumes it can use the common host tmp folder and wants to access the folder that is outside your webspace. This is impossible for security reasons. Therefore, the open_basedir limit cannot be relaxed. It limits the access of your scripts to your own webspace. Instead, you must use a tmp folder in your own webspace.

Solution

In the "session" section of the file //conrecte/config/config.php (for the first domain of your webspace, the main domain, usually /httpdocs/conrecte/config/config.php) you will find the line

save_path => null

Change the line so that the save_path variable points to your own tmp directory, e.g.

save_path => '/var/www/vhosts//tmp'

Instead of "your main domain", enter the first domain of your webspace under which your webspace was set up. If your main domain is "mydomain.com", e.g.

save_path => '/var/www/vhosts/mydomain.com/tmp'

It is correct that the tmp directory is outside of your document root directory. If you set up concrete5 in another domain of your webspace, you still use the general tmp directory of the webspace. It is unnecessary to create a seperate tmp directory for each domain.

Overview of frequently asked questions