Fresh install - open_basedir restriction - EDIT tmp dir location ?

[Vaupell]

Fresh install, new everything.

 

After installation I got a blank BO and SHOP..

 

Enabled Dev mode.

 

getting these errors in BO : 

 

Warning: file_put_contents() [function.file-put-contents]: open_basedir restriction in effect. File(/tmp/class_index.php.KtI4IX) is not within the allowed path(s): mylink/httpdocs/classes/PrestaShopAutoload.php on line 152

 

 

Warning: file_put_contents(/tmp/class_index.php.KtI4IX) [function.file-put-contents]: failed to open stream: Operation not permitted in mylink/httpdocs/classes/PrestaShopAutoload.php on line 152

 

 

 

Any ideas?

Edited September 5, 2014 by Vaupell (see edit history)

[Vaupell]

After copying the excakt permission setup from another presta shop running 1.6.0.9 which is working,

the FO loaded once, but never the BO..

 

Here's a link with debug enabled - http://www.diverse-shop.dk/

[vekia]

it's related to permissions on your hosting account

/tmp/ directory simply can't be accesses by your "www" service user

 

The open_basedir setting is primarily used to prevent PHP scripts for a particular user from accessing files in another user's account. So usually, any files in your own account should be readable by your own scripts.

 

make sure that your "www" user has got possibility to manage files in "/tmp/" directory

[Vaupell]

it's related to permissions on your hosting account

/tmp/ directory simply can't be accesses by your "www" service user

 

make sure that your "www" user has got possibility to manage files in "/tmp/" directory

 

Since I dont have physical access or anything to the server that is nothing I can change,

so i contacted the host, and he told me to 

 

- Change my tmp folder to this link /var/www/vhosts/diverse-shop.dk/diverse-shop.dk/phptmpdir.

 

So where do i change the link to my temp folder, especially since both FO and BO is just an error page,

I'm guessing somewhere in "phpMyadmin"  ?   for the sql db.

[vekia]

case you mentioned is not related to Prestashop settings but to host settings.

it's a case of host configuration.

[zapalm]

case you mentioned is not related to Prestashop settings but to host settings.

it's a case of host configuration.

it is a bug that was already fixed a few monthes ago: http://forge.prestashop.com/i#browse/PSCSX-2922