adlpres Posted May 7, 2015 Share Posted May 7, 2015 (edited) Hello, I have to upgrade my prestashop from 1.5.x to 1.6.x. So I tried to use the "One click upgrade" module: it didn't work and I had to restore my website. The problem is that I didn't save the error messages. So I don't know now what it the reason of the bug, and I don't want to lose customers and money by breaking another time my site. It is written here that there is a log file in modules/autoupgrade... but I don't have it... And I need it. Could you help me please to find a way to know what is the bug ? Thanks a lot, Edited May 7, 2015 by adlpres (see edit history) Link to comment Share on other sites More sharing options...
PrestaHeroes USA Posted May 7, 2015 Share Posted May 7, 2015 I suggest creating a copy of your production shop, this will allow you to review the upgrade process before going live. Then you can make informed decision on how to move the upgrade to production. It's not advise to upgrade production but copy first. Link to comment Share on other sites More sharing options...
adlpres Posted May 7, 2015 Author Share Posted May 7, 2015 Thanks a lot for your quick answer. I already tried with a copy on a local computer... and that worked... Link to comment Share on other sites More sharing options...
PrestaHeroes USA Posted May 7, 2015 Share Posted May 7, 2015 Thanks a lot for your quick answer. I already tried with a copy on a local computer... and that worked... have you considered moving good upgrade to prod rather than upgrading prod? Link to comment Share on other sites More sharing options...
bellini13 Posted May 8, 2015 Share Posted May 8, 2015 have you considered moving good upgrade to prod rather than upgrading prod? i agree, when this scenario occurs, it is typically because your shared hosting environment does not have the available resources to allow the upgrade to execute properly. it is easier to just put the store in maintenance mode for 2-3 hours, copy your store to localhost, execute the upgrade, and then copy your localhost back to your prod store (obviously remove your prod store before that). Then log into your back office and reconfigure it, once it is working properly, then enable the store. Link to comment Share on other sites More sharing options...
adlpres Posted May 11, 2015 Author Share Posted May 11, 2015 Thanks for yours answers. I agree. That's what I have finally plan to do (although I have a dedicated server). Thanks, 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