Creating a staging environment for your PrestaShop store is the most effective way to ensure that a new module or a version update doesn’t “break” your business. In April 2026, PrestaShop remains a complex engine where a single database mismatch can cause a checkout failure.
By following this workflow on your mybox server, you can create a safe “sandbox” to test everything from tax changes to design overhauls.
Table of Contents
The Pre-Flight Checklist
Before you begin, ensure you have the following:
- Current Backups: Never start a migration without a fresh backup of your production files and database.
- Server Space: Ensure your mybox plan has enough disk space to hold a full clone of your store.
- Database Credentials: You will need to create a new, empty database in your mybox panel before starting Step 3.
Step-by-Step Staging Setup for PrestaShop
1. Subdomain Creation
Log in to your mybox panel and create a subdomain, such as test-store.yourdomain.ro. Point this subdomain to a new, empty folder on your server (e.g., /public_html/staging).
2. File Duplication
Use an FTP client (like FileZilla) to copy all files from your main directory to the staging folder.
3. Database Cloning
- Open phpMyAdmin and export your live database.
- Create a new database and a new user in your hosting panel.
- Import the SQL file into the new database.
4. Linking the Staging Site to the Staging Database
You must tell the staging files to look at the new database, not the production one.
- For PrestaShop 1.7 & 8.x: Edit
/app/config/parameters.php. - For older versions: Edit
/config/settings.inc.php.Update thedatabase_name,database_user, anddatabase_passwordfields.
5. Updating the Store URL
If you try to log in now, the site will redirect you back to the live store. You must change the URL in the database.
- In phpMyAdmin, go to the
ps_shop_urltable. - Change
domainanddomain_sslto your subdomain (e.g.,test-store.yourdomain.ro). - Ensure
physical_urimatches your path (usually/if using a subdomain).
6. Regenerating .htaccess and Clearing Cache
- Delete the contents of the
/var/cache/directory manually. - Log in to your PrestaShop staging back office.
- Navigate to Shop Parameters ➜ Traffic & SEO.
- Toggle Friendly URL to “No,” save, then toggle back to “Yes” and save again. This regenerates a clean
.htaccessfile for the staging environment.
Securing Your 2026 Staging Environment
To prevent Google from indexing your test store as “duplicate content” or customers accidentally placing “fake” orders:
- Password Protection: Enable HTTP Authentication (htpasswd) in your mybox panel for the staging folder. This is the only 100% effective way to block bots.
- Maintenance Mode: Go to Shop Parameters ➜ General ➜ Maintenance and enable it, adding your personal IP to the whitelist so only you can see the frontend.
- Robots.txt: Ensure your staging
robots.txtcontains:PlaintextUser-agent: * Disallow: /
Summary: Staging Management on mybox
| Task | Production (Live) | Staging (Test) |
| Debug Mode | OFF (for security/speed) | ON (to catch errors) |
| Caching | ON (LiteSpeed/Memcached) | OFF (to see changes instantly) |
| Indexing | Public | Private (Blocked) |
| Active | Disabled (to prevent test emails to customers) |