Quote from: Aleeious on April 22, 2014, 09:11:21 PMQuote from: admin on April 22, 2014, 04:07:11 PMTrue, however they will be running newer versions of PHP that are more secure and compatibility won't maa difference throwing out the whole "5.2.17 for compatibility" issue. As for the others that aren't compatible my last comment still stands.Quote from: Aleeious on April 21, 2014, 02:33:41 AM
EDIT: You should also remove PHP versions that have reached EOL(end-of-life) PHP 5.3 EOL Announcement and require the site owners to use the next higher version. If the scripts on the site stops working then the owner will hopefully "wake up" and can either upgrade the script to a newer version, ask the script publisher to support the latest PHP version or move to a different script. I once had a very bad experience with a host that refuses to upgrade past 5.2.17 because:
Sorry for the double post. Our plans are to remove 5.2 and 5.3 once 5.6 is released. (5.2 may very well be removed before that. It has only been kept due to compatibility reasons for some users, but honestly it is not worth the risk.) The problem is that some have 5.2.17 selected that can use a newer version.Quote from: admin on April 22, 2014, 04:02:07 PMNope, seems when you upgraded the forum you removed the permissions required to self update it. Thanks for updating it.Quote from: Aleeious on April 21, 2014, 02:33:41 AM
P.S. Could you please change the Pong Master text next to my name to Aleeious Lead Developer Thanks.
Are you not able to update your title in the forum? If not, I will do this for you.
Sincerely,
Aleeious
I agree with you about older PHP versions, especially 5.2.17. We will force these to at least 5.3.28 and remove 5.2.17 as a selection. I have found some users still using 5.2.17 because that is what they were using on the old servers, even though they are running newer scripts. Once 5.6.x is released, the same thing will be done with 5.3, moving all that have 5.3 set to 5.4. The choices will be 5.4/5.5/5.6 at that time.