It has been five months since the release of PrestaShop 1.7 stable version. Currently, the latest version available in 1.7 series is PrestaShop 188.8.131.52. The version 1.7 was an important milestone for PrestaShop as it was a major release after a long gap of nearly one and half year.
The new version is a complete makeover and does not carry the legacy of the PrestaShop 1.6.x versions on various aspects. Instead, it provides a completely new architecture of those aspects. For example, the 1.6 themes do not work here, because 1.7 uses Symfony2 framework instead of Bootstrap-based and Smarty framework which were used in 1.6 versions. So View of Users about PrestaShop New Version 1.7 are given below;
The new features and what users think about it?
The Theme makeover
The new default theme is based on the Symfony2 framework. PrestaShop in version 1.7 has discontinued the Bootstrap and smarty based default theme. It also means that the old 1.6 themes are not going to work with the new version. So, users thinking about an upgrade from 1.6 to 1.7 would have to consider purchasing a new theme compatible with PrestaShop 1.7’s Symfony2 framework.
There is also a starter theme available separately which designers can use as a base to create new themes in relatively quicker time. So, it’s good for developers that they have got some backup from the platform itself.
Xavier Borderie is documentation manager at PrestaShop. In Xavier Borderie’s words:
“If you want to upgrade from 1.6 to 1.7, you will have to:
– Have the theme rewritten
– Have the modules updated (the vast majority will work as-is, with only a need to adapt the CSS code)
– Test your overrides thoroughly.”
PrestaShop says that most of the 1.6 modules will work on the new version with little or no change. Well, that does not seem so, we had to make our every 1.6 module compatible with the new version by making significant changes. They say that only those modules are needed to be tweaked:
– Which target the theme/front office – Because they rewrote the way themes were written in 1.6 versions.
– Which target the Product page- Because they have rebuilt the product page with Symfony2 and its Twig template engine.
– Which target the Modules page- Again because of the new frameworks included, Symfony2 and Twig template engine.
If we look at the situation, almost every module developed for 1.6 targets the front office, Product Page and Modules Page somewhere. So, users hoping to upgrade from PrestaShop 1.6 to 1.7 will face a hard time getting almost all of their modules rewritten. I don’t think anyone would go for an upgrade on their running store .
One of the PrestaShop users says this about the modules:
“70% of our 120 PrestaShop stores we support are still using PS 1.5 or older, only new shops are using PS 1.6. One concern I have with PS 1.7 is, that module developers can no longer afford to develop and support new addons for 1.7 AND 1.5/1.6 in the future”
The pain of a PrestaShop developer,
“It’s a pain for us developers, too. Consider I have a good bunch of modules using the product back office hooks, as well as override, not to mention the front display relying on current styles and templates”
Unfortunately, the new 1.7 version does not use overrides anymore. According to PrestaShop:
“Unfortunately, PrestaShop 1.7 will not use overrides anymore. The article states legacy architecture will still be usable; however, the back office’s Product and Modules page will not allow their usage. Into human language, it means all modules currently (wisely) using overrides will have to drop the system in future 1.7 versions” – FAQ PrestaShop
It means simply means that developers have one more reason to rewrite their modules which use overrides. This also means that module developers will have to edit the core directly as they cannot override now.
El Patron, a PrestaShop user, says:
“For me, overrides were nice, but the typical PS functions one wanted to manipulate could be hundreds of lines long and were never broken down into parts that made overriding a very safe proposition. This made it ‘nearly’ impossible to do anything meaningful in the product class, for example.
PrestaShop indicates it will take ‘requests’ and possibly include case for override in next 1.7 version. That will be an interesting path to follow.”
The new Back-office
The new look of back-office is pretty good. I must say that it’s clean and user-friendly. The modules page is a completely changed interface with an App store like view. It’s connected with the PrestaShop official marketplace which features the modules from the marketplace on the modules page. Overall, the module page is better in 1.7 than the older version.
It seems that users with the older version of PrestaShop have hardly done the upgrade. As even PrestaShop suggests, if you are running your store on PrestaShop 1.6.x or older versions, you should not consider upgrading yet. PrestaShop 1.7 is still young and has a lot to improve in the future. Till 1.6 versions are being supported by the PrestaShop, it better to stick with it for a while. However, the new website owners can start their shop with the new version.
Author Bio: Ethan Roy, a technical content writer by Profession. With years of experience on various eCommerce platforms (Magento, PrestaShop, OpenCart, Shopify), he has a lot to share with the readers. Currently working as Technical Content Writer at Knowband.