# After upgrading to 4.5.2, phinx migration "crashes" with a warning about requiring PHP 8.4
**URL:** https://community.xibo.org.uk/t/after-upgrading-to-4-5-2-phinx-migration-crashes-with-a-warning-about-requiring-php-8-4/38416
**Category:** CMS Installation
**Created:** [September 8, 2026, 12:55pm UTC](https://community.xibo.org.uk/t/after-upgrading-to-4-5-2-phinx-migration-crashes-with-a-warning-about-requiring-php-8-4/38416 "2026-09-08T12:55:22Z")
**Posts on this page:** 8
**Page:** 1
### Author:  [@Mythril](https://community.xibo.org.uk/u/Mythril)
#### Post date: [September 8, 2026, 12:55pm UTC](https://community.xibo.org.uk/t/after-upgrading-to-4-5-2-phinx-migration-crashes-with-a-warning-about-requiring-php-8-4/38416/1 "2026-09-08T12:55:23Z")
# CMS Version
Upgraded from 4.5.0 to 4.5.2
# Installation Method
Custom install (Apache httpd v2.4.62 with PHP-FPM v8.3.33)
# Operating System
AlmaLinux 9.8
# Issue
After upgrading to 4.5.2, the phinx executable “crashes” with a warning about requiring PHP 8.4, even when just running the command itself:
```auto
xibo_user> vendor/bin/phinx
Composer detected issues in your platform:
Your Composer dependencies require a PHP version ">= 8.4.0". You are running 8.3.33
```
We don’t want to force upgrade the PHP version in AlmaLinux to anything higher than its regular appstream modules (8.3 is highest). So I tried to bypass the warning by editing vendor/composer/platform\_check.php and changing the PHP version check to PHP 8.3 (instead of 8.4 / 80400 which was the original check):
`if (!(PHP_VERSION_ID >= 80300)) {`
Since I assumed none of the actual PHP code actually requires PHP 8.4.
Running the migration and testing the admin dashboard afterwards seemed to work fine.
---
### Author:  [@dan](https://community.xibo.org.uk/u/dan)
#### Post date: [September 9, 2026, 7:58am UTC](https://community.xibo.org.uk/t/after-upgrading-to-4-5-2-phinx-migration-crashes-with-a-warning-about-requiring-php-8-4/38416/2 "2026-09-09T07:58:56Z")
> [@Mythril](#):
>
> Since I assumed none of the actual PHP code actually requires PHP 8.4.
Just a heads up that there might be various other dependencies, etc, that require 8.4.
PHP 8.3 dropped out of active support 8 months ago on 31 Dec 2025, and due to various new regulations (and best practice) we will be pushing forward as fast as we can with PHP versions. That means 8.5 will be coming soon too.
---
### Author:  [@Romolo\_Manfredini](https://community.xibo.org.uk/u/Romolo_Manfredini)
#### Post date: [September 9, 2026, 10:56am UTC](https://community.xibo.org.uk/t/after-upgrading-to-4-5-2-phinx-migration-crashes-with-a-warning-about-requiring-php-8-4/38416/3 "2026-09-09T10:56:11Z")
I’m running 4.5.2 without docker on php 8.5 (ubuntu server 26) without any single warning.
---
### Author:  [@Mythril](https://community.xibo.org.uk/u/Mythril)
#### Post date: [September 10, 2026, 10:07am UTC](https://community.xibo.org.uk/t/after-upgrading-to-4-5-2-phinx-migration-crashes-with-a-warning-about-requiring-php-8-4/38416/4 "2026-09-10T10:07:36Z")
We are using RHEL distros for our servers, which is currently up to PHP 8.3 in dnf modules, and we prefer not to “force install” newer versions of software unless strictly necessary.
But docker install is of course an option anyways.
---
### Author:  [@Mythril](https://community.xibo.org.uk/u/Mythril)
#### Post date: [September 10, 2026, 10:10am UTC](https://community.xibo.org.uk/t/after-upgrading-to-4-5-2-phinx-migration-crashes-with-a-warning-about-requiring-php-8-4/38416/5 "2026-09-10T10:10:57Z")
Oh yeah also, if you are going to require PHP 8.4 from now on you can update the version requirements here (which still says PHP 8.1, which is why I was confused):
> **[Xibo Digital Signage](https://account.xibosignage.com/docs/setup/xibo-on-a-web-server)**
>
> Guidance for the installation of the Xibo CMS as a manual/custom installation on a web server
---
### Author:  [@dan](https://community.xibo.org.uk/u/dan)
#### Post date: [September 10, 2026, 4:06pm UTC](https://community.xibo.org.uk/t/after-upgrading-to-4-5-2-phinx-migration-crashes-with-a-warning-about-requiring-php-8-4/38416/6 "2026-09-10T16:06:53Z")
Yes, I noticed this too and have raised it as an issue. As you can see on that page our docs are undergoing an overhaul and manually installing (without Docker) won’t be covered anywhere but here in future:
>
I appreciate that is also wrong 😅 we will get it changed.
---
### Author:  [@Romolo\_Manfredini](https://community.xibo.org.uk/u/Romolo_Manfredini)
#### Post date: [September 14, 2026, 3:33pm UTC](https://community.xibo.org.uk/t/after-upgrading-to-4-5-2-phinx-migration-crashes-with-a-warning-about-requiring-php-8-4/38416/7 "2026-09-14T15:33:14Z")
Dan,
while I do unnderstand that docker may simplify installation as somehow it get standardized with all the required components, but docker installation in LXC containerized environment, as by example proxmox, is really a pity…
Also from a security point of view non dockerized installations get the patches for php and the database as soon as they are distributed by the os, while docker installation is not automatic at all.
I really hope it will be possible to continue to install xibo outside of docker.
---
### Author:  [@dan](https://community.xibo.org.uk/u/dan)
#### Post date: [September 24, 2026, 7:35am UTC](https://community.xibo.org.uk/t/after-upgrading-to-4-5-2-phinx-migration-crashes-with-a-warning-about-requiring-php-8-4/38416/8 "2026-09-24T07:35:35Z")
> [@Romolo\_Manfredini](#):
>
> I really hope it will be possible to continue to install xibo outside of docker.
You’re welcome to install Xibo outside of Docker if you want, and all of the documentation to do so will be in the repository mentioned above. However suggesting it in our documentation alongside the other options leads to many more users taking a non-docker route than there otherwise would be, and not all of them are security conscious like you guys are.
On the dependency versioning topic, there are various new regulations which require us to keep moving forward with dependency updates as quickly as possible. We will balance that against the complications of updating dependencies, but there really isn’t any choice in the matter.