Fix · Emergency
CMS & Website Support: Fixing Bugs, Broken Updates and Migrations
Your website or online store is down, throwing a critical error, or broke right after an update — and you need it working again, not a rebuild. We step into your existing CMS (WordPress, Drupal, PrestaShop, Magento, Shopify and others), isolate exactly which layer is failing — theme, plugin or module, core, database or hosting — and fix the actual cause. Remote, worldwide, billed by the half-hour with no subscription, and a reply within two business hours.
Situations we're called in for
- Your site shows a white screen or a "critical error" and the admin dashboard is unreachable.
- An automatic plugin, theme or core update broke the layout, checkout or a key feature.
- A plugin or module conflict appeared after you added or updated something, and now pages error out.
- Your online store's cart, payment or checkout suddenly stopped working before a busy period.
- The site is painfully slow or times out, and you can't tell if it's the CMS, the database or the server.
- You inherited a site from a previous agency or freelancer who has disappeared, with no documentation and no admin access.
- You need to migrate or take over a CMS site to new hosting or a new domain without losing content or SEO.
- You suspect the site was hacked, is redirecting visitors, or is flagged as unsafe, and you need it cleaned and secured.
- The database is corrupted, out of sync, or throwing "error establishing a database connection".
- Your staging and production environments have drifted apart and a deployment overwrote live changes.
How we diagnose it, in order
- We reproduce the exact failure and read the real error: server logs, PHP error log, and the CMS debug output (for example WordPress WP_DEBUG, a PrestaShop or Magento exception, a Drupal watchdog entry) instead of guessing from the front-end symptom.
- We separate the layers fast: is it the theme, a plugin/module, the CMS core, the database, or the hosting/server? A quick controlled test — reverting to a default theme, selectively disabling extensions, or checking a clean core file — usually tells us within the first session.
- We confirm the environment: PHP version, memory limits, disk and database quotas, file permissions, and recent host changes. A lot of "the CMS broke" cases are really the application failing on a server that itself is fine — the kind of split we handle daily from hosting-support experience.
- We fix the root cause, not the symptom: resolve the conflict, patch or roll back the offending extension, repair or reconnect the database, correct the update path, and re-test the exact flow that was failing (checkout, login, form, media upload).
- For migrations and takeovers, we inventory files, database and DNS first, move everything on a safe copy, verify URLs, SSL, redirects and search-engine indexing, then cut over so you don't lose content or rankings.
- We hand back a short, plain explanation of what was wrong and what we changed, plus the concrete steps to avoid it recurring — backups, update discipline, or a staging step.
Technologies & environments — examples, not a limit
Don't see your CMS or setup here? This isn't a compatibility checklist. Tell us the problem and describe your environment, and we'll confirm quickly whether we can take it on — in most cases we can, because we work from the problem down through the layers, not from a fixed list of tools.
Frequently asked questions
My WordPress site shows "There has been a critical error on this website" — can you fix it?
Yes. That message hides the real error, so the first step is to read the actual PHP or debug log to find the failing plugin, theme or core file. Once identified, we disable, patch or roll back the culprit and restore access to your dashboard. It's usually resolved quickly once the true cause is visible.
My site broke right after an update. Can you roll it back?
In most cases, yes. We identify which update caused the break, then either roll that component back to a working version or fix the incompatibility directly. Where a full rollback risks data loss, we repair forward instead so you keep recent content and orders.
The previous developer disappeared and I have no admin access. Can you still help?
Yes — this is one of the most common situations we handle. With hosting or FTP access we can regain control of a site even without the original admin login or documentation, then diagnose and take over maintenance from there.
Do you charge a monthly retainer?
No. There's no subscription. You're billed in 30-minute increments for the time the work actually takes, so a small fix costs a small amount and you're never locked into an ongoing plan.
Can you migrate or move my CMS site without losing SEO?
Yes. We migrate files, database and configuration on a safe copy, then verify URLs, redirects, SSL and search-engine indexing before cutover. Done in that order, your content and rankings are preserved.
How fast can you start?
We reply within two business hours and work remotely, worldwide. For an outage we can typically begin diagnosis in the same session once we have access, since the first goal is to read the real error and isolate the failing layer.
Tell us what's broken and describe your environment. We'll confirm we can take it on and start with a clear diagnosis — no subscription, billed by the half-hour, reply within two business hours.
Besoin d'une intervention ciblée ?
Décrivez le blocage — devis sans engagement, ou rappel sous 2 h ouvrées. Supplément urgence possible (+40€).