Decide which kind of failure you have
Failures in a plugin-heavy site fall into a few families, and each has a different safe first step. A fatal error or blank page is a code failure. A feature that fails while the page loads is often a conflict. A form that says "sent" with no email is a sending problem. A post that publishes late is a scheduling problem. Members seeing the wrong content is an access and caching problem. A plugin that fails only on a newer PHP version is a compatibility problem. Naming the family first stops you trying the wrong fix.
- Fatal error: critical-error job.
- Feature fails: conflict isolation.
- Email missing: sending path.
- Late publishing: scheduler.
- Wrong access: access matrix and caches.
- New PHP version: compatibility scan.
Work on a copy, change one thing at a time
WordPress documentation describes finding a conflict by deactivating plugins one at a time, and recommends a backup before updates. A staging copy turns that from a risk into a test. Record every run: what was active, what you tried, what happened. Remember that must-use plugins and host-installed drop-ins keep running when you deactivate ordinary plugins.
- Match the copy's PHP version and caches to live.
- Turn off outgoing email on the copy.
Plugins declare minimums, not guarantees
A plugin's header states the lowest WordPress and PHP versions it needs. It does not say which newer versions it was tested on, and an abandoned plugin keeps its old header forever. When a host announces a PHP retirement date, find out which plugins have had no release for a long time; they are the likely blockers.
- Check each plugin's last release date.
- Ask which plugins are essential before deciding to patch or replace.
Paid options for this platform
Bounded jobs here cover one failing feature (published test price from GBP 245), form sending for up to three forms (GBP 175), one plugin on a newer PHP version (from GBP 295), members-only access (from GBP 395) and scheduled tasks (GBP 195). Standing services test updates on a private staging copy (GBP 145 a month, up to twenty updates) and check forms monthly (GBP 95 a month). Network installs are quoted separately. All prices are untested proposals and payment follows the agreed checks and sign-off.
- Pick the family first, then the job.
Sources and limits
- WordPress documentation: Manage Plugins Checked 2026-10-11.
- Deactivating plugins one at a time is a documented way to find a conflict, a current backup should exist before updating, and must-use plugins cannot be disabled from the plugins screen.
- WordPress plugin handbook: header requirements Checked 2026-10-11.
- A plugin declares its minimum WordPress and PHP versions in its header.