Working with PHP?

PHP upgrade broke the site? We fix it.

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.

  • Since 2015Fixing technology
  • FreeEstimates
  • US teamReal engineers

php-error.log

still failing

What it is

PHP at a glance

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.

Type
Server-side scripting language
First released
1995
License
PHP License v3.01
Maintained by
The PHP Group
Typically used for
Web applications, CMSes, ecommerce back ends, APIs and CLI scripts

The honest version

PHP pros and cons

No technology is all upside. This is where PHP earns its place and where it tends to cause trouble.

Where PHP is strong

  • Runs on practically any hostShared hosting, container platforms, cloud VMs and managed app services all ship with PHP ready to go, so deploying something is seldom blocked by the runtime.
  • Mature package ecosystemComposer and Packagist cover almost every library a web app needs, and the tooling around autoloading and version constraints is now well settled.
  • Fast request startupEach request boots cleanly and exits, which keeps memory leaks rare and makes horizontal scaling straightforward behind a normal web server.
  • Deep talent poolIt is one of the most widely known languages on the web, so finding developers, documentation and host support is rarely the hard part of a project.
  • Modern versions perform wellThe JIT added in PHP 8 and years of engine work mean current releases run considerably faster and use less memory than the 5.x line most legacy sites were built on.
  • The frameworks that carry the webWordPress and Laravel between them power a huge chunk of real-world sites, which means proven patterns for almost every feature you might need to add.

Where PHP bites

  • Deprecated patterns are everywhereShort open tags, the old mysql_* functions, magic quotes assumptions and create_function calls still live in codebases that have not been touched in a decade.
  • Major versions break somethingEvery jump, 5 to 7, 7 to 8, 8.1 to 8.2, removes functions or tightens type rules, and code that ran fine last week throws fatals the morning after the upgrade.
  • Type coercion has a historyYears of loose comparisons and silent conversions left subtle bugs in older code that only surface once stricter checks arrive with a new runtime.
  • Shared hosting lags badlyPlenty of hosts still default new accounts to a PHP release that lost security support years ago, and customers rarely find out until something external forces the move.
  • Encoded and licensed extensionsionCube, Zend Guard and similar loaders tie a codebase to specific PHP builds and often block an upgrade until the vendor ships a matching runtime.

Sound familiar?

Common PHP problems we fix

The PHP problems that bring people to us, and what you have once each one is fixed.

white screen after PHP 8 upgrade

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

Deprecated: implicit float to int

The log is flooded with deprecation notices

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

composer: your PHP version does not satisfy

Dependencies refuse to install

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

Class 'Memcache' not found

An extension vanished in the upgrade

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

memory_limit exhausted at 128M

Scripts run out of memory under load

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

PHP 7.4 end of life

The runtime no longer gets security fixes

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

mysqli_connect HY000/2002

The database connection stopped working

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

PHP help, from rescue to upkeep

Call us for one broken deploy, or hand us the whole codebase.

Rescue
White screens, fatal errors and failed deploys after a version change. We get the site serving again, then explain what caused it.
Version upgrades
Moves from PHP 5.6, 7.0 or 7.4 onto a current release, rehearsed on a copy of the site before anything touches production.
Deprecation sweeps
Walking the code for patterns the next version will refuse, and clearing them before the host forces the change on its own schedule.
Performance
Opcache sizing, JIT settings, slow endpoint tracing and query work, with numbers recorded before and after.
Framework work
Laravel, Symfony and legacy custom apps, including upgrades across framework major versions alongside the language upgrade.
Managed Tech
Updates, monitoring, backups and a team to call, on an ongoing basis.

How it works

From first message to fixed

  1. Look Free estimate

    Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.

  2. Fix

    We fix the cause, not the symptom. If something is down, getting it back up comes first.

  3. Harden

    Backups, monitoring, updates and access, so the same problem can't quietly come back.

  4. Hand back or stay on

    You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.

Often found together

Running PHP alongside something else?

We work on the whole stack, so the problem can be wherever it actually is.

Questions

PHP questions

Something else? Call+1 737 727 7327

Can you upgrade our site from PHP 5.6 to PHP 8?

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.

How do I fix a 'deprecated function' notice after upgrading PHP?

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.

Why does my site white-screen after a PHP update?

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.

Is PHP 7 still safe to run?

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.

What's involved in upgrading a Laravel app from PHP 7 to PHP 8?

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.

How much does a PHP upgrade cost?

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

PHP upgrade looming?

Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.

  • No charge to find out what it will take
  • If it's urgent, say so

Replies come from a person. By sending, you authorize us to email you back. No marketing.