✓ No commitment · ⚡ Reply within 24 h · 📞 06 78 85 05 63
🚨 White screen · Immediate diagnostic

PrestaShop white screen?
we restore your store without touching your data.

Diagnostic and resolution of PrestaShop white screens

A fully blank page — no error, no 500, just emptiness — is almost always a silent PHP fatal error. We enable debug, read the real error, neutralise the culprit (module, override, hook) and restore your store without losing a single order.

Or call: +33 6 78 85 05 63
✓ Zero data loss ✓ Intervention within 24 business hours ✓ From €60/h excl. VAT ✓ 30-day warranty
👀 Which type of white screen

4 scenarios we handle every week

The context in which the white screen appears already orients the diagnostic. Recognise yours.

A. Everything is white (front + admin)

Nothing responds — not the home, not product pages, not /admin-xxx. Typical cause: corrupted core file (often config/defines.inc.php or config/config.inc.php wrongly edited), error in composer.json on PS 8.x/9.x, or broken autoloader. Fix: targeted restoration of the faulty file + git audit of the last diff.

B. Front white, admin OK

You can log into the back-office but the front shows white — including the homepage. Typical cause: module hook plugged onto displayHeader throwing an exception, or corrupted theme (parse error in layouts/layout-full-width.tpl). Fix: switch to default classic theme via SQL, identify the problematic module.

C. Admin white, front OK

Your visitors see the store normally but you can no longer log in to the BO: white screen from /admin-xxx or after login. Typical cause: admin controller override broken after update, or module crashing on actionAdminControllerInitBefore. Fix: neutralise /override/controllers/admin/, SQL-disable recently installed modules.

D. White only on specific product pages

Home, catalogue and checkout work, but some product pages are white. Often a module that crashes when a specific attribute is present (combinations, customizations, linked accessories). Fix: identify pivot product, disable culprit hook, patch.

🩺 Diagnostic table

What the white screen tells us (or doesn't)

A few minutes in debug mode are usually enough to isolate the cause. Here's the grid we use.

Symptom observedProbable causeWhere to look
Fully white, empty source codeFatal PHP error at bootstrapphp-fpm.log + error_log
White, source = HTML layout without contentdisplayHeader or actionDispatcher hook throwingDebug mode + recent module
White, but view-source: shows raw SmartyCorrupted Smarty cache, template parse error/var/cache/prod/smarty/
White only after admin loginBroken admin override / faulty BO module/override/controllers/admin/
White + Class not found logBroken autoloader, file renamed/removedOverride + composer autoload
White + Cannot redeclare logOverride / module redefining a class/override/classes/
💰 Pricing

Pricing stated up-front

Free diagnostic. For the intervention, you know exactly what it costs before we touch the code.

🔍 Diagnostic

Diagnostic

see the hidden error
0€free
30 min · no commitment
  • PrestaShop debug mode temporarily enabled
  • Faulty module / override identified
  • Firm quote sent immediately
  • You decide if we continue
Start the diagnostic →
⚡ Most requested🔧 Intervention

Targeted intervention

restore the store
from 60€excl. VAT
per diagnostic · price stated up-front
  • Files + DB backup before intervention
  • Neutralisation of faulty module / override
  • Debug disabled, Smarty cache cleared, prod tests
  • Written report: cause + applied fix
  • 30-day warranty on the fix
🛡️ Maintenance

Monthly maintenance

pre-prod tests before every update
from 50€/ month
24/7 monitoring · no commitment
  • Module audit before every major update
  • Daily backups externalised (S3 / Backblaze)
  • Priority intervention on white screens
  • Override watch + porting on every update
❓ FAQ

PrestaShop white screen — frequently asked questions

A white screen means the server returned HTTP 200 OK but with an empty body. It's typically a silent PHP fatal error: display_errors is off in production, so PHP swallows the error and Smarty renders an empty template. Common causes: class override throwing at bootstrap, module hook crashing during theme load, wrongly edited defines_custom.inc.php, corrupted Smarty cache.
A 500 is shown by Apache/Nginx with an explicit message. A white screen is HTTP 200 OK with empty body: PHP crashed but the error was masked. Diagnostic tools differ: for a white screen we must manually re-enable PrestaShop debug mode.
Classic case of broken admin controller override or BO-only module crash. We access via SSH/FTP, temporarily disable /override/controllers/admin/ by renaming, test, isolate. If unresolved, SQL-disable recently installed modules. Resolution 30-60 min.
Very common, rarely serious in terms of data. A 1.7→8 or 8.x→9 update rewrites many core classes: your overrides may reference disappeared methods. Old modules that didn't follow either. Fix: neutralise /override/, port overrides, audit modules. Orders, customers, catalogue remain intact.
Free diagnostic (30 min) then intervention on quote, from €60/h excl. VAT. Most white screens resolved in 1-2 hours once identified. Firm quote within 24 business hours. Included in Business/Performance maintenance.
On 1.7+, edit /config/defines.inc.php: define('_PS_MODE_DEV_', true);. On 8.x/9.x, use /app/config/parameters.php. NEVER leave active in production (exposes server paths and sensitive data). Enable 5 min, read error, disable, fix.

Your store is white right now?

Free diagnostic in 30 min. Firm quote within 24 business hours, intervention from €60/h excl. VAT. No surprises.

📞 +33 6 78 85 05 63
📞 Call · 06 78 85 05 63