support PHP Version 7.2.7

[dimsarostov]

Hi people!
SMF 2.1.x supported the PHP Version 7.2.7 ?

[Arantor]

It should do.

[dimsarostov]

It should do.

have you tried?

[Arantor]

No, mostly because I'm not really working on SMF 2.1.

The main issues that 7.2 raised that broke a lot of SMF 2.0, however, I *know* those have been fixed.

[d3vcho]

Not sure if I tried it with PHP 7.2.6 or 7.2.7 but definitely it works.

[Arantor]

And if it doesn't work in some way, that's a bug and should be reported.

[Chen Zhen]

I currently use PHP 7.2.8 and have had no issues.

[Kindred]

and you have self-modified the forum to make it work....

And possibly missed something...

Either way - when the official support for 7.2 comes out (if it does) thn you will have to undo all of your self-made changes.

Once again. SMF 2.0.x does not support php 7.2 (and there is no reason that any reasonable host would force you to run 7.2

[Arantor]

This is the 2.1 board... one presumes we were all discussing 2.1 which should be ok on 7.2...

[Kindred]

whoops...  right.

I know that Chen Zen was trying to modify 2.0 to allow php 7.2 as well and got confused

[Chen Zhen]

Yes that was concerning SMF 2.1.

Concerning SMF 2.0 I made a mod that provides all the changes which should only involve uninstalling that modification when/if the SMF 2.0 branch is updated concerning deprecated syntax.
People are not forced to upgrade to PHP 7.2 at this time but they like to have a choice for various reasons.

and you have self-modified the forum to make it work....

And possibly missed something...

Either way - when the official support for 7.2 comes out (if it does) thn you will have to undo all of your self-made changes.

Once again. SMF 2.0.x does not support php 7.2 (and there is no reason that any reasonable host would force you to run 7.2

Perhaps I can respond to that above statement in kind.

I could explain further but if you can not fathom reasons for using it on your own then I see no point.
BTW - I missed nothing but apparently you did.

[vivien]

Note: Ubuntu server 18.04 only supports PHP 7.2 and more and more hosts migrate to this version.

[albertlast]

i already got a php 7.3 RC4 env running and
notice no error in smf 2.1 gh version.

[SpacePhoenix]

Both versions 5.6 and 7.0 of PHP go EOL by the end of the year, once that happens some hosts might move all their servers over to 7.1 or 7.2

[live627]

Concerning SMF 2.0 I made a mod that provides all the changes

It's over 9000!!!

That mod seems to me very brittle due to the amount of edits it makes.

[Chen Zhen]

It's over 9000!!!

That mod seems to me very brittle due to the amount of edits it makes.

That's highly over exaggerated and Imo very internet troll like in nature.
Perhaps some peer`s bad habits are rubbing off.

Also (unrelated to the above) maybe someone can delete the post from the spam lecher.

[Irisado]

The spam post has been removed, but please use the report to moderator button next time to ensure a faster response.

[Arantor]

I'm not sure I'd disagree on brittle, because there's only three ways to do it: do a find/replace on each standard code using package manager (relies on no changes, misses non stock codes), do a find/replace on just the syntax (way more fragile, can still miss some), or write something insanely clever to do the conversion on Subs.php to pick up every code and every mod in the file.

That last one isn't entirely impossible but it does rely on detecting implicit conditional compilation but some clever calls to get_tokens() to get the syntax as PHP itself sees it would solve that. It also breaks uninstalling any of the mods while it's at it (though so do the others)

Honestly, while I applaud the effort that's gone into trying to prolong the life of a 7 year old system, maybe that energy would have been better spent on getting 2.1 out that already has this future proofed.

[SD-X]

i already got a php 7.3 RC4 env running and
notice no error in smf 2.1 gh version.

Same here with PHP 7.2.8.

[vivien]

Yesterday the PHP team released PHP 7.3.0 for general availability (GA) and marked the third feature update to PHP 7.

Changelog : http://www.php.net/ChangeLog-7.php#7.3.0 [nofollow]

PHP 5.6.39 and PHP 7.0.33 are both security releases considered to be the last release in their respective branches. You should view these versions as the final releases.

[live627]

Yesterday the PHP team released PHP 7.3.0 for general availability (GA) and marked the third feature update to PHP 7.

very nice

[Arantor]

Unfortunately over here in the real world, neither apps nor hosts keep up with PHP releases as fast as PHP out them out.

[Gwenwyfar]

If there's anything good the culture of "maniacally being up to date with everything" brought, it's at least a reduced wait period for new things.

Then instead of "horray! new feature in N! *sets reminder to use it in 10 years*" it's more like "horray! new feature in N! *sets reminder to use it in 5 years*"

[Arantor]

I've never been fond of "move fast and break things", a lesson that the npm world hasn't learned yet but that thankfully enough Composer contributors have.

[Gwenwyfar]

Me neither.

Maybe soon enough more people will learn the lesson (or burn themselves out enough, as already happens to so many) that things go back to a sane pace. Things that don't work can't last long. The sad part is the amount of people who see it as a "good thing".

[SD-X]

Well, personally I fear updating things such as PHP and MySQL because of that same chance of things breaking, (which is all too common with both of those products). In fact, the only thing stopping me from updating to anything higher than PHP 7.2.8 right now is the fact that they reverted everything allowing the use of "caching_sha2_password" from MySQL 8+ in PHP 7.2.9 and higher.

Security is important to me, so I'm stuck in a loop of trying to decide whether I should upgrade PHP and lower the encryption on my MySQL passwords to secure PHP further, or hold off and leave PHP at risk so MySQL remains more secure. (Not that it matters anyway. The right type of security exploit in either can probably result in the other being breached, but hey...that's life).

Too bad they don't offer updates to their products like SMF does. *Wink wink*.

As for the actual topic, has anyone tested PHP 7.3.0 with SMF 2.1.x yet?

[Kindred]

It will break even more things than 7.2 does

[albertlast]

i already got a php 7.3 RC4 env running and
notice no error in smf 2.1 gh version.

--> 2.1 is fine with php 7.3