The site went blank after the version change
Removed functions such as each(), split() or create_function(), or a type mismatch the old runtime quietly allowed, now fatal on the new one.
Code brought up to the new version
Working with PHP?
Most PHP codebases that land on our desk were last touched around PHP 5.6 or 7.0, and the host has just announced the old version is going away. We walk the code, find every pattern the new runtime refuses to accept, and get you onto a current release without surprises in production.
What it is
PHP is a server-side scripting language created by Rasmus Lerdorf in 1994 and now maintained by the PHP Group. It runs a sizeable share of the public web through WordPress, Laravel, Drupal, Joomla and Magento, and most shared hosting plans include it by default.
The language supports procedural, object-oriented and functional styles, so codebases written over the last twenty years look very different depending on when and by whom they were built. That variety is also why upgrading an older site onto a current PHP release is rarely a one-command job.
The honest version
No technology is all upside. This is where PHP earns its place and where it tends to cause trouble.
Sound familiar?
The PHP problems that bring people to us, and what you have once each one is fixed.
Removed functions such as each(), split() or create_function(), or a type mismatch the old runtime quietly allowed, now fatal on the new one.
Code brought up to the new version
Warnings from PHP 8.1 and later about nullable parameters, implicit conversions and dynamic properties that the previous runtime did not care about.
Warnings cleared at the source
A library has moved to require PHP 8.2 or later and the server is still on 7.4, so composer update stops before anything lands.
Runtime and lockfile back in step
Modules such as Memcache, mcrypt or an old ionCube loader that were present on the old server but never installed on the new one.
Extensions matched or replaced
A report or import that holds every row in an array, or an opcache that was never sized for the codebase.
Memory use measured and bounded
An old release that the host is about to force off the server, with a codebase nobody has audited against anything newer.
Upgraded on a tested plan
An old mysql_* call pattern, a socket path that changed with the new PHP packages, or credentials that moved during a host migration.
Connection restored and documented
What we do
Call us for one broken deploy, or hand us the whole codebase.
How it works
Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.
We fix the cause, not the symptom. If something is down, getting it back up comes first.
Backups, monitoring, updates and access, so the same problem can't quietly come back.
You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.
Often found together
We work on the whole stack, so the problem can be wherever it actually is.
Yes, and it is one of the most common jobs we take on. We run the existing code against a modern runtime on a copy first, list every pattern that needs changing, fix them, and only then move the live site. Skipping the rehearsal is what turns these upgrades into outages.
A deprecation notice is the runtime telling you that a call still works today but will stop working in a later release. The right fix is to change the call rather than to silence the warning. Common culprits are create_function, each(), implicit nullable parameters and dynamic property writes, each with a documented replacement.
A blank page from PHP almost always means a fatal error with display_errors turned off. The real message is in the PHP error log and is usually a removed function, a stricter type check, or a missing extension on the new server. Once the log is readable the fix is normally a small code change, not a rollback.
No. Every release in the 7.x line, including 7.4, has passed its official security support window. Hosts and distributions may patch some issues for a while longer, but new vulnerabilities are not being fixed upstream, and compliance reviewers increasingly flag it on sight.
Usually two upgrades at once: the language and the framework, because older Laravel releases do not support PHP 8 and current Laravel releases do not support PHP 7. We pin a working combination, update composer constraints, run the test suite against the new runtime, and work through the deprecations the framework itself has introduced along the way.
Estimates are free. Tell us the current PHP version, roughly how big the codebase is and what framework it uses, and you get a price before any work starts.
Free estimate
Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.
Your message is with a real person, and we'll get back to you soon.
Rather talk now? Call us: