Dolke Posted January 16, 2019 Share Posted January 16, 2019 Hi guys, I still remember 2013 when we started to work on our Prestashop website... since then noting really changed except we gain reputation, customers and grown to over 15000 products! Back then we stopped at 1.5.4.1 version and haven't updated. Since update from 1.5.4.1. to any 1.7.x version is more migration rather then upgrade Im aware that it i will be painful process or does it have to be? Unfortunately we done a lot of core changes and modified a lot of core PS files which is never a good idea. Back then we thought it will be the easiest way to adapt Prestashop for using on our market and it was, but now problem is that we need to overwrite these changes with an update and implement them differently. My first question would be is there a way (except builtin prestashop feature which I find not thrustworthy) to list all core files that have been modified and maybe even list these modifications? Thank you in advance Link to comment Share on other sites More sharing options...
joseantgv Posted January 16, 2019 Share Posted January 16, 2019 45 minutes ago, Dolke said: Hi guys, I still remember 2013 when we started to work on our Prestashop website... since then noting really changed except we gain reputation, customers and grown to over 15000 products! Back then we stopped at 1.5.4.1 version and haven't updated. Since update from 1.5.4.1. to any 1.7.x version is more migration rather then upgrade Im aware that it i will be painful process or does it have to be? Unfortunately we done a lot of core changes and modified a lot of core PS files which is never a good idea. Back then we thought it will be the easiest way to adapt Prestashop for using on our market and it was, but now problem is that we need to overwrite these changes with an update and implement them differently. My first question would be is there a way (except builtin prestashop feature which I find not thrustworthy) to list all core files that have been modified and maybe even list these modifications? Thank you in advance Probably not very sophisticated, but I used WinMerge to compare folders. I compare /classes and /controllers store folders against original files. 1 Link to comment Share on other sites More sharing options...
Dolke Posted January 16, 2019 Author Share Posted January 16, 2019 Thank you for the suggestion. I will check the software! Any other general suggestions for the upgrade? Link to comment Share on other sites More sharing options...
JBW Posted January 16, 2019 Share Posted January 16, 2019 Not sure how it look in 1.5 but in later versions I can see a list of modified files in "advanced parameters->information". Same is available in the 1-click-upgrade module, too. General suggestion: Build a 1.7 shop separately and migrate the data when everything else is running fine (theme, modules, your modifications)... Link to comment Share on other sites More sharing options...
ksaan Posted January 16, 2019 Share Posted January 16, 2019 2 hours ago, Dolke said: Back then we stopped at 1.5.4.1 version and haven't updated. Since update from 1.5.4.1. to any 1.7.x version is more migration rather then upgrade Im aware that it i will be painful process or does it have to be? It depends on what you call "painful". Will need time ? Yes. Money ? Probably. There will be issues and bugs ? For sure. How many ? Will depend on who does the migration and how well you test the new shop. But - will your team be happy with the newest shop ? you can make it happen - will your new shop serve you well and be up-to-date with selling practices ? probably (maybe it's time to re-think this theme of yours ? - will you benefit from new features ? if there was a module only compatible with 1.6 or 1.7 : you're gonna be able to use it ! also if you upgrade your server to php7 you should see a speed boost of your pages, which is a nice-to-have to sell better So you can make it a beautiful and useful project that serves your company 1 Link to comment Share on other sites More sharing options...
El Patron Posted January 19, 2019 Share Posted January 19, 2019 (edited) here is generic upgrade project that has little to NO production downtime when we do upgrades, we do it on a copy of production and when ready we replace production with new copy and import out of sync customers/orders..there may be more depending on your shop.... === checklist .doc'ing identify all 3rd party modules and obtain their 1.7 compatible zips identify core changes (mentioned above), you should also identify template changes (.tpl's). .doc existing overrides select new feature rich theme, we like Leo themes but there are lots of others review existing hosting, most age just like your shop. it's best to get new hosting account and move to that rather than try to have old hosting upgraded === pre upgrade build a test copy of your production shop, then back this up so you can refresh your test system until upgrade completes. hopefully your hosting allows php level by domain/subdomain so you start out with php7.2. if not find new hosting. uninstall 3rd party modules make sure overrides clean up php max execution time to 'large', 600 or 1200... === upgrade back up this test system so you can restore if upgrade fails so you do not have to uninstall moudule/override again perform upgrade install/configure modules apply core changes install configure theme ===shake and bake until prod ready == Production installation create a new copy of production to be used for historical purposes import customers/orders from old shop to new shop copy new shop to production or if new hosting (recommended) switch dns happy upgrading el Edited January 19, 2019 by El Patron (see edit history) 2 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