Austra02 Posted August 16, 2012 Share Posted August 16, 2012 Hi everyone, My entire site (silk.manehairandmakeup.com.au) was moved to a new server by my hosting company due to resource issues on the old server. Everything 'seemed' to be fine after the move, but I've started to notice some issues that are a real problem. When I go into the Back Office > Tools > Configuration Information, I now have the attached error(s) in the required parameters section. These weren't there prior to the move. I have checked permissions on all the directories and they are all 775 - Folders and 644 - Files: ~Set write permissions for \"config\" folder ~Set write permissions for tools folder ~Set write permissions for \"cache\" folder ~Set write permissions for \"img\" folder and subfolders, recursively ~Set write permissions for \"modules\" folder and subfolders, recursively ~Set write permissions for \"themes/glamfashion/lang/\" folder and subfolders, recursively ~Set write permissions for \"translations\" folder and subfolders, recursively ~Set write permissions for \"upload\" folder and subfolders, recursively ~Set write permissions for \"download\" folder and subfolders, recursively I have tried setting all folders AND files to 755 but the error is still there. I really don't want to up to 777 - especially the files as my site will be prone to hacking; correct? Any other suggestions as to how to correct this issue??? This is the REAL BIG issue: I have some custom CMS articles that are linked to in the left column of my site. While the links to the articles are shown in the column, when I click on one of those links, there is a blank page (my 'theme' is shown, just a blank page within that theme). The articles are all still 'enabled' and all is fine as far as the BO is concerned, but none of there are displaying. The default CMS articles (Terms, Privacy Policy etc) are also NOT displaying when clicking on the link to their respective pages. I have also noticed that I am getting the following error when I open the Modules tab in the BO: "The following module(s) could not be loaded: All modules cannot be loaded due to memory limit restriction reason, please increase your memory_limit value on your server configuration" But the CMS module is loaded and enabled. I know what this error is and it is being fixed at the moment, but there is an issue with my .htaccess file allowing global php configuration so I can't adjust that just yet, until my host has resolved the issue. Could the CMS module actually be effected by the memory issue but still show as loaded properly? Can someone PLEASE offer some assistance or information on these issues (especially the CMS one) as my site has now been offline for over two days and I was due to launch almost a week ago now, and I still can't? Thanks in advance! Scott (AKA: desperate!!) :-| Link to comment Share on other sites More sharing options...
SuperCharlie Posted August 16, 2012 Share Posted August 16, 2012 Are you using seo friendly urls? If so, try disabling them temporarily and see what happens. Link to comment Share on other sites More sharing options...
pashaps Posted August 22, 2012 Share Posted August 22, 2012 We're actually having the same exact issue. I'm thinking its a file-ownership problem, but haven't been able to pinpoint it. Anybody else have ideas? Link to comment Share on other sites More sharing options...
Austra02 Posted August 22, 2012 Author Share Posted August 22, 2012 **PASHAPS** Mine turned out to be a combination of: File permissions. The new server I had been migrated to had been provisioned incorrectly and as a result, the default permissions of Prestashop (755 for folders and 644 for files) was not working. Consequently, I had to modify the perms to 777 for all files and folders in the standard set of folders of Prestashop (config, modules, img, etc). Once the hosting company had configured php on the server properly, I was able to change the perms back to the minimum correct required for Prestashop (755 and 644) and everything corrected itself as far as that was concerned. The newly provisioned server again, did not have suPHP enabled (something to that effect anyway) and this was causing the 500 Internal Server Error whenever I enabled the suPHP line in the .htaccess file. If this is happening to you - I would get onto the hosting company immediately and get them to ensure it is enabled and running on your server as once they installed this module in the php config of the server (my terminology may be slightly incorrect - but the context is correct), this immediately fixed my '500 Internal Server Error' Issue. Hope this helps! Scott. Link to comment Share on other sites More sharing options...
pashaps Posted August 22, 2012 Share Posted August 22, 2012 Yep, just recently figured out the problem was caused by PHP and the user account it runs as. On our old server it was running as the account user. On the new one it runs as "nobody". suPHP allows it to run as the account user, so that's being installed and I expect it to solve the problem. 1 Link to comment Share on other sites More sharing options...
EK-Si POS Posted August 22, 2012 Share Posted August 22, 2012 0755 is the default for directories, except directories in your first post's first section. They always should be 0777 if your server and php user is not the owner of these directories. For general: 7=(read)4+(write)2+(list)1. First 7 is for the owner, second for the group, last is for everyone. If the directory owned by 'root', it won't be writable by your server and php scripts user (ex: 'www-data') if the permission is 0755 as you said. Ex: if the "img" folder is 0755, you won't add images of your new products. Link to comment Share on other sites More sharing options...
Austra02 Posted August 22, 2012 Author Share Posted August 22, 2012 0755 is the default for directories, except directories in your first post's first section. They always should be 0777 if your server and php user is not the owner of these directories. For general: 7=(read)4+(write)2+(list)1. First 7 is for the owner, second for the group, last is for everyone. If the directory owned by 'root', it won't be writable by your server and php scripts user (ex: 'www-data') if the permission is 0755 as you said. Ex: if the "img" folder is 0755, you won't add images of your new products. Only if you are on an older serve running an older version of php. Mine are ALL set to 755 and the entire shop is running without any issues what-so-ever. And yes, with 755 set on the img folder set to 755, I most certainly CAN add images to my new products... I have created about 30 new products since setting back to 755 - all with images. It is a hosting issues and the version of php and the settings on the server. Link to comment Share on other sites More sharing options...
EK-Si POS Posted August 22, 2012 Share Posted August 22, 2012 Austra02, You are using something like suPHP, you can add images because PHP is running as root or whatever that has permissions to these directories, by the "owner" 7. It is not about older PHP version or old server (if the server is unix-like). And I'm sorry that I didn't write my answer is for everyone who reads this. I wrote because someone would think that these directories should be 0755 (without suPHP). Link to comment Share on other sites More sharing options...
Austra02 Posted August 22, 2012 Author Share Posted August 22, 2012 Ah, okay. My bad - now I understand, and see what you were saying :-) So, yes; 100% agree. Cheers, Scott. Link to comment Share on other sites More sharing options...
benjamin utterback Posted August 22, 2012 Share Posted August 22, 2012 Hello All, Well, it seems like this thread is solved! I will go ahead and mark it this way. Thank you all for choosing PrestaShop, we hope to see you around more often! Link to comment Share on other sites More sharing options...
Recommended Posts