[SOLVED] What does this Error mean

[kalua]

Hey all

 

Does anybody know what this error means?

 

Warning: tempnam(): open_basedir restriction in effect. File(/home/.sites/102/site1393677/webcache) is not within the allowed path(s): (/home/.sites/102/site1393677/web:/home/.sites/102/site1393677/tmp:/usr/share/pear) in /home/.sites/102/site1393677/web/classes/PrestaShopAutoload.php on line 151

Fatal error: Class 'PrestaShopLogger' not found in /home/.sites/102/site1393677/web/controllers/admin/AdminProductsController.php on line 1906

Edited January 21, 2015 by kalua (see edit history)

[mytheory.]

HI,

 

It may be a server side setting error.

 

It appears that your host may have an open_basedir rule that is blocking access.

 

To be honest I'm not sure... but I think it is something you may want to first contact your host about.

 

HTH!

[kalua]

Thanks MyTheory, i have located one of all the bugs. The first one related to /PrestaShopAutoload.php will be this:

In the original File (1.6.9 and also 1.6.11) PrestaShopAutoload.php at line 35 i can find this code:

 

const INDEX_FILE = 'cache/class_index.php';

 

but there should be another slash in the code like:

 

const INDEX_FILE = '/cache/class_index.php';

 

And it worked. The error with the tempnam() did not appear any more. But still the problem with Fatal error: Class 'PrestaShopLogger' not found ...

[mytheory.]

Hi,

 

Glad you got 1 thing figured out.

 

As for the other Fatal error... I'm not sure as my experience is limited.

 

However, going through a bit of info, the PrestaShopLogger is class that logs errors into the db and emails you if the severity is high (or as it is set). So with that in mind, first, can you see if you have this class file in your installation? Check to see if this file exists - /classes/PrestaShopLogger.php

 

Then can you see if you can access the logs page in the backoffice? In the BO, go to Advanced Parameters > Logs ... can you access the page? Is there a list of messages?

 

Also, please see if your host sees any errors on your server logs... it may be a memory issue. Like if PS is trying to write a log to the db but its taking too long or runs out of memory in their logs it may show a 500 internal server error. In this case, they will need to increase php memory for you.

 

Quick question... where is the error occurring?

 

Thanks!

[kalua]

Hey

 

Thanks for your help, getting light into the problem. Indeed the logs stopped a few days ago when this problem occurs.

Just checked the the memory and it is set to 75M. That might be the problem ...

 

Error appears while updating products ...

 

I will contact the host and reply the status about the problem soon.

 

Update: Had been a problem of the memory limit. Everythings fine now

Edited January 21, 2015 by kalua (see edit history)