PHP developer in Birmingham

PHP developer for Birmingham and West Midlands firms: Laravel, Symfony, legacy upgrades, integrations, WordPress. Remote, written reply within 48 hours.

PHP developer

My place in the WordPress community

  • I have had a wordpress.org account since 2006.
  • I contributed to WordPress core for versions 7.0 and 7.1.
  • I maintain 30 plugins on wordpress.org.
  • I organise and speak at WordCamps.
  • I have attended every WordCamp Europe from 2017 to 2026.

My WordPress.org profile

If you are looking for PHP developers in the West Midlands, the first question is rarely Laravel against Symfony. It is how old the application is and which version of PHP it runs on. I am a single developer in Gdynia, a port city on the Baltic, and I take PHP work from Birmingham and the surrounding counties remotely. There is no Birmingham office. Polish clocks run an hour ahead of British ones, and every enquiry is answered in writing before 48 hours have passed.

#Where PHP support stands today

Support dates decide the order of work, so here they are as published on 9 November 2026.

  • PHP: the supported versions page lists 8.2, 8.3, 8.4 and 8.5. Security fixes end on the last day of 2026 for 8.2, of 2027 for 8.3, of 2028 for 8.4 and of 2029 for 8.5. Anything older is missing from that table.
  • Laravel: per the release notes, version 11 stopped receiving security fixes on 12 March 2026. Version 12 gets them until 24 February 2027, and 13 runs on PHP 8.3 and above.
  • Symfony: the releases page shows 6.4 with bug fixes until November 2026 and security fixes until November 2027. Branch 7.4 is the long-term support release, fixed until November 2029.

An application on PHP 8.1 or Laravel 11 is therefore already outside what its maintainers patch. One on PHP 8.2 has until the end of this year. That is a plan with dates, not an emergency, and most of the work is mechanical once the tests are in place.

#What I build and repair

  • Laravel applications and APIs: back offices, customer portals, queues and scheduled jobs.
  • Symfony systems: long-lived business software, Messenger workers and integrations with the accounting, CRM or stock systems you already run.
  • Legacy upgrades: an old codebase moved up one supported PHP version at a time, with tests written around the behaviour you cannot afford to lose.
  • Integrations: payment, shipping and ERP connections that retry safely and log what they did.
  • WordPress and WooCommerce code: custom plugins and REST endpoints. Themes, shops and upkeep have their own pages: WordPress developer in Birmingham, WooCommerce developer in Birmingham and care plans.

The general overview of my PHP work is on the PHP developer page.

#How an upgrade runs

An upgrade of a neglected application follows one order, and skipping a step is where projects go wrong.

  1. Read the code, the Composer lock file and whatever tests exist. List the packages that block a newer PHP.
  2. Add tests around the pages and jobs that earn money: login, checkout, invoices, exports.
  3. Move up one PHP branch at a time on a staging copy, fixing deprecation notices as they appear.
  4. Upgrade the framework only after PHP is on a supported branch, so two risky changes never land together.
  5. Release outside your busy period, keep a way back ready, and finish with written notes.

Everything lives in a Git repository in your own account. Any developer can pick it up after me, which matters more than a local postcode.

#UK rules a PHP application meets

Legal advice is outside my remit and the call on what binds your company is yours. Below are the points I look for in code, each one pinned to the statute text.

#Personal data breaches

The 72-hour window in UK GDPR Article 33 starts when a controller learns of a breach, and the regulator is told within it where feasible, and a late notice must give its reasons. A breach unlikely to put people at risk need not be notified, but it is still documented. My side is technical: access logs that survive long enough, a clear record of which code touches personal data, and a timeline you can hand to whoever makes the report.

#Cookies and tracking scripts

Schedule A1 to PECR, in force since 5 February 2026, needs no consent for storage essential to the service a visitor requested. Counting visits so the site can be improved is exempt as well, provided the figures stay within that purpose, visitors are plainly told and can object easily at no cost. A PHP application sets session and CSRF cookies, and these usually fall in the first group. Marketing tags do not. In code I keep them apart, and the marketing group fires only after a visitor agrees.

#West Midlands: what is local and what is not

The UK section of the WordPress.org meetup listings includes a WordPress Birmingham Meetup on the fourth Wednesday of each month. It lists no group for Coventry, Wolverhampton, Worcester or Stoke. I do not claim a local network I do not have. A West Midlands company gets repository access, docs and a staging site, so continuity does not rest on one person living nearby.

#Questions from the West Midlands

#Are you based in Birmingham?

No. My desk is in Gdynia, where clocks run an hour ahead of Britain’s. Mail and files carry the project, and you get a written answer to each message inside 48 hours.

#Is the work limited to Birmingham itself?

Yes, Coventry, Wolverhampton, Worcester or anywhere else, because the work is remote. Distance changes nothing about how a project runs.

#Which PHP version should we run?

Start new projects on 8.4 or 8.5. For an existing application, the supported-versions table above sets the deadline, and I plan the upgrade backwards from it.

#Will you do the interface design?

No. Layouts, mockups and graphic design come from you or your designer. I build the supplied layout into working, accessible screens.

#How to start

Send the brief through the contact form: the application, its PHP and framework versions, the hosting and what you need changed. I answer in writing within two working days. For code that handles personal data, the WordPress security audit page describes how I review it.

Need this service: PHP developer in Birmingham?

Describe your project by e-mail. I reply within 48 hours.

Describe your project

Latest PHP developer articles

Oct 21, 2026

PHP2Shell: is my WordPress site at risk and what to do

PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35, released on 21 October 2026, fix two critical vulnerabilities in PHP itself (CVE-2026-109618, CVE-2026-109619). How to check the PHP version in WordPress, what to do when your host has not updated the server yet, and which passwords to change after the update.

Explore other WordPress services and knowledge base