wp-admin broken
The site looks fine to the world. The cockpit is on fire.
A broken wp-admin is a strange emergency: customers see nothing wrong, but you can't post, update, fulfill, or fix anything. The dashboard breaks separately from the site because it runs more code — and repairs separately for the same reason.
Same-day diagnosis. Flat quote before any fix.
What’s actually happening
wp-admin loads a different, heavier codebase than your public pages: every plugin's admin screens, editors, cron tasks, and update machinery. A fault in that admin-only layer — a settings screen fataling, an editor script conflict, an admin-side memory blowout — breaks the cockpit while leaving the storefront untouched.
That separation is diagnostic gold: whatever broke lives in the admin-only set — plugin dashboards, editor extensions, admin themes — which is a far shorter suspect list than 'the whole site.' Blank admin, half-styled admin (bare links, no CSS), and erroring admin each narrow it further.
The usual causes, ranked
After twenty-seven years of these calls, the odds are well mapped. Start at the top.
An admin-screen fatal in a plugin
A plugin's settings or dashboard page fatals on load — sometimes taking all of wp-admin with it. The everyday leading cause.
Admin-side memory exhaustion
The heavier admin codebase crosses the memory budget the lighter front end fits within. The 'why only admin?' classic.
Editor and script conflicts
Block editor extensions, builder admin scripts, and jQuery-era plugins colliding — a half-working dashboard with dead buttons and spinning panels.
The unstyled-admin cache/proxy quirk
Admin rendering as bare links means its CSS is being blocked or mangled — a cache, proxy, or security rule applied where it shouldn't be.
What you can safely try first
Nothing below can make things worse — that’s the selection criterion. Anything riskier belongs in professional hands, on a backup.
- 1
Note the exact flavor
Blank? Erroring with text? Styled but broken? Unstyled entirely? Each flavor is a different suspect list, and the flavor is free information.
- 2
Check your email for the fatal-error notice
WordPress mails the admin when it catches an admin fatal, naming the plugin. That email is the diagnosis, gift-wrapped.
- 3
Try one specific admin page directly
If the dashboard home dies but /wp-admin/edit.php loads, the fault is on the dashboard's widgets — a narrower hunt than 'admin is broken.'
Stop and call when…
- No error email arrived and the admin is fully blank — log-reading territory
- You need the store fulfilling orders today and can't reach them
- The fix requires disabling plugins without a working dashboard — doable properly, but not a first-timer's afternoon
From there it’s our job: same-day look, flat quote, and the $229 flat repair covers most cases of exactly this.
Single Error Fix — buy it now, skip the hunt.
One error, hunted down and fixed — 500s, white screens, redirect loops, broken pages.
Covers one specific error or broken behavior on one site. Diagnosis, the fix, and a plain-English note on what happened. If we can't fix it, you get a full refund.
Questions we hear a lot.
How do you fix admin if admin is what's broken?
The dashboard is one door, not the only one: the fault isolates and repairs from the server side — logs name the failing file, the culprit gets paused without the UI, and admin comes back. That out-of-band work is exactly what the flat fix covers.
Why does everything work except the admin?
Because admin runs code the front end never loads. Your public pages exercise maybe a fifth of the installed machinery; wp-admin exercises all of it. Faults in that admin-only majority break the cockpit invisibly.
Is a broken admin urgent if the site looks fine?
Quietly, yes: you can't update (security debt accrues daily), can't publish, can't fulfill — and whatever broke admin often reaches the front end at the next update. It's the calm-looking emergency, best fixed before it stops being calm.
Related symptoms & help
Errors travel in packs. If this one visited, check its friends.
Cockpit fires, put out same-day.
Send the symptom, get a same-day look and a flat quote from the developer who's fixed this exact thing more times than either of us can count.