Available for projects & agency overflow · Quick reply, from the person who does the work

WhatsApp contact@allaux.fr
FR EN TR
allaux.
Emergency Discuss my project

Technical guides

Twenty-one procedures written to be followed, not merely read. Each starts from a definite task — back up before working, enable debug mode, read an error log, prepare a major upgrade — and gives the steps in order, with what to check at each one.

Who these guides are for

This section is not for someone still hunting the cause of a failure: the problems section starts from the symptom for that. Here you already know what you want to do. Create a child theme before touching the design, enable debug mode to see the message the site is hiding, prepare a migration without losing rankings, or simply clear the right cache.

The typical reader is a technical merchant, an e-commerce manager, or a developer meeting a platform they don't use every day. The guides assume access to the shop admin, and some assume file access over SFTP or access to the hosting panel. Where that is the case, it is stated at the top, before you have lost ten minutes.

How the section is organised

The twenty-one guides read in groups. Before working: back up the shop, enable debug mode on PrestaShop, enable it on WordPress, set file permissions on the server. Observe: read PrestaShop error logs, read WooCommerce ones, diagnose a slow shop. Routine upkeep: clear the PrestaShop cache, clear the WordPress cache.

Customise without breaking: create a WordPress child theme, understand PrestaShop hooks, choose between an override and a module. Performance and search: optimise product images, migrate without losing rankings, move the site to HTTPS. Infrastructure and updates: prepare a major update, choose e-commerce hosting, secure a shop after a hack. Connect: configure a PrestaShop carrier, configure a payment webhook, connect a product feed.

The order to take them in

Almost every intervention follows the same order, and keeping to it avoids most accidents. Back up first: files and database together, because restoring one without the other yields an inconsistent shop. Make the error visible next, by turning on development mode — on PrestaShop, the _PS_MODE_DEV_ constant in config/defines.inc.php; on WordPress, WP_DEBUG and WP_DEBUG_LOG in wp-config.php, which writes to wp-content/debug.log.

Then read what the site actually says, before forming any hypothesis. Then fix, one thing at a time: two simultaneous changes make it impossible to know which one worked. Then close up — turn debug mode off in production, because it prints file paths and query fragments that have no business being shown to a visitor.

The guides assume that discipline rather than repeating it on every page. If you read only one before working, read the one on backups.

The four most used guides

Frequently asked questions

How is this different from the problems section?
The problems section starts from a symptom and looks for the cause. The guides start from a decided task and give the steps. In practice you move between the two: the diagnostic page names the subject, the guide explains how to handle it.
Can I follow these procedures without being a developer?
Most of them, yes, provided you have the necessary access and don't skip the backup step. Guides that need real technical skill say so at the top rather than letting you find out halfway through.
Do the procedures depend on my PrestaShop or WordPress version?
Sometimes. File paths and admin screens change between major versions. The guides state the reference version used and flag the differences where they matter, particularly between PrestaShop 1.7, 8 and 9.
What if the procedure doesn't give the stated result?
Stop rather than pressing on. A gap between what the guide describes and what you see nearly always signals a configuration difference — an extension intercepting, an unusual host, an older version — and carrying on blind turns a gap into a failure.