Jump to content

Fatal Error Messages (Urgent)


Recommended Posts

Not sure about the second error but the first one is clear.

Go to var/www/html/cache/smarty/compile/ and delete everything in that directory.

Then make sure that compile is 755.

Hi,

 

That has already been done and the permissions are set to 755 also.

 

But the error still appears. Especially when the website traffic increases during a product launch.

Link to comment
Share on other sites

Smarty makes template files and puts them in to compile directory.

At first I thought that smarty has no permissions. 

It can happen for various reason eg. you uploaded your website and smarty cannot override template files as they belong to different users/groups.

 

BUT if this only happens then traffic is increased you might be out of hard drive space. 

Link to comment
Share on other sites

Try turning off all caching so see if that clears the error message

 

If it does clear the message, then turn caching back on, if the error returns it could be a user / group / problem as Simonas suggested. 

Link to comment
Share on other sites

i encountered this issue recently.  the problem was that some cache files were being created under the apache user, while other cache files were being created under the web account user.  And having permissions as 755 do not allow the apache user to write folders and files.

 

You don't mention what version of Prestashop you are using, for me it was PS v1.6.0.9

 

To correct my issue, I had to stop routing PHP handling away from NGINX, and keep all PHP processing in apache directly.  I also recently upgraded my PHP version to 5.5.30 which may play a part in the issue.

Link to comment
Share on other sites

i encountered this issue recently.  the problem was that some cache files were being created under the apache user, while other cache files were being created under the web account user.  And having permissions as 755 do not allow the apache user to write folders and files.

 

You don't mention what version of Prestashop you are using, for me it was PS v1.6.0.9

 

To correct my issue, I had to stop routing PHP handling away from NGINX, and keep all PHP processing in apache directly.  I also recently upgraded my PHP version to 5.5.30 which may play a part in the issue.

 

My prestashop version is 1.6.1.1 

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...