URGENT! New Error Message. Everything was running fine

Hello …



Everything was running fine at my shopping cart. I clicked on an order number to view the details and got this error message.



Error: Can’t write template cache in the directory: /home/username/public_html/var/compiled/customer.

Please check if it exists, and has writable permissions.



I didn’t change anything concerning the permissions and was using it seconds before.



Can anybody advise as to how get the store back online?



The current permissions for the /var/complied/customer directory is 755



Thanks!



Jeff

I just found out that my hosting company is installing PHPSuExec which will not allow permissions to be greater than 755.



The are citing security. This is an issue for me.



****.

Seems like your only choice is to move host. I’d suggest talking to some of the Pro’s here to help you out. I personally like and use Jesse-Lee for website issues. He’s quick and does great work.

[QUOTE]Seems like your only choice is to move host.[/QUOTE]

Are you kidding me? :smiley:



This one is ridiculously simple and just means you will need to update the permissions on a few files and nothing more.



One thing that will be a concern if you don’t own the server or have any kind of administrator access is all the “nobody” owned files. If your host is changing to either phpSuExec or SuPHP, they will need to reset the ownerships on files in your account currently owned by user “nobody” to your login name.



Permissions (Basic recommendations)

-------------------------------------------------------------------------------------

I actually don’t recommend 777 EVER !!! (That goes for DSO people too!)



*** Oh and just a side FYI, I’ve done hundreds of CS-Cart installations on every type of system possible and never once had a single problem running anything flawlessly but then I know what I’m doing too. :wink:



phpSuExec | suPHP

-----------------------

755 (owner:owner) Folders

600 (owner:owner) PHP Scripts

400 (owner:owner) Configuration Files (config.php, etc)

600 (owner:owner) Script files requiring WRITE access

640 (owner:nobody) Non-Script Files, HTML, Images, etc

750 (owner:nobody) CGI/Perl Scripts



If no access to setup group ownerships then set Non-Script files to [COLOR=“Navy”]644[/COLOR] and CGI / Perl Scripts to [COLOR=“Navy”]755[/COLOR]





DSO (Apache Module)

-----------------------------------

750 (owner:nobody) Folders

640 (owner:nobody) PHP Scripts

640 (owner:nobody) Configuration Files (config.php, etc)

660 (owner:nobody) Script files needing to have “WRITE” access

640 (owner:nobody) Non-Script Files, HTML, Images, etc

750 (owner:nobody) CGI/Perl Scripts



If no access to setup group ownerships then set Folder to [COLOR=“Navy”]755[/COLOR], PHP Scripts and Configs to [COLOR=“Navy”]644[/COLOR], Non-Script files to [COLOR=“Navy”]644[/COLOR], Write Files to 666, and CGI / Perl Scripts to [COLOR=“Navy”]755[/COLOR]


[QUOTE]I just found out that my hosting company is installing PHPSuExec…[/QUOTE]



Are you absolutely 100% certain that your host is changing to [COLOR=“Red”]phpSuExec[/COLOR]?



If your host truly is changing to phpSuExec, they really need to talk to me ASAP!



phpSuExec is fatally flawed and actually has more serious security concerns than the Apache module (DSO) based PHP it was designed to replace and if they really are going to phpSuExec, then I would agree with KBM on changing hosts in that case.



However, if they are changing to SuPHP, that is an entirely different story and this would actually be a very good thing for you and drastically increase the security to your site and you just simply need to get the correct ownerships and permissions.