Virtual server PHP broken after using the Web App installer for installing Wordpress

[tecpi]

I installed just PHP 8.4 not PHP 8.5 so if you dont install PHP 8.5 you should not see on Virtualmin. I did not write that there is a bug or issue for with PHP 8.5 can’t be selected but in my case I just installed PHP 8.4. Maybe Ubuntu install also PHP 8.5 not fully because I cannot see currently by Virtualmin but the point is: why using Web App Installer for install Wordpress changed the PHP client version from 8.4 to 8.5?

This should not happen on my point of view and caused issues.

[jimr1]

If you installed php 8.4 using the ondrej repository prior to the release of php 8.5 you would have not got a php 8.5 instalation however when php 8.5 was released the ondrej repostitory pushed both the updated php 8.4 and also installed php 8.5, in my case php 8.5 just appeared one day. I don’t know what happens if you install php 8.4 after the release of php 8.5 maybe it will install just php 8.4 if that is the case there may be some bug/feature in the repro that installed php 8.5 as well as updating php 8.4

[Ilia]

@tecpi

I can understand maybe if my server was missing the supported PHP and necessary PHP extensions but in this case maybe the setup should show the issue and asking to resolve or auto-resolve but in my case.

I agree, I’d probably leave it as is and just show a warning when required version of PHP isn’t available rather than changing it.

That’s why we need a comment from @Jamie about what his initial intentions were and how he prefers to handle it now.

[Joe]

I’d also note that there’s no technical reason each app can’t use its own PHP version. We’d just need a separate PHP-FPM config for each one. We need to re-factor PHP-FPM support, anyway, so resource limits work.

[Ilia]

@Joe

I’d also note that there’s no technical reason each app can’t use its own PHP version. We’d just need a separate PHP-FPM config for each one. We need to re-factor PHP-FPM support, anyway, so resource limits work.

Yeah, that would be a big rework, but worth it! I’m motivated to look into it soon.

[Jamie]

@Ilia

@Jamie, what are your thoughts on this? Why don’t we show a confirmation screen instead of immediately proceeding, so the user can confirm if they’re okay with the PHP version switch before continuing the installation?

I actually would prefer if we could support per-directory PHP-FPM versions. It would be non-trivial, but would at least be consistent with how the FCGI PHP support works.

[Ilia]

@Jamie

I actually would prefer if we could support per-directory PHP-FPM versions. It would be non-trivial, but would at least be consistent with how the FCGI PHP support works.

Yes, yet this is for the future rework.

For now, we need to decide how to handle the forced PHP change gracefully when a web app is installed.

The problem is that one domain can host several web apps, and not all of them are installed through Virtualmin. When Virtualmin automatically changes the PHP version after a new app is installed, it can cause other PHP apps on that domain to break.

Can you clarify what the original intent was? Or was it primarily designed for FCGI mode, which allows per-directory PHP versions?