What we do
Tools
Industries
Department
How we workLet's talk →
Home/PHP Developer
PHP Development

Hiring a PHP Developer When the Code Is Old and the Host Is Upgrading

A lot of businesses run on PHP without thinking of it that way: the customer portal, the booking tool, the WooCommerce shop, the admin screens someone built ten years ago. It keeps working until the host retires the PHP version it was written for, or a security notice lands for a package nobody has updated. That's usually when the search for a PHP developer starts, with a deadline already set by someone else.

Got the "PHP version retiring" email?

Find out which version you're on. Your hosting control panel usually shows it. On WordPress, the Site Health screen lists it under the server details. php.net publishes the date each PHP release stops getting security fixes, so you can see how far behind you are.

Don't let the host upgrade the live site first. Ask for a staging copy on the new version, or have a developer run the code against it locally. Most breakage shows up in the first few page loads.

If the deadline is close, ask the host whether they offer paid extended support for your old version. It buys weeks, not years, and the code still has to move.

What old PHP code does on a newer PHP version

These are the failures that turn a routine host upgrade into a blank page. Each one is findable before the switch, by running the code on the new version and reading the log.

A blank page and "Call to undefined function mysql_connect()"

How you'll know: The whole site or app stops at the first database call.

Fix: The old mysql_* functions were removed back in PHP 7.0. The code needs moving to PDO or mysqli, and that's the moment to switch to prepared statements, which also closes the SQL injection holes old code tends to have.

each() or create_function() no longer exists

How you'll know: A fatal error on PHP 8, often inside an old library or a plugin bundled years ago.

Fix: Both were removed in PHP 8.0. Replace them with foreach loops and anonymous functions, or update the library if a newer version exists. Tools such as PHPCompatibility scan the codebase for every case at once.

Comparisons that quietly give a different answer

How you'll know: No error at all, but a login check, a discount rule or a status filter now behaves differently.

Fix: PHP 8 changed how a string is compared with a number using ==, so code that relied on the old behavior can take the other branch. Search for loose comparisons in anything that touches money or access, and switch them to strict === where the types should match.

Logs filling with deprecation notices

How you'll know: The app works, but the error log grows by thousands of lines a day after the upgrade.

Fix: PHP 8.1 deprecated passing null to many built-in functions, and 8.2 deprecated setting properties a class never declared. Nothing breaks yet, but these become errors in a later version. Fixing them now is cheaper than doing it under the next deadline.

Composer packages pinned to an old framework

How you'll know: composer.lock holds a Laravel, Symfony or CodeIgniter version that won't install on the new PHP, or there's no Composer file at all and libraries were copied in by hand.

Fix: Upgrade the framework one major version at a time, with tests around the parts the business relies on. Rector can automate a lot of the mechanical changes, but someone still has to check what it did.

Starting fresh: Laravel or WordPress?

Both are PHP, and plenty of developers do both. They suit different jobs.

WordPress

When the site is mostly content and marketing

  • Your team edits pages, posts and products themselves, without a developer.
  • Plugins cover most of what you need: forms, SEO, a WooCommerce shop.
  • Custom work is a small plugin added on, not the heart of the site.
  • See WordPress developer for that route.
Laravel

When the site is really an application

  • Logins with roles, approvals, quotes, bookings or jobs that move through stages.
  • Your own data model, not posts and pages bent to fit.
  • Integrations with accounting, CRM or stock that run on queues and schedules.
  • See Laravel developer for the framework in more depth.

A common mix is WordPress for the public site and a Laravel app behind a login for customers or staff. Forcing an application into WordPress plugins is where most of the old PHP rescue jobs we see started.

Ask before a PHP developer touches the old codebase

The answers show whether they'll treat the code as something the business depends on, or as something to rewrite in their favorite style.

  • "How will you find out what the code does today?"

    The safe answer involves reading it, running it on a copy and writing tests around the money and access paths before changing anything. "We'll rebuild it properly" on day one is a warning sign.

  • "Which PHP version will it end up on, and when does that one stop getting fixes?"

    Landing on a version that's already near its end of life means doing this again soon.

  • "Where will the code live?"

    In a repository your company owns, with Composer managing libraries, not files edited straight on the server over FTP.

  • "What happens to our database during the upgrade?"

    Old PHP apps often store data in ways the new code reads differently, like dates as text or mixed character sets. A database developer skill set matters when that's the case.

  • "Who keeps it current after this?"

    Security releases for PHP, the framework and every package keep coming. Someone has to apply them, or the app drifts back to where it is now.

Let's talk

Old PHP, moved forward without a rewrite

n-frames takes over PHP applications and heavily customized WordPress and WooCommerce sites that a business can't afford to have stop: we get the code into a repository, run it on a current PHP version, fix what breaks and keep it patched afterward. When the server side is bigger than one app, backend developer covers that work, and a brand-new product is custom software development.

Upgrade our PHP app safely →

Questions people ask

Can you take over a WordPress or custom PHP site a previous freelancer built?

Yes, and it's one of the most common ways PHP work reaches us. We start with an inventory: PHP version, framework and package versions, plugins, where the code lives and who has access. Nothing changes until we've run it on a copy and know what it does.

How do you handle security patching on PHP apps after launch?

For the apps we look after, we track security releases for PHP itself, the framework, WordPress core and the plugins or Composer packages the app uses, and apply them after testing on a staging copy. Launch isn't treated as the end of the job.

If our PHP project is just one small fix, is a full rebuild on the table?

No. A small fix gets priced and done as a small fix. If it uncovers something bigger, like a PHP version that's out of support, we raise it as a separate decision rather than folding it into the fix.

What does the free quote on PHP work actually include?

A look at the code and the server it runs on, how current the PHP, framework and plugin versions are, and a number for the job you asked about. If the version gap is a risk on its own, it's priced separately so you can choose.

Do we have to rewrite old PHP to move it onto Laravel?

Rarely all at once. A working app can be upgraded in place to a current PHP version first. If moving to Laravel is worth it, new features can be built there while old screens keep running, and parts move over one at a time.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.