PHP version mismatch
The host moved to PHP 8.2 or 8.3 and an older extension still calls removed functionality. The site can look fine until one specific code path is used.
Compatibility
Something updated and something else stopped working. The only reliable way to find out what is bisecting the stack — not deactivating plugins at random on a live site.
WordPress updates are usually safe. When they are not, the failure is often a version mismatch: a plugin that declares PHP 8 support but calls a deprecated function, a page builder whose add-on is two majors behind, or two plugins competing for the same hook. The error surfaces in the feature you use least, which is why it can take a week to notice.
I reproduce on a copy of the site, bisect the stack in halves, and read the stack trace from the fatal. Then the fix is one of four things: patch, pin, replace, or reorder. The live site only changes once the copy proves the fix.
The host moved to PHP 8.2 or 8.3 and an older extension still calls removed functionality. The site can look fine until one specific code path is used.
No release in years, no compatibility declaration, and a growing list of deprecations. Pinning it buys time; replacing it is the actual fix.
Two plugins register the same post type, hook or checkout field. The winner depends on load order, which changes with every update.
The parent theme updated its templates while the child theme overrides an old copy. The override wins and the new markup never arrives.
A real copy with the same PHP version and data. Live visitors are not the test environment.
Half the plugins off, test, narrow. Usually a handful of requests instead of an afternoon of guessing.
The fatal names the file and line. That points at the component and often at the exact incompatibility.
Whichever option is cheapest to maintain for this site — not the one that is easiest to sell.
The broken feature, the surrounding pages and admin screens. Then update live with a rollback point ready.
For diagnosis I prefer a copy. If the site is already broken and the host will not allow staging, I can work live with a snapshot and a short maintenance window — but that risk is yours to accept, and I will say so plainly.
No. Skipping updates is how sites get hacked. The answer is updating on a copy first, with a rollback and a short test checklist.
I will not install or distribute them. If a nulled plugin is the cause, I replace it with a licensed equivalent or remove the feature. Pirated code is a common source of backdoors.
That is a postponement. The old PHP branch stops receiving security fixes and the incompatible code is still there. The durable fix is updating or replacing the extension.
Plugin & update conflicts
A short diagnosis is free. If the fault is outside this service, you will be told which one applies — or that the site is not worth repairing.
Or email hello@wordpressfixe.com — first reply within 1 business day.