indus Posted September 13, 2013 Share Posted September 13, 2013 (edited) Hi I have been trying to upgrade from 1.4.11 to the 1.5 version via the auto upgrade module without success. Anyone who has managed to do the same, can you please post what and how you managed to do it. I wil try the manual upgrade process in a few days, but on prestashop documentation site it says this method is deprecated. My biggest issue is that my site wont come out of maintenance mode. And in the backoffice, no products are visible. regards, Edited September 13, 2013 by indus (see edit history) Link to comment Share on other sites More sharing options...
Nils-H Posted September 13, 2013 Share Posted September 13, 2013 I upgraded from 1.4.3 via 1.4.11 to 1.5.4.1 without problems. The theme wasn't compatible, but I already knew that in advance. Link to comment Share on other sites More sharing options...
indus Posted September 13, 2013 Author Share Posted September 13, 2013 Did you switch to the default theme before upgrading? Link to comment Share on other sites More sharing options...
Xavier Borderie Posted September 13, 2013 Share Posted September 13, 2013 Please note that the manuel method is only deprecated because it is much harder to perform than the automatic one, and takes much longer, resulting in potentially more issues when you forget or bypass one step. Otherwise, if the automatic method does not work for you, you can still use the manual method, of course. Link to comment Share on other sites More sharing options...
Nils-H Posted September 13, 2013 Share Posted September 13, 2013 Indus: No, I didn't. Link to comment Share on other sites More sharing options...
indus Posted September 30, 2013 Author Share Posted September 30, 2013 Hi I was able to upgrade to 1.5.5 with help from the prestashop team, especially from Gregory Roussac. Seems like i had around 300 empty tables in ps_configuration_lang which i had to delete to make the upgrade work. Link to comment Share on other sites More sharing options...
bellini13 Posted October 1, 2013 Share Posted October 1, 2013 I use a variation of the manual upgrade process when I upgrade my clients stores. It works very well, but requires a level of technical expertise, trial an error and the ability to know how to troubleshoot and analyze issues and work around them. I would say 9 times out of 10 it works without issue. The one time it does not work is when you need to play detective, and it is typically related to an existing bug which has been reported and/or corrected. Link to comment Share on other sites More sharing options...
Dh42 Posted October 1, 2013 Share Posted October 1, 2013 I would say that I have upgraded around 15 -20 shops from 1.4 to 1.5 To expound on what Bellini said about bugs, I always disable 3rd party modules, I have had errors with them before. Link to comment Share on other sites More sharing options...
bellini13 Posted October 1, 2013 Share Posted October 1, 2013 I concur, in order to be successful, you have to disable anything custom that you have introduced (custom theme, 3rd party modules, overrides etc...). Get the upgrade to work using core Prestashop features, and then add back your customizations only after successfully upgrading. Link to comment Share on other sites More sharing options...
shroom Posted October 1, 2013 Share Posted October 1, 2013 (edited) Our shop needed a design change (we were using a customized default theme). We thought it was a good time to do that big upgrade and so I had a theme ready for v1.5.x. Nothing impressive as I did a v1.2.5 > v1.4 couple years ago. I did couple upgrades on a test domain and always this way : v1.4.8.2 > v1.4.11.0 > v1.5.5.0. The auto-upgrade process went quite fine, apart from one or two warnings that didn't prevent the upgrade to complete successfully (mostly due to a bugged auto-upgrade module). We did the real upgrade couple weeks ago, with an updated auto-upgrade module and it worked fine. Of course I had (and still have) to fix multiple minor bugs and annoyances, but no real major bugs and nothing related to the upgrade itself. Tips : - if you've customized your v1.4 installation, create a list of the changes that were made - duplicate your production database and create a new sql user for that specific test database - copy your v1.4 installation to a test subdomain on your server and update the config file in order to use the duplicated database (and not your production one) - remove all the custom override codes you've added - update your auto-upgrade module on the test domain - upgrade to the latest v1.4 then unlock the v1.5 upgrade option and untick the backup settings (not needed on a test installation, will speed up considerably the process) and let it deactivate the external modules during the process - test, test, test and test; unless you have issues with your host, there's no reason for the process not to work - apply your custom work back accordingly (you'll have to update most of it to the new code) - you'll probably have to update your cron jobs too - make backups prior to do the real upgrade - enjoy cool new features, regret the missing ones and be ready for new annoyances Edited October 2, 2013 by shroom (see edit history) Link to comment Share on other sites More sharing options...
bellini13 Posted October 2, 2013 Share Posted October 2, 2013 Many hosts have resource limitations (memory, cpu, process execution time etc..) which interfere with the upgrade. So get around that by performing the upgrade on a test system that does not have these limitations, and then simply move the store to your live domain. Link to comment Share on other sites More sharing options...
Recommended Posts