E-commerce · 2026
PrestaShop 1.7.6 to 9.2 upgrade
A PrestaShop 1.7.6 store with old payment modules, a child theme, an override and custom code, upgraded to 9.2 step by step and tested after every step, including everything the official upgrade tool did not report.
Read the full write-up ↗
- Client
- Moonivo (test store we built)
- Services
- PrestaShop upgrade, Module and theme fixes, Testing
- Technology
- PrestaShop 1.7.6 → 8.2 → 9.2 PHP 7.1 → 8.1 Mollie PayPal Child theme Overrides Automated browser tests
- Path
- 1.7.6.7 → 8.2.8 → 9.2.0, PHP 7.1 → 7.2 → 8.1
- Store
- Mollie, PayPal, reviews, wishlist, analytics, a child theme, an override and a custom module
- Testing
- Product page, cart, guest checkout, order and back office after every step
- Found
- Silent failures the upgrade tool did not report, from disabled payments to unsaved GDPR consents
- Result
- Every page and the full order flow working on PrestaShop 9.2, no console errors
The challenge
Most stores still on PrestaShop 1.7 are not plain installs. They have payment modules from years ago, a customised theme, an override or two and some code an agency wrote for them. The official upgrade tool moves the core in minutes, but it cannot tell whether those parts still work. We wanted to show, on a store we could publish, what that gap looks like and how we close it.
We built a PrestaShop 1.7.6.7 store the way such stores usually look: Mollie and PayPal versions from 2020, product reviews, a wishlist and analytics, a child theme with its own product page block, an override that adds a delivery date, and a custom module written with the habits of that time.
What we did
- Checked the store before touching it with our readiness check: the modules, the theme, the override and the server.
- Planned the path: PHP 7.2 first (the current upgrade tool does not run on 7.1), then 1.7.6 → 8.2, PHP 8.1, and 8.2 → 9.2.
- Upgraded on a copy with the official tool and kept a full backup of every step.
- Ran the same automated browser test after every step: every custom block on the product page, the cart, a guest checkout, the order confirmation and the main back-office pages.
- Fixed what broke: payment modules that the upgrade had silently disabled, trust icons returning 404 on every page, a combination name that went empty without an error, a module endpoint that returned error 500 and then 403, and an override that would have taken down every product page on 9.
- Rewrote the custom module once so that the same code runs on PrestaShop 8 and 9, with a small upgrade script for its saved settings.
- Kept PayPal when the upgrade tool offered to uninstall it: its own changelog lists PrestaShop 9 support, and it works on 9.2.
- Checked the result again and found what no upgrade report mentioned: the official GDPR module no longer saved customer consent on 9.2, and payment module code still called removed functions.
The result
The store runs on PrestaShop 9.2 and PHP 8.1 with every page, the full order flow and the back office working and no errors in the browser console. Each problem is written down with its cause and fix, and the same checks now run on every upgrade we do.
We also used the test on our own tool: it showed where our free readiness check missed a call and where it raised false alarms, and both were fixed the same day.
