HTTP 500 / white screen
PHP fatals after a module or PHP version change.
Urgent PrestaShop support
HTTP 500, checkout down, payment gateway dead. You speak with the developer who opens the store and reproduces the fault.
Do not send passwords in the first message.
The storefront that is failing, plus back office if the admin is the issue.
HTTP status, white screen, payment message — a screenshot helps.
Module update, PHP bump, theme edit, or “nothing, it just broke”.
Can it still take orders? Since when?
If sales are down, that is the priority — not a redesign.
PHP fatals after a module or PHP version change.
Gateway timeouts, missing confirmation emails, carts that will not convert.
Admin CSS gone, login loops, or modules that crash the dashboard.
Two Addons modules fighting hooks on the same cart event.
Order mails, cron, or SPF — I isolate whether it is PrestaShop or the host.
Broken assets after a domain or certificate change.
URL, error, last change. I say if I can take it now.
Logs and a copy of the fault before I change production.
Restore service first. Then the durable fix.
What broke, what changed, what to watch. Hourly €30 + VAT.
No. Unknown faults start with diagnosis. I report what the evidence shows.
Availability varies. Send impact, URL, error and the last change so I can confirm.
Yes, when server configuration or infrastructure is involved.
No. Do not send credentials in the first message.
WhatsApp with the URL and the error. If it is not an emergency, use the quote form.