Job plugin-php-version-incompatibility-one-plugin · revised 11 October 2026
Make one WordPress plugin run cleanly on the PHP version your host is moving you to
Patch one custom or abandoned WordPress plugin so it passes an agreed PHP compatibility scan and an agreed list of functions on a staging copy at the target PHP version.
You might be seeing
- A white screen or critical error appears only after switching to the newer PHP version
- The PHP log fills with deprecation notices naming one plugin folder
- The plugin's listing says it was last tested with a much older WordPress version
- The host will not move you to the new PHP version until the plugin is dealt with
No passwords, keys, card details or admin invites needed to start.
What usually happened
Each PHP release removes or changes features. Code written for an older version can then throw deprecation notices, behave differently or fail outright. A maintained plugin ships a compatible update, but a custom or abandoned one does not, so the site stays stuck on a PHP version that is approaching the end of its security support.
Who it’s for: Owner or agency of a WordPress site that relies on one custom-built or no-longer-maintained plugin, and whose host is retiring the current PHP version.
Usually starts when: The host announces an end date for the PHP version you use, a staging test on the newer version shows warnings or a white screen from one plugin, or the plugin's author has stopped releasing updates.
The result: One named plugin passes an automated compatibility scan for the PHP version you choose, its agreed functions work on a staging copy running that version with no new PHP errors logged, and you get the patch, the scan results and steps to switch the host over and back.
Check whether this job fits
A few short questions. Your answers stay on this page unless you choose to email them.
Checks you can run yourself
Find the PHP version and the last release date
In the WordPress admin open Tools, then Site Health, then Info, and read the Server section. On the Plugins page note the plugin's version and, if it is from the directory, open its listing.
Look for: The PHP version now in use and the date of the plugin's last release. A last release years ago, or "not tested with the latest major releases", means no compatible update is likely.
Ask your host for the end date
Ask your host's support when the PHP version you use is being retired for your plan.
Look for: A date. It sets the deadline; the plugin work should finish with time to test.
What you get
- The patched plugin as files or a patch, with the changes listed
- The scan results before and after, and a list of any findings left and why
- Test results for each agreed plugin function at the target PHP version
- Switch-over and switch-back steps for your host
- A note on the replacement options
Included
- One plugin whose code we can read and are allowed to change
- A static compatibility scan of that plugin for the agreed target PHP version, with each finding explained
- Fixing the findings that matter with the smallest change, and checking the plugin's agreed functions on a staging copy at the target version
- Checking the rest of the staging site loads with the plugin active at the target version
- A note on whether a maintained replacement plugin exists
Not included
- More than one plugin, or the theme and WordPress core compatibility as a whole
- Plugins that have an update from their maker that already supports the target version: you should just install it
- Encoded or licence-locked plugin code that cannot lawfully be changed
- Rewriting the plugin's features or adding new ones
- Server changes such as installing a PHP extension, which only your host can do
- Applying the switch on the live site
How we know it’s done
Agreed with you before work starts. Each check produces evidence you keep.
The compatibility scan of the plugin folder for the agreed target PHP version reports no errors, and each remaining warning is listed with a reason
Evidence: The scan output before and after, saved with the plugin version
Each agreed plugin function succeeds on the staging copy at the target PHP version
Evidence: A step list and screenshot or output for each function
No new PHP error or deprecation message naming the plugin appears in the staging log during the test run
Evidence: Redacted log excerpt for the test window
The staging site's home page, admin login and Plugins screen load with the plugin active at the target version
Evidence: Status codes and screenshots for each
Sign-off. You sign off after the staging checks pass; your site holder then switches the PHP version and confirms the agreed functions on the live site.
If it fails. If the checks do not pass, you do not pay, and you keep the scan results and findings so anyone can continue.
When it fits, and when we stop
It fits when
- The plugin is custom-built for you, or its maker no longer releases updates
- The plugin's source is readable and you hold the right to modify it
- You can make a staging copy that can run at the target PHP version
- You can list the plugin functions that matter, such as "the booking form saves an entry"
We stop and tell you if
- The plugin's code is encoded or obfuscated
- The plugin depends on a PHP extension your host will not provide at the target version
- The plugin's licence forbids modification
- The staging copy cannot run the target PHP version
- The failure turns out to be in another plugin or the theme rather than this one
- The site is a multisite network, which is quoted separately
What could go wrong
The patch changes only the named plugin's files, which your site holder keeps a copy of. Switching the host back to the previous PHP version restores the old behaviour at once, so long as that version is still available to you.
Scroll the table sideways to read it all.
| Risk | How we handle it |
|---|---|
| A static scan misses a problem that only appears when the code runs | We run the agreed functions on staging at the target version and read the PHP log; the handover lists what was and was not exercised. |
| The patch is overwritten when the plugin is next updated or reinstalled | For an abandoned plugin there should be no update; for a custom plugin we hand over files, not a change inside a hosting dashboard. The note says how to keep the patch. |
| Staging data differs from live data and hides a fault | We ask for a copy with realistic made-up content and list data cases the functions must handle; your site holder re-tests on live after switching. |
A second reviewer checks the scan results against the fixes, reads every changed line that touches input, files or the database, and checks the switch-back steps.
How we deliver
We arrange the work and independent review, then show you the result against the agreed checks. You keep authority over your systems.
- Restore the plugin and a staging copy at the current PHP version and record the agreed functions working
- Run the compatibility scan for the target version and sort the findings into fix, ignore and unknown
- Fix each finding with the smallest change and re-run the scan
- Run the agreed functions and the main site pages on the staging copy at the target version and compare with the old version
- Independent review of changes touching forms, file handling, database queries or logins
- Hand over the patched plugin, scan results, test results and switch-over and switch-back steps
This is a one-off job, not emergency cover or a subscription. We confirm eligibility, the total price, a start window and a delivery date before you accept. Work starts only after agreed inputs, secure access, any licences and necessary permissions are in place. Hosting, plugin licence and supplier charges are excluded unless the written quote includes them. No charge or booking is created by an enquiry.
Need to keep it working?
Discuss trying each plugin update on a staging copy before it goes live.
Ongoing work is separately scoped and quoted: no monitoring, response-time guarantee or automatic subscription is included in this job.
Explore an ongoing engineering lane, or mention the responsibility you need in your enquiry.
What you can check
This is a new service. We have not delivered this job for a client yet.
Other ways to get this done
- Replace the plugin with a maintained one that does the same job. This is often the more durable choice if the plugin's function is common; we say so in the replacement note.
- Stay on the current PHP version until its support ends. This is a short-term option only; the PHP project publishes its end dates.
Questions
Is a clean scan enough?
No. A scan reads code without running it, so we also run the functions you list on a copy at the new version.
Can you patch a plugin from the WordPress plugin directory?
Only if it has no compatible update and its licence allows changes. If it has an update, install that instead; the first step of the job is to check.
What if I have three old plugins?
This job covers one. Several are a wider upgrade, which we would quote separately after a scan of each.
Send an enquiry
Send us
- The plugin's name, its version and the PHP version you run now and want to move to
- Where the plugin came from: built for you, a marketplace purchase, or the WordPress plugin directory
- What the plugin does, and three to six functions that must work afterwards
- The warning or error text you see at the newer version, with personal details removed
- Whether your host offers a PHP version switch per site and a staging copy
Later, once you agree
- A staging copy of the site that can run at both PHP versions
- The plugin's files, or access to them on the staging copy
- Evidence that you may modify the plugin, such as a licence file or the developer's written confirmation
- A company-controlled secure handoff agreed before access: no live passwords, keys, private code or customer records by ordinary email.
You keep the live site and hosting account. We change the plugin on a staging copy and hand over the patched files; your site holder installs them and switches the PHP version.
Email fallback: open your mail app
If website submission is unavailable, review and send the fallback email yourself. An email fallback is not a website receipt. Or write to hello@syntheticindustry.ai with “plugin-php-version-incompatibility-one-plugin” as the subject.