Why are you running an EOL version of PHP?

Why are you still running an EOL version of PHP?

  • I don't have access to upgrade PHP myself, and the server owner won't do it for me

    Votes: 7 4.4%
  • I can't upgrade because other software I use requires an old version of PHP

    Votes: 22 13.8%
  • I lack the technical know-how to upgrade PHP

    Votes: 5 3.1%
  • I don't consider updating PHP to be particularly important

    Votes: 2 1.3%
  • I’m running PHP 7.latest and that’s fine for me

    Votes: 14 8.8%
  • I’m running PHP 8 🥳

    Votes: 110 68.8%

  • Total voters
    160
Is there any advantage of using 8.4 compared to 8.3?
The more people use it, the sooner developers can take advantage of the features it offers. Most notably for XenForo, it ships with a more secure, more modern HTML parser.
 
The more people use it, the sooner developers can take advantage of the features it offers. Most notably for XenForo, it ships with a more secure, more modern HTML parser.
I actually have to check to see if my shared host has it yet. Last I looked, the selector maxed out at 8.3, and I am on 8.2 (good intentions to bump it up but forgot last maintenance window)
 
I actually have to check to see if my shared host has it yet. Last I looked, the selector maxed out at 8.3, and I am on 8.2 (good intentions to bump it up but forgot last maintenance window)

Does your host time limit you to when you can make server setting changes? If so, I don't think I'd be with them very long.
 
@Chris D it's time for the yearly bump of this thread requesting the current PHP version breakdown :D

Hoping to see 8.1 wiped out in the statistics 🤔

Here we go. Again, focusing on reports from 2.3 installs as this is most representative of customers who are likely to upgrade.

1779878084844.webp

Bored Season 9 GIF by The Simpsons


Last report:

I’d say almost certainly XF 3.0 will be 8.1 or higher as a minimum. Maybe 8.2.

From XF 2.3 installs:

View attachment 318890
 
Looks like you might be safe to go 8.2 for XF3 then :D

(I didn't know XF 2.3 even ran properly on 7.4 :ROFLMAO:)

The extent of issues with 2.3 and 8.4 & 8.5 are just deprecation notices that don’t affect the software outside of logging noise (mostly in development mode).

If you did mean 7.4, then 7.2 and above is fine with 2.3.
 
If you did mean 7.4, then 7.2 and above is fine with 2.3.
Yeah I did mean 7.4, I haven’t ran that old of a version for an age 😆

Personally I run 8.4 on production and I have no error log noise.

In either case, looking forward to being able to take full advantage of modern language features in future XF versions. Hopefully 3.0 will also come with “real” type hints for all core code rather than just relying on docblocks 😉
 
...I have one site on 7.4 because updating requires a massive infrastructure upgrade and almost a complete rewrite of a game backend.
Is it strictly necessary for your game backend to run on the same vhost as your XF forum? Any control panel software worth its storage requirements can have different PHP versions per vhost, and you can easily set that up yourself if you’re not using a control panel.

My own server as an example; I host my own site on 8.4, a legacy forum on 8.3, an old API on 8.1 I think it is, and password protected pre-upgrade snapshots of two vBulletin forums on 8.0 I think it was.

All there is to it is to ensure each PHP-FPM process listens on its own port - locally I use 8080 for 8.0, 8081 for 8.1, you get the idea. Then in Apache or Nginx you connect to the correct proxy using that version’s specific port.
 
Is it strictly necessary for your game backend to run on the same vhost as your XF forum? Any control panel software worth its storage requirements can have different PHP versions per vhost, and you can easily set that up yourself if you’re not using a control panel.

My own server as an example; I host my own site on 8.4, a legacy forum on 8.3, an old API on 8.1 I think it is, and password protected pre-upgrade snapshots of two vBulletin forums on 8.0 I think it was.

All there is to it is to ensure each PHP-FPM process listens on its own port - locally I use 8080 for 8.0, 8081 for 8.1, you get the idea. Then in Apache or Nginx you connect to the correct proxy using that version’s specific port.
It's an issue with connecting to MSSQL with newer versions of PHP, and also partially has to do with part of how the add-on we use for registration and payments is developed. There are also some other complications which is why I have been holding off.
 
It's an issue with connecting to MSSQL with newer versions of PHP, and also partially has to do with part of how the add-on we use for registration and payments is developed. There are also some other complications which is why I have been holding off.
Fair enough, if you decide to take the plunge and need someone to update those addons, you know who to call ;)

I vaguely remember writing an admin portal for a Lineage II private server, that was pretty cursed though as game server manipulation was done via raw packets and only reads were done from MS-SQL.
 
Back
Top Bottom