Prestashop Staging

  1. Staging Subdomain e.g. dev.shop.de
  2. Set PHP version same as prod
  3. Staging DB
  4. Delete files from shop/var/cache/prod or dev or _PS_ENV_/prod or _PS_ENV_/dev
  5. Copy files from shop prod to shop staging e.g. via web ftp
  6. Export DB prod via PHPMyAdmin utf-8, SQL
  7. Import DB prod to DB stage
  8. Double check, delete files from shop_staging/var/cache/prod or dev or _PS_ENV_/prod or _PS_ENV_/dev

Update Config Files in staging files

shop_dev/app/config/parameters.php
change database_name, database_user, database_password

Update SQL Tables in staging DB

UPDATE xyz_configuration
SET value = 'dev.shop.de'
WHERE name IN ('PS_SHOP_DOMAIN', 'PS_SHOP_DOMAIN_SSL');

UPDATE xyz_shop_url
SET domain = 'dev.shop.de',
    domain_ssl = 'dev.shop.de',
    physical_uri = '/'
WHERE id_shop = 1;

Update .htaccess in staging files

Search and replace

RewriteCond %{HTTP_HOST} ^shop.de$

with

RewriteCond %{HTTP_HOST} ^(shop\.de|dev\.shop\.de)$

PrestaShop 1.7.6.4 Admin Panel 500 error

Issue 1 happened during an update from version 1.7.6.4 to the latest stable one.

After the DB restore, the shop itself run well, but the admin backend run into an error

prestashop FileLocatorFileNotFoundException

solution: download and install the 1.7.6.4 version and copy the src directory from the fresh one, renamed first and deleter afterwards the corrupt one.

Issue 2

Upgrade of modules was not possible: classes/../tools/pear/PEAR.php): failed

solution: removed blockrss module and replaced other corrupted modules which run into the same issues from modules of fresh installation

Prestashop Upgrade Step by Step

Step 1 – Install 1 Click Upgrade module

Step 2 – backup FTP content and database

Step 3 – set the shop into maintenance mode via 1-Click-Upgrade

Step 4 – Start the upgrade

take into account, the module backups it initially
then the copy process starts

Step 5 – Final check after successful upgrade

please act accordingly to last tasks shown in the blue screen

xt:Commerce – Aenderung eines Serverpfades

IST:

Das CMS ist in einem Verzeichnis auf dem Server installiert (bspw. /shop) und ist lauffähig

SOLL:

Das Verzeichnis soll mit minimaler Downtime des CMS umbenannt werden.

Antwort:

  1. Umbenennung des Ordners via FTP-Client
  2. Umlenkung der Domain bzw. der Subdomain auf das neue Verzeichnis

Hinweise:

  • Keine Ă„nderungen im CMS erforderlich
  • Downtime beträgt einige Sekunden, bis die Umlenkung abgeschlossen ist