Pavol Rašev
Available for remote contracts from December
Blog

Upgrading PrestaShop 1.7 to 8 or 9: what breaks and how to find out early

Upgrade 1.7 to 8 first, and treat 9 as a second, separate step: no PHP version runs both 1.7.8 and 9. The core upgrade is the easy part. What breaks are the modules, overrides and leftovers around it, and most of them fail quietly, so you find them on a copy of the store, not on the live one.

PrestaShop 1.7 to 9 in two trips PrestaShop 1.7.8 runs on PHP 7.1 to 7.4 and upgrades to 8.2 on PHP 7.4. After switching the server to PHP 8.1, 8.2 upgrades to 9, which needs PHP 8.1 or newer. No PHP version runs both 1.7.8 and 9, so the direct jump is crossed out. PrestaShop 1.7 to 9, in two trips The PHP version decides the path, not PrestaShop on PHP 7.4 on PHP 8.1+ 1.7.8 PHP 7.1 to 7.4 Symfony 3.4 8.2 PHP 7.2.5 to 8.1 switch PHP here 9 PHP 8.1 and newer Symfony 6.4 no PHP version runs both 1.7.8 and 9 pavolrasev.com

In a PrestaShop upgrade, the core itself rarely fails. That is the pattern I keep seeing. The core upgrade is a script that has been run thousands of times, and it mostly works. What hurts is everything around it: the modules, the overrides, the PHP version jump, and the copies you make to be safe.

The path is decided by PHP

PrestaShop 1.7 has been in security-only “extended support” since 8.0 came out in October 2022, and PrestaShop said that support would end when 9.0 was released. 9.0 was released on 10 June 2025. If you are still on 1.7 in late 2026, you are running a version nobody patches.

The first thing to look at is not PrestaShop at all. It is the PHP version your host runs, because each PrestaShop line supports a different range:

Version PHP supported Recommended Symfony
1.7.8 7.1 to 7.4 7.4 3.4
8.0 to 8.2 7.2.5 to 8.1 8.1 4.4
9.0 8.1 to 8.4 8.4 6.4
9.1 8.1 to 8.5 8.5 6.4

Look at the first and third rows. There is no PHP version that runs both 1.7.8 and 9. The Update Assistant (the official upgrade module, technical name autoupgrade, formerly “1-Click Upgrade”) says it can take any 1.7 store to a higher version, but the store has to run on a PHP version both sides understand while it does. So in practice it is two trips: 1.7.8 on PHP 7.4 up to 8.2, then switch the server to PHP 8.1 or newer, then 8.2 up to 9. I would do them weeks apart, with the store running normally in between, because each trip breaks different things.

The Symfony column matters if you have custom modules with admin pages. 1.7 to 8 moves from Symfony 3.4 to 4.4. 8 to 9 moves from 4.4 to 6.4, which is the bigger jump: admin controllers have to be services, $this->get() in a controller stops working, and Guzzle and Swift Mailer are gone from the core. A small leftover from Matrace Lema shows how quiet these changes are: the composer.lock in the store’s root still lists Symfony 3.4.49, while the vendor folder that actually runs has 4.4.51. Nobody reads that file, so nobody noticed.

What broke on a real 1.7.8 to 8.2.3 upgrade

Matrace Lema sells custom-sized mattresses. I took it to 8.2.3 at the end of January 2026, still on the bought theme it had run on 1.7. Today it has 23 override files, about 200 module folders and a set of my own modules, one of which sends every order to the company’s ERP.

The core upgrade itself took two runs of the Update Assistant. On 16 January it made a full backup of the store, then on 1.7.8.7, and moved it to 1.7.8.11. On 30 January it took it from 1.7.8.11 to 8.2.3. The log of that second run is short: from putting the store into maintenance at 18:23:04 to “Shop updated to 8.2.3” at 18:24:07 is about a minute, and the database part in the middle ran 184 queries from the upgrade files of 8.0.0 to 8.2.2.

The SQL and PHP upgrade files inside the Update Assistant, step by step from 1.7.8.0 to 8.2.2, are the best documentation of 8.0 I know of. A few things in there will matter to someone:

  • 8.0 drops the quantity and location columns from combinations, the shipping_number column from orders, the tax rule from carriers and the whole referrers feature.
  • 8.1.3 changes every product and combination with a minimum quantity of 0 to 1.
  • 8.1.7 converts 36 text columns, product descriptions among them, to MEDIUMTEXT.

If any module, export or report of yours reads one of those dropped columns with raw SQL, it fails with an “unknown column” error. That at least is loud.

The PHP side of the same change is quieter. PrestaShop 8.0 removed Order::$shipping_number, deprecated since 1.5, and the tracking number now lives on the order’s carrier record. Code written for 1.7 often still reads it like this:

if (!empty($order->shipping_number)) {
    $note = $carrierName . ' ' . $order->shipping_number;
}

On 8.x the property no longer exists, so empty() returns true and the branch never runs. No error, no log line. If a module needs the tracking number, $order->getShippingNumber() reads it from the right place.

This is why I don’t trust a module just because it installs and its settings page opens. Search the code of every module you rely on for what the 8.0 changelog removed: shipping_number, Tools::jsonEncode, Tools::jsonDecode, Combination quantity. It takes ten minutes with grep.

