Case study · ExpressionEngine modernization

Multi-site ExpressionEngine 6: PHP 8.3 compatibility and a staging rescue

A licensed add-on took down every page after a PHP upgrade. We patched it to run on PHP 8.3 and found why staging logins failed.

Client
Two organisations sharing one ExpressionEngine Multi Site Manager install (name withheld)
Technologies
ExpressionEngine 6.4Multi Site ManagerPHP 8.3Add-on patching

Project overview

The organisations run their websites from a single ExpressionEngine 6.4 install using Multi Site Manager (MSM). After the server moved to a newer PHP version, the front end stopped loading.

The challenge

Every page that loaded the site header failed with a fatal error, so both websites were effectively down. A separate staging copy, needed to test fixes safely, would not let anyone log in.

Technical challenges

  • A licensed maps add-on threw a fatal TypeError inside its bundled Carbon date library on PHP 8.
  • The add-on still used create_function(), which was removed in PHP 8.
  • Magic methods in the add-on had visibility that PHP 8 no longer accepts.
  • Staging showed "configured cookie domain does not match the site URL" at login.

Our approach

  • Reproduced the fatal error and traced it to the library call inside the add-on rather than the site templates.
  • Patched the Carbon library call and replaced create_function() with a closure.
  • Fixed the magic-method visibility so the add-on loads cleanly on PHP 8.3.
  • Traced the staging login failure to a front controller that pointed at the live system folder and the live database.

Outcome

The maps add-on runs on PHP 8.3.