Case studies

A closer look at how I work: what was broken, what I changed, and how I proved it works. Each one has a detailed change log.

Case study 01 · Japanese manufacturer · 2 sites

Finding a silent contact-form failure before a PHP 8.4 launch

Every inquiry would have vanished on PHP 8. I found the bug before launch, and both sites now deliver every email with zero errors.

Before, on PHP 8.4Blank page after submitting. 0 emails sent.
AfterAuto-reply and admin notice delivered. 0 errors.
  • 0 → 2emails delivered per inquiry
  • 2sites upgraded: corporate and recruitment
  • 0errors, warnings, or deprecations
  1. ScanPHPCompatibility on both codebases
  2. RebuildTest databases from the schemas
  3. ProveReal emails through a local mail server
  4. Verify0 errors with every warning on
  • PHP 8.4
  • Fegg framework
  • PHPMailer
  • SQLite
  • PHPCompatibility
  • Git
Problem
A Japanese manufacturer's corporate website and its separate recruitment site had to move to PHP 8.4. The pages loaded, but the corporate site's code had a hidden problem: its contact form read two form fields that didn't exist. PHP 7 ignored this, but on PHP 8 every inquiry would end on a blank page with no email sent to the customer or the company. Uploads without a file also crashed, and local testing showed dozens of deprecation warnings.
What I did
Scanned both codebases with PHPCompatibility, built test databases from each project's schemas, and ran the sites with every error type switched on from the start. To test the forms for real, I ran the contact and job-entry forms through the actual PHPMailer code path against a local mail server, comparing the original and fixed code. I guarded the missing form fields, fixed the upload and CMS crashes, and cleared every deprecation by declaring each class property explicitly. The recruitment site had already been partly upgraded, so I confirmed what was done and patched only what was left.
Result
The corporate contact form went from sending 0 emails to delivering both the customer auto-reply and the admin notice, and the recruitment entry form delivered both emails too. Every page, CMS screen and form on both sites runs on PHP 8.4, and full test runs with every warning switched on produced zero errors, warnings or deprecations.

Case study 02 · Welfare organization · 2 sites

PHP 8.4 upgrade and security hardening for two legacy sites

Two sites moved to PHP 8.4 without breaking anything, and logins were upgraded to modern password hashing without a single password reset.

BeforeAdmin screens and uploads crashed. Passwords stored with sha1.
AfterEvery screen works on PHP 8.4. Passwords use password_hash().
  • 2legacy sites upgraded
  • ~190pages tested on one site
  • 0password resets needed
  1. ScanPHPCompatibility on both codebases
  2. TestAbout 190 pages, forms, and CMS screens
  3. FixPHP 8 errors and deprecated functions
  4. SecureModern hashing, tighter access rules
  • PHP 8.4
  • Fegg framework
  • SQLite
  • PHPCompatibility
  • Git
Problem
Two websites for a Japanese welfare organization, a corporate and recruitment site and an internal file portal, had to move to PHP 8.4. Several admin screens and upload forms crashed with fatal errors, and the login still used outdated sha1 password hashing.
What I did
Scanned both codebases with PHPCompatibility, then ran each site locally and tested every page, contact and recruitment form, and CMS screen. Fixed PHP 8 errors in the admin and upload code, replaced deprecated functions, removed an outdated library, tightened server access rules, and moved logins to password_hash() with an automatic upgrade for existing users.
Result
Both sites run on PHP 8.4 with their existing behavior intact, and admin accounts use modern password hashing without anyone having to reset their password.

Case study 03 · Japanese company · corporate and recruitment site

Bringing a legacy PHP framework back to life on PHP 8.4

A site that failed on every page under PHP 8 now runs cleanly on PHP 8.4, with all 73 templates proven identical to the original.

Before, on PHP 8Fatal error on every page. The template engine used a removed feature.
AfterEvery page, CMS screen, and form works. 73 of 73 templates identical.
  • 73 / 73templates identical
  • 0errors, warnings, or deprecations
  • 100%pages, CMS screens, and forms
  1. ScanPHPCompatibility across the codebase
  2. RewriteTemplate compiler with native closures
  3. CompareOld and new output, all 73 templates
  4. Verify0 errors, warnings, or deprecations
  • PHP 8.4
  • Fegg framework
  • SQLite
  • PHPCompatibility
  • Git
Problem
A Japanese company's corporate and recruitment website returned a fatal error on every page under PHP 8. Its template engine was built on create_function(), which PHP 8 removed, and local testing also showed dozens of deprecation warnings that broke sessions.
What I did
Rewrote the template compiler's dynamic functions as native closures, then proved they behave exactly the same by rendering the full site with the old and new logic and comparing the output. Fixed PHP 8 errors in the CMS, file uploads and the job application form, and cleared every deprecation warning by declaring each class property explicitly, without falling back on #[\AllowDynamicProperties] to silence them. I also repaired a broken gallery uploader and tightened server access rules.
Result
Every page, CMS screen and form runs on PHP 8.4. All 73 compiled templates came out identical to the original, and a full test run with every warning switched on produced zero errors, warnings or deprecations.

Have an older site that needs the same care?

Tell me about it, and I’ll reply within one business day with what I’d check first.