2017 experienced many update fluctuations with 2 main upgrade versions: Magento 2.1.7 and Magento 2.1.8. It marked milestones for development of Magento CMS and improve our belief that Magento CMS will become stronger and stronger. MagenTech is Magento Provider and we never forget our mission that "Keeping improving products". As soon as the notification of Magento 2.1.8 was out, our developers/ researchers started studying and the result is that all our Magento 2 Themes were upgraded to be compatible with the latest version of Magento 2.1.8.

Hi guys! We come back. Maybe in the previous post How To Upgrade Magento 2 to The Latest Version - Run System Upgrade, you have already know what should do when having upgraded file of Magento 2. However, as we mentioned before, there are 2 ways to take action. And today, we will bring you the remaining way: Command-line Upgrade! Thanks to Magento.com Commuinity again for giving us these fantastic way!

Hi everyone, we come back! Magento 2.1.8 has recently been released. However, not all of us know how to upgrade the current version to the latest version because they are scared of unexpected errors during update/ installation. Thank to Magento.com for this useful artical. Now let's learn how to upgrade Magento 2 with us!

Welcome to our Blog. Now we come back with The Latest version of Magento 2.1.8 (formerly Community Edition). Perhaps, most of you are ready to update this version. However, wait for a while, let's have a look what's new in this version, shall we?

Hi my friends, PrestaShop 1.7 is so popular today. However, not all of us know clearly about this newest version. Some of our customers get troubles of not compatible. Well, do you know that "PrestaShop version 1.7 is not really stable?". That is the reason why PrestaShop team has to do everyday to provide you with the best services as well as the best juice. The question is "How can we deal with this bad issue?". We will tell you in this blog.

We know you expected a lot from the next minor version, and we didn’t want to let you down. It closes almost twice as many pull requests as 1.7.1.0, 1.7.1.1 and 1.7.1.2 combined (126 vs. 203), and we took a month more of testing and improving it.