Jafar Muhammed Posted July 9, 2020 Share Posted July 9, 2020 (edited) Hello Community, My host recently migrated all the domains to a different home directory. Previously, I have installed PrestaShop using Softaculous, and the installation path was /home/users/domains/myshop.com/public_html Now the new home directory is /home2 instead of /home. That means /home2/users/domains/myshop.com/public_html I can access all of my files and databases. But both my front end back office is showing HTTP 500 Error. How can I change my directory from /home to /home2 and get back my website up? Edited July 11, 2020 by Jafar Muhammed (see edit history) Link to comment Share on other sites More sharing options...
Guest Posted July 10, 2020 Share Posted July 10, 2020 (edited) 1. PrestaShop version 2. enable debug mod ./config/defines.inc.php 3. screenshot error messages Changing the home folder should not affect the running of Prestashop. Probably some module saved the old path to the files. Edited July 10, 2020 by Guest (see edit history) Link to comment Share on other sites More sharing options...
Jafar Muhammed Posted July 10, 2020 Author Share Posted July 10, 2020 Hello @Guest PrestaShop version 1.7.6.5 Debug mode enabled. Now front end works fine, but the back office is not loading. Please see the attached screenshot. Link to comment Share on other sites More sharing options...
Guest Posted July 10, 2020 Share Posted July 10, 2020 https://github.com/PrestaShop/PrestaShop/issues/12117 Link to comment Share on other sites More sharing options...
Jafar Muhammed Posted July 11, 2020 Author Share Posted July 11, 2020 Hi @Guest I checked /phppsinfo.php and see that every requirement and almost all recommendations are met. I just switched my PHP version, and now I can log in to BO. Some plages in BO is accessible like Customer Service, Orders etc. But some pages are still showing the same error. Products, Administration pages are examples. Within the same hosting, I can install a new PrestaShop without any such errors. Link to comment Share on other sites More sharing options...
Guest Posted July 11, 2020 Share Posted July 11, 2020 Hi, I thought there would be a bug in the PHP version. Other errors indicate missing translations. It's really hard to identify a problem from your posts. It is necessary to carefully study the error logs that are in the ./var/logs folder. Link to comment Share on other sites More sharing options...
Guest Posted July 11, 2020 Share Posted July 11, 2020 1. first delete all files from the logs folder 2. Recall the administration error 3. Upload to the forum files from the logs folder as attachments Link to comment Share on other sites More sharing options...
Jafar Muhammed Posted July 11, 2020 Author Share Posted July 11, 2020 Hi @Guest, I have attached the dev.log dev.log Link to comment Share on other sites More sharing options...
Guest Posted July 11, 2020 Share Posted July 11, 2020 PHP min 5.6 max 7.2 Link to comment Share on other sites More sharing options...
Guest Posted July 11, 2020 Share Posted July 11, 2020 If it's still a problem, it's better to hire someone to work and debug. It is not possible to repeat indefinitely what has already been solved and how to eliminate the errors. Several steps are written, such as manually renaming the dev and prod folders in the ./var/cache folder to FTP. Also turn off override rewriting, turn off non-original Prestashop modules ....... Link to comment Share on other sites More sharing options...
Jafar Muhammed Posted July 11, 2020 Author Share Posted July 11, 2020 Hi @Guest, I have changed PHP to 7.2. Now I can access both front and back without errors with Debug mode enabled. When I disable the debug mode, same HTTP 500. Link to comment Share on other sites More sharing options...
Guest Posted July 11, 2020 Share Posted July 11, 2020 Rename dev and prod folders in ./var/cache folder. Delete renamed folders dev and prod. Clear cache. https://presta.site/blog/en/how-to-clear-prestashop-cache/ Link to comment Share on other sites More sharing options...
Jafar Muhammed Posted July 11, 2020 Author Share Posted July 11, 2020 Hi @Guest That resolved my issue. Thanks a ton 😍 Link to comment Share on other sites More sharing options...
Guest Posted July 11, 2020 Share Posted July 11, 2020 I wrote to you about clearing the cache before, you just didn't read the whole posts and you didn't do what I wrote you. Otherwise, you should have solved it a long time ago. You can give a like by clicking on the gray heart below my posts. Next, edit the first post and write SOLVED in the topic title. Link to comment Share on other sites More sharing options...
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now