PHP 8 also turns notices into crashes. The blog module on the store had four small bugs. On PHP 7.4 they produced notices nobody saw. On PHP 8 one of them became TypeError: Cannot access offset of type string on string, and every tag page and archive page of the blog returned a 500. Another left the article titles on category pages empty. Google crawls those pages whether your customers visit them or not. Third-party modules written for 1.7 were written for PHP 7, and the PHP jump is what finds their bugs, not the PrestaShop one.

Then the overrides. The Update Assistant has an option to disable all overrides during the update, and its docs suggest it to avoid conflicts. On this store, one of the 23 overrides replaces PrestaShop’s URL dispatcher; it comes from a “pretty URLs” module that removes IDs from addresses, and every category and product URL in Google depends on it. Others come from a cookie consent module, a free-gift module and two captcha modules. Switching them all off is fine for the few minutes of the update, as long as you know which ones to switch back on and test right after. Before the upgrade, list them: override/classes and override/controllers tell you what each one replaces, and the comment above each method says which module put it there.

After the upgrade I kept deploying modules by uploading files. Three times a feature of mine “worked locally and not on production”, and three times the cause was the same: the files were new, but PrestaShop had never run the module’s upgrade scripts, so the hooks they register were missing. Once it was the custom size switcher on the product page, the most important widget in the store. Now, when something works on staging and not on production, the first thing I compare is the list of hooks each module is registered on, not the code.

One of the worst problems came from a copy made to be safe: a full backup of the old theme, left inside themes/, which the e-mail template module picked up as the target: it wrote the new order e-mails into the backup folder, and customers kept getting the old ones until I found out why. It isn’t a PrestaShop bug. It’s the kind of copy people make around an upgrade and then forget.

Going on to 9

I have not taken a live store from 8 to 9 yet. My PrestaShop 9 experience comes from Vlnkovo, a store I moved from Shoptet and built on 9.1 from the start, so treat this part as what I would check, not as a story.

The PHP move is forced: 9 needs 8.1 at least. The theme is the bigger question than on 8. Classic is still the default theme in 9.0, and the new Hummingbird theme is optional, but the 9.0 changes list touches templates directly. For example the manufacturer image is now an array of sizes instead of a single URL, and the category, manufacturer, supplier and store pages get their image data in a new format. A child theme of classic with few overrides survives this. A heavily customised bought theme needs its author to have shipped a 9 version, and you should check that before you plan anything.

Custom admin pages are where 9 costs real time, because of Symfony 6.4. And one thing that bit me on Vlnkovo has nothing to do with the changelog: a module that ships its own vendor folder can replace a library the core uses. Mine carried PHPUnit’s dependencies by mistake, among them a newer nikic/php-parser, and because Composer puts a module’s autoloader in front of the core’s, the back office Modules page died with Attempted to call an undefined method named "create" of class "PhpParser\ParserFactory". The stack trace blamed a different module. If a page in the back office breaks after you install or update a module, check which libraries that module bundles.

You can also see what vendors expect from 9 by reading their code. A review module on Matrace Lema ships a “PrestaShop 9 compatibility package” that re-implements Tools::displayPrice(), Tools::encrypt() and a few others. When a vendor writes that, they are telling you which calls to search for in your other modules.

The checklist I use before an upgrade

None of this needs me. It needs a copy of the store and a day.

  1. Write down the inventory. PrestaShop version, PHP version, theme (bought, child of classic or custom), every enabled non-native module with its version and author, and every file in override/. Mark the ones that touch money or URLs: payment, shipping, invoices, ERP or accounting exports, URL rewriting, redirects.
  2. Ask each module author one question: which version supports PrestaShop 8 (or 9) and PHP 8.1? No answer is an answer. Plan to replace that module.
  3. Grep your custom modules for what the changelog of the target version removed. For 8.0: shipping_number, Tools::jsonEncode, Tools::jsonDecode, combination quantity and location. For 9.0: $this->get( in admin controllers, Guzzle, Swift Mailer.
  4. Plan the PHP path. 1.7.8 upgrades on PHP 7.4. Switch to PHP 8.1 only once you are on 8.x, then run the store for a while before you think about 9. Ask your host whether you can switch PHP per site and how fast you can switch back.
  5. Make a staging copy on the same PHP version as production, with a copy of the real database, and do the full upgrade there first. Read the PHP error log, not just the pages. Notices on 7.4 are the 500 errors of 8.x.
  6. Test what earns money and what Google sees: an order with each payment method and each carrier, an order with a discount, the invoice PDF, the e-mails the customer gets, the export to your ERP or accounting, a sample of product, category and CMS URLs (they must not change), the sitemap, and the pages that only crawlers visit, like blog tags and archives.
  7. After the live upgrade, compare hook registrations between staging and production, re-enable the overrides you need, and then delete or lock the backup: it sits in {admin}/autoupgrade/backup and holds your database password and every customer’s data. Make sure it is not reachable from the web.

The store came out of this on PrestaShop 8.2.3, and once the platform was current, the work on speed and the new theme could start: mobile PageSpeed went from about 40 to over 90, which is in the case study.

If your store is still on 1.7, or you are on 8 and wondering what 9 will do to it, I can run this checklist on a copy of your store and tell you what will break before your customers find it: which modules to update, replace or drop, what the overrides do, and how long the store will be in maintenance. That usually decides whether the upgrade is a weekend or a month. The first estimate is free once I have looked at the store. Here is how a PrestaShop upgrade works with me, or send me your store’s address and the list of modules, and I will start there.

Sources