Boost Your Tactics With Magento Upgrade Technique

Magento Upgrade

Now you are completely aware about what is Magento, How it is a boon for eCommerce, list of best Magento extensions and many other questions aroused in your mind regarding Magento. But, from past few days we have been continuously asked regarding Magento Upgrade and its ‘difficult’ procedure.

So here the question arises- Why do we exactly need the Magento upgrade, right? The most obvious answer to this question is-

  1. For the regular updates that brings new features to the existing Magento version.

  2. The important security fixes that are important for the Magento store’s safety.

So, we are here with the solution and ready to replace your word ‘difficult’ with ‘simple’. All you need to do is follow these few steps given below and then ultimately you will complete your mission of ‘Magento Upgrade’.

  • Get Set Go For Magento Upgrade

Success needs PREPARATION”. Pondering how to start? Don’t despair – To make the procedure more distinctive and clear we installed a shop on older version of Magento i.e. Magento 1.4.2.0 with sample data which is to be upgraded to the latest version of Magento – 1.9.1.0.

The site is installed into/home/upgtest/public_html, the database is on localhost and is called upgtest_magento. So if you utilize the guidelines from this article, ensure you supplant these values with your own ones.

  • Hey! Take The Backup!

It’s time for one of the vital deed whilst Magento Upgrade and that’s – Back-Up. Well, this task is not only for your Magento Upgrade but for any of your genuine changes you are about to implement on your valuable website.

Backup your Magento store – It’s a vital procedure which spares you from unsuccessful upgrades, site breakdowns, data loss and verifies the update won’t drive you up the wall.

The easiest variation of Magento backup can be done utilizing these two summons:

  • tar -czf ~/magento-files.tar.gz -C /home/ upgtest public_html

  • mysqldump –add-drop-table -h localhost -u upgtest -p upgtest_magento | gzip > ~/magento-db.sql.gz

Oh No! The Magento Upgrade did go wrong! Now? Well you can roll everything back with these codes:

  • cd /home/upgtest

  • mv public_html public_html-BAK

  • tar -xzf ~/magento-files.tar.gz

  • gzip -dc ~/magento-db.sql.gz | mysql -h localhost -u upgtest -p upgtest_magento

  • Does The Shirt Fits Your Size? – Check System Requirements

For instance just imagine a scenario where you get a shirt not of your size? Obviously after wearing you won’t feel comfortable and won’t be able to do any of your tasks. Similarly, this happens to Magento website when your server doesn’t suit your system requirements of the Magento version you are upgrading to. You might need to observe the PHP variant (5.4.x or 5.5.x is required) and memory_limit esteem in php.ini in any case.

Techniques of Magento Upgrade

  • A Sandbox Required – Create It

Listen carefully – Don’t ever update the primary site in case you’re not 100% sure about everything. On the off chance that you don’t test the update on a sandbox you won’t know whether the site is going to work after the update and the amount of time the overhauling procedure will take.

Your store’s update may require few hours, and there’s no reason for closing the essential e-shop down for the entire working day just to figure out that the overhaul went wrong, the times lost and you should simply restore the site from a backup copy. Note that recovering from a backup copy takes more time than backing down itself, so include this time.

To know if the upgrade is proper and running smoothly, let’s create a sandbox which we are going to upgrade first. Create an empty upgtest_staging first.

  • cd /home/ upgtest

  • mkdir public_html/staging

  • tar -xzf ~/magento-files.tar.gz –strip-components=1 -C public_html/staging

  • gzip -dc ~/magento-db.sql.gz | mysql -h localhost -u upgtest -p upgtest_staging

Now it’s time to set the sandbox up:

Start by editing the database connection settings in public_html/staging/app/etc/local.xml

Later go to upgtest_staging database, discover core_config_data table and change the website’s URL. For example if the previous URL was http://upgtest.local/ , then the new created URL will be http://upgtest.local/staging/ . Then turn the compilation off at System / Tools / Compilation. Disable cache at System / Cache Management.

Finally the sandbox is fully prepared to be upgraded.

  • Finally! It’s Time For Testing!

Deliberately check how your site is functioning. Go to Magento logs at/home/upgtest/public_html/staging/var/log and to web server logs at/var/log/httpd,/var/log/apache2 or/var/log/nginx relying upon the distribution unit and the web server you utilize. Precisely look through the logs to get any conceivable errors.

Now thing to note: Please verify that you deliberately test the execution of your extensions. In case if you upgrade to the most recent and fresh version of Magento, chances are that few extension will work with blunders or conflict with one another, as not all Magento Extension Suppliers test their modules immediately after the release.

  • Primary Magento Upgrade

If the cautious research and testing didn’t uncover any malfunctions or you have discovered how to fix the blunders, now it’s an ideal opportunity to overhaul the primary site. As the procedure of upgrade and testing takes certain time, make a fresh backup copy of the primary site, in light of the fact that you don’t want to recover from an old backup copy and lose the most recent changes. Before backing up, change your site to maintenance mode and disable cron.

Magento Upgrade-performance

  • touch /home/upgtest/public_html/maintenance.flag

  • crontab -u upgtest -e

Save a backup copy:

  • cd /home/upgtest

  • tar -czf magento-files.tar.gz -C /home/upgtest public_html

  • mysqldump –add-drop-table -h localhost -u upgtest -p upgtest_magento | gzip > ~/magento-db.sql.gz

Now repeat the same procedure on your fundamental site.

We don’t suggest supplanting the primary site with the sandbox store, as all things considered you’re in danger of losing the information that was changed or included while testing.

Done! The only thing left is to turn the maintenance mode off and enable cron:

  • rm /home/upgtest/public_html/maintenance.flag

  • crontab -u upgtest –e

Also, remember that there are some of the Magento features that need not to be re-installed or upgraded as it can be carry forwarded to the new version. For an instance, the Magento connect feature in all the version is the same, so you can take the backup from its older version. Other than that, there are features like the one-step checkout that doesn’t require updating to get installed with the new version.

Yupiee! The mission is completed! Now your website is upgraded to the latest stable Magento version

Kodematix’s professional team is always ready to help you with any of your questions regarding Magento. Contact us at any clock for your consultation.

Leave a Reply