PrestaShop 1.7.8.6 to 8+: Your Expert Guide to a Seamless Upgrade
As e-commerce experts at Migrate My Shop, we frequently encounter merchants grappling with the complexities of platform upgrades. A recent PrestaShop forum thread perfectly illustrates a common, yet critical, scenario: upgrading PrestaShop 1.7.8.6 to a newer version, specifically PrestaShop 8+, driven by urgent PHP security vulnerabilities (CVE-2026-109618 and CVE-2026-109619) affecting PHP 7.4.
MaxV2019's struggle to upgrade, encountering errors like "can't delete folders," "server not responding," and a perplexing missing api_public_key, resonates with many. This guide distills expert advice from the community, offering a comprehensive roadmap to navigate your PrestaShop upgrade successfully.
Before diving into the PrestaShop core, let's address the foundational issue:
Prioritizing PHP Security: A Critical First Step
It's crucial to understand that upgrading PrestaShop itself does not patch vulnerabilities in your underlying PHP version. As Fred at PrestaHeroes rightly pointed out, PHP 7.4 is end-of-life and affected by critical security flaws. Your immediate action should be:
- Contact Your Hosting Provider: Inquire if your current PHP 7.4 build includes backported security patches for CVE-2026-109618 and CVE-2026-109619. Some providers offer this as a temporary measure.
- Plan for a Supported PHP Version: Ultimately, you must migrate to a fully supported and patched PHP version. For PrestaShop 8 and 9, this means PHP 8.1, 8.2, or 8.3, with specific patched releases like PHP 8.2.35+, 8.3.36+, or 8.5.12+ for PrestaShop 9.2.
Perform all PrestaShop upgrades in a restricted development environment, never directly on your live production store.
Unpacking MaxV2019's Upgrade Hurdles: Solutions to Common Errors
MaxV2019's experience highlights several common upgrade blockers. Let's break them down:
1. The Missing api_public_key and api_private_key
This was the primary technical wall MaxV2019 hit. These parameters were introduced with the new Admin API in PrestaShop 8.1. PrestaShop 1.7 doesn't use them, and the upgrade tool is supposed to generate them automatically during the 8.1 transition.
According to Prestachamps, the most common reasons for this failure are:
-
Outdated Upgrade Module: The PrestaShop
autoupgrade(or "Upgrade assistant") module's 4.x builds don't generate these keys. The auto-generation feature landed in version 5.x.Solution: Download the latest release of the autoupgrade module directly from PrestaShop's GitHub and install it. This usually resolves the parameter error.
-
OpenSSL Not Available: The keys are genuine RSA keys, requiring OpenSSL. If the PHP CLI environment running the upgrade has OpenSSL disabled, key generation fails silently.
Solution: Check your PHP CLI configuration. Run
to confirm OpenSSL is enabled for the PHP binary used by your CLI. If not, enable it or use a PHP version where it's active.php -m | grep -i openssl -
Manual Seeding (Temporary Fix): If immediate action is needed, you can manually copy these two lines from a fresh PrestaShop 8.1+
app/config/parameters.phpfile or generate your own RSA key pair using OpenSSL and paste them into your existingparameters.php. However, fixing the module version is the recommended long-term solution.
2. "Server Not Responding"
This typically occurs during web-based upgrades when PHP's max_execution_time or memory_limit is exceeded. The upgrade process is resource-intensive.
Solution: Switch to the CLI (Command Line Interface) for upgrades. Ensure your CLI PHP configuration has a generous memory_limit (e.g., 1536M) and a sufficient max_execution_time or disable it for CLI scripts.
3. "Can't Delete Folders"
This error points to file-lock or ownership issues during the backup-and-swap phase of the upgrade.
Solution:
- Clear Opcache: Ensure your PHP opcache is cleared before starting the upgrade.
- File Permissions: Make sure the entire shop directory tree is writable by the PHP user. Incorrect file permissions are a frequent cause of this issue.
- Windows Hosting: If on Windows hosting, this symptom is common due to how Windows handles file locks.
Choosing Your Upgrade Path: Staged In-Place vs. Fresh Installation
Once the immediate technical blockers are understood, the strategic question arises: how best to approach the upgrade? The community offered two primary, expert-backed strategies.
1. The Staged In-Place Upgrade
This method involves upgrading your existing shop incrementally, version by version. It's often considered the "normal path" for same-platform upgrades, as confirmed by Prestachamps.
Fred at PrestaHeroes outlined a robust staged route:
- Rigorous Backups: Before *each* stage, create a full backup of your files and database. Perform all upgrades on a separate development copy of your shop.
- Module & Theme Management: Disable all third-party modules and switch to the PrestaShop default theme (e.g., Classic or Hummingbird). Treat existing themes and modules as incompatible until proven otherwise. Re-enable/update them only after the core upgrade is stable.
-
Incremental Upgrades:
- Upgrade PrestaShop 1.7.8.6 to 1.7.8.11 (keeping PHP 7.4).
- Backup the working 1.7.8.11 shop.
- Upgrade to PrestaShop 8.2.8 (keeping PHP 7.4 during the upgrade, then switch to PHP 8.1, clear cache, and test).
- Backup the working 8.2.8 shop.
- Upgrade to PrestaShop 9.2.0 (keeping PHP 8.1 during the upgrade, then switch to a fully patched PHP 8.5.12+).
- Post-Upgrade: Once you reach the target version, install compatible versions of your theme and third-party modules. Enable them individually, testing critical functionalities like payments, shipping, and checkout at each step.
This approach, while potentially lengthy, allows for granular troubleshooting and ensures you're building upon a stable foundation at each step.
2. The Fresh Installation & Data Migration
Fred at PrestaHeroes strongly advocates for this approach, especially for major version changes or when the existing installation is burdened by years of accumulated files, overrides, and unused modules. This method offers a clean slate.
The process typically involves:
- New Installation: Set up a fresh installation of your target PrestaShop version (e.g., 9.2.0) on a development subdomain with a compatible, patched PHP version.
- Data Migration: Use a reliable migration tool (Fred recommends Migration Pro) to transfer essential PrestaShop data: products, categories, customers, orders, etc. Data from third-party modules may require separate consideration.
- Build & Configure: Install your compatible custom theme (or use Hummingbird) and current versions of necessary modules. Reconfigure all module settings from scratch.
- Thorough Testing: Configure and test the new shop extensively on the development subdomain while your existing shop continues trading.
-
Final Cutover:
- Backup both shops.
- Put the production shop into maintenance mode.
- Perform a final data resynchronization to capture recent changes.
- Move the old production shop to an archive subdomain.
- Clear the production document root and move the new shop into place.
- Update domain settings, check SSL, clear cache, regenerate rewrite rules.
- Confirm correct PHP version and conduct final tests before reopening.
While this route means rebuilding module configurations and reconciling URLs, it provides a much cleaner codebase, avoids carrying over legacy issues, and offers greater predictability for the go-live phase.
Key Takeaways for a Successful PrestaShop Upgrade
- Backup, Backup, Backup: This cannot be stressed enough. Full file and database backups before *every* significant step are non-negotiable.
- Development Environment: Always perform upgrades on a separate, isolated copy of your shop.
- PHP First: Address PHP security and compatibility before attempting any PrestaShop core upgrade.
- Module & Theme Discipline: Disable third-party elements during core upgrades. Only reintroduce compatible versions after the core is stable.
- Understand Errors: Common errors like missing API keys, server timeouts, or file permission issues often have specific, actionable solutions.
- Consider Professional Help: For complex shops, or if you're unsure, engaging an experienced PrestaShop developer or migration expert can save significant time, stress, and potential data loss.
Upgrading PrestaShop, especially across major versions, requires careful planning and execution. By understanding the common pitfalls and applying these expert strategies, you can ensure a smooth transition to a more secure and feature-rich PrestaShop environment.
Need expert assistance with your PrestaShop migration or upgrade? Don't risk your e-commerce business. Contact Migrate My Shop today for a seamless and secure transition.