DeacoN_Carr Posted July 19, 2019 Share Posted July 19, 2019 Hello all, I could really use a hand... This morning - I tried to upgrade my site to the latest version of Prestashop using the 1-click upgrade module. Big mistake... After the update - I noticed that all of the links on my admin dashboard resulted in blank pages - and I couldn't take my page off of maintenance mode. So I tried to roll it back. I got an error "Maximum execution time of 30 seconds exceeded" and after that - I got a 500 HTTP error when trying to access the backend at all, while the main page was just stuck on the maintenance page. I had my web hosting provider roll the whole site back to this morning - now my main page looks perfect again - and I can log into the dashboard - but clicking on nearly all the links results in a page with the following text: Oops! An Error Occurred The server returned a "500 Internal Server Error". Something is broken. Please let us know what you were doing when this error occurred. We will fix it as soon as possible. Sorry for any inconvenience caused. Like I said the website looks and behaves fine - but I can't do anything in the background! I'm dead in the water! Can someone please help me figure out what's going on? I'd really appreciate it! Link to comment Share on other sites More sharing options...
DeacoN_Carr Posted July 19, 2019 Author Share Posted July 19, 2019 When I turn on error reporting - I get a slew of error messages - maybe this could help figure out whats up? I have attached it to this post. error.txt Link to comment Share on other sites More sharing options...
Rhobur Posted July 20, 2019 Share Posted July 20, 2019 First of all, your max_execution time was too low, you should've checked the requirements first, like here for example https://www.prestashop.com/forums/topic/884856-best-server-settings-for-prestashop-17-tested-in-production/ Second, it seems like your provider may have restored the files but not the database, check this with them. Link to comment Share on other sites More sharing options...
DeacoN_Carr Posted July 20, 2019 Author Share Posted July 20, 2019 Thanks for taking the time to respond Rhobur, I know now that there's a ton of things I should have done in retrospect - I'm new to this, but I've been learning an awful lot about what to do next time. Thanks for that link *bookmarked I contacted the host provider - they did a database restore to before the upgrade, but I'm still seeing the same error logs... Very strange - page looks great but the office is completely inaccessible. Any other ideas? Link to comment Share on other sites More sharing options...
Rhobur Posted July 20, 2019 Share Posted July 20, 2019 From what I see it seems that this error is specific to 1.7.6.0 therefore I think your site wasn't fully restored according to the previous version. A complete restore is like: 1. Move/Delete all your PS root files leaving the directory empty. 2. Copy/Delete the content of your current DB; 3. Find the files backup containing the previous PS version and copy the contents into the PS root dir. 4. Import the backup's DB content into your current empty DB. Now you will end up with the same PS as it was the date the backup was created. Link to comment Share on other sites More sharing options...
Dani80 Posted July 20, 2019 Share Posted July 20, 2019 Hola tengo un problema parecido. Una vez importada la base de datos y los archivos. Me da error 500 y no puedo acceder. Como o que se modifica para que vuelva a funcionar. Gracias Link to comment Share on other sites More sharing options...
DeacoN_Carr Posted July 21, 2019 Author Share Posted July 21, 2019 On 7/20/2019 at 12:19 PM, Rhobur said: From what I see it seems that this error is specific to 1.7.6.0 therefore I think your site wasn't fully restored according to the previous version. A complete restore is like: 1. Move/Delete all your PS root files leaving the directory empty. 2. Copy/Delete the content of your current DB; 3. Find the files backup containing the previous PS version and copy the contents into the PS root dir. 4. Import the backup's DB content into your current empty DB. Now you will end up with the same PS as it was the date the backup was created. That's what's so strange to me. They are claiming all content is completely wiped out and then restored. How could an error still persist? I'm not sure how that'd possible... Looks like I'm going to have to have the restore an even earlier backup and hope for the best. If it fails...I have to rebuild the whole damn store... Unless you know of a way to keep all your themes, products, etc and just do a fresh install, but I don't think that's possible. I'll check back in after the restore...wish me luck. 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