I'm thinking of upgrading Magento v184.108.40.206 to v220.127.116.11
I have never conducted this kind of operation.
I have read there are two ways of doing it. Using SSH or Magento Back-Office.
I know I can't upgrade directly from v18.104.22.168 to v22.214.171.124.
I might need to pass by v126.96.36.199, v188.8.131.52 and v184.108.40.206
I have read loads of forums articles. None of them explains the
process the same way.
What way is the best to conduct this operation (SSH or by Back-Office) ?
How to conduct this operation via SSH ?
How to conduct this operation via Back-Office ?
How do I specify the name of the new version I want to install, from magento Back-Office (and from SSH) ?
How do customers and admin data bases get updated after core and skin files ?
Thank you very much for your help !
I would recommend you to use method where you after making backups wil make new magento folder and then transfer your database into new magento default package. Then you will open site url and upgrade will start. Once it done you can copy your template and extensions.
If there will be error in the report file during upgrade then you will needto find out the issue and options to fix it.
Also prior upgrade dont forget to clean magento log dtabase tables.
Thanks for the reply.
Could you be more specific ? How do I transfer the old DB content to new magento default package ?
Hello Mate ,
you need to replace library file and core file of magento .
Please take back up before performing any operation in it .
and if you find any issue then disable module from module pool and enable each module one by one to find confliction of module .
let me know if you have any other issue .
You will need to upgrade from 220.127.116.11 to 18.104.22.168 before moving on due to the tremendous amount of database restructure. Once you have passed that hurdle, it's easier to upgrade to the last stable version of any major update after that.
Back in the day when I did it, 22.214.171.124 to 126.96.36.199 totally died on the database rework, 188.8.131.52 flew through with very little issue. Also you'll be doing this on a staging server till you get it right, or suffer economic damage while your site's down.
All third party modules, templates and your personal module rewrites will have to work with the final version you choose.
Also, everything works better if you use SSH and move your upgrade as a tarball from your staging server to your live server.
You have quite a bit of work ahead of you.
I see there are some solution to upgrade magento 184.108.40.206 to 220.127.116.11 directly. You can move data to higher version of Magento, even magento 1.9, magento 2.x